Non-repudiation feature storage (enterprise)

Questions
1

Reading: Non-repudiation — Daml SDK 2.7.6 documentation

Note that at the current stage you need to also have a PostgreSQL server running where signed commands will be persisted.

  1. Does this mean that each command is stored, or there is a commandId+signature/validation stored in the DB that you relate/join back to the ledger transactions when running a report?

  2. The DB used by the non-repudiation reverse proxy is required to perform the non-repudiation review when reviewing the ledger? or is a data point stored against the ledger that would be accessed?

Thanks

2

It means that the whole command is stored. No interaction with the Ledger API happens after the command has been issued.

The middleware is a single process that also spins up a web server used by the operator to verify repudiation claims against the same database used to store signed commands.

Note that the non-repudiation middleware is in labs status and is subsequently not covered by support and can be removed at any time (you can read more on status definitions here).

3

Thanks @stefanobaghino-da. How is the signed commands in the db joined with the ledger transactions? It is the commandId?

4

The non-repudiation middleware is concerned exclusively with commands. It doesn’t perform any join with the ledger data but exclusively ensures that commands are signed with a known signature and stores them for later verification. If you want to link back a transaction to a signed command, you would have to join the information as part of a client-side solution and join it with the command ID in each transaction as reported by the Ledger API (docs).

1 Like
5

Understood. Thank you.