DD 22: Wallet Proofs to Auditor

23.23. DD 22: Wallet Proofs to Auditor#

Design status:

Draft

Implementation status:

Not started

DD shepherd:

TBD

Historical contributors:

Florian Dold

First published:

2021-09-12

Last substantive change:

2021-09-12

Normative references:

Auditor RESTful API

Note

This incomplete proposal is retained for historical context and is non-normative. Auditor complaint submission remains to be designed and implemented in the normative API.

23.23.1. Summary#

This design document defines the structure and contents of proofs of misbehavior that the wallet sends to auditors.

23.23.2. Motivation#

There are some situations where the wallet learns that some entity did something against the protocol specification. When the wallet has cryptographic proof for this, this proof should be stored in the database and eventually be exportable to auditors, courts, etc.

23.23.3. Requirements#

  • Users should be able to review all the information that a misbehavior proof would reveal.

23.23.4. Proposed Solution#

23.23.4.1. Types of Misbehavior#

This section collects all types of misbehavior for which the wallet can export cryptographic proof.

  • exchange-denomination-spec-inconsistent

    An exchange has announced a denomination with the same denomination public key, but different metadata (value, expiration)

  • exchange-denomination-gone

    The exchange is not accepting/listing a denomination anymore that it previously listed.

23.23.5. Discussion / Q&A#

  • What about complaints to the auditor that do not contain cryptographic proof? (e.g. “exchange XYZ has not been responding for the last 14 days”)