022-wallet-auditor-reports.rst (1710B)
1 DD 22: Wallet Proofs to Auditor 2 ############################### 3 4 :Design status: Draft 5 :Implementation status: Not started 6 :DD shepherd: TBD 7 :Historical contributors: Florian Dold 8 :First published: 2021-09-12 9 :Last substantive change: 2021-09-12 10 :Normative references: :doc:`../core/api-auditor` 11 12 .. note:: 13 14 This incomplete proposal is retained for historical context and is 15 non-normative. Auditor complaint submission remains to be designed and 16 implemented in the normative API. 17 18 19 Summary 20 ======= 21 22 This design document defines the structure and contents of proofs 23 of misbehavior that the wallet sends to auditors. 24 25 Motivation 26 ========== 27 28 There are some situations where the wallet learns that some entity did 29 something against the protocol specification. When the wallet has 30 cryptographic proof for this, this proof should be stored in the database and 31 eventually be exportable to auditors, courts, etc. 32 33 Requirements 34 ============ 35 36 * Users should be able to review all the information that 37 a misbehavior proof would reveal. 38 39 Proposed Solution 40 ================= 41 42 Types of Misbehavior 43 -------------------- 44 45 This section collects all types of misbehavior for which the wallet 46 can export cryptographic proof. 47 48 * ``exchange-denomination-spec-inconsistent`` 49 50 An exchange has announced a denomination with the same 51 denomination public key, but different metadata (value, expiration) 52 53 * ``exchange-denomination-gone`` 54 55 The exchange is not accepting/listing a denomination 56 anymore that it previously listed. 57 58 59 Discussion / Q&A 60 ================ 61 62 * What about complaints to the auditor that do not contain 63 cryptographic proof? (e.g. "exchange XYZ has not been responding 64 for the last 14 days")