blob: 0df5e427f0e0c59ce955d9ff720acbc9bf292daf (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
DD22: Wallet Proofs to Auditor
##############################
.. note::
Status (2021-05-25): Writing in progress.
Summary
=======
This design document defines the structure and contents of proofs
of misbehavior that the wallet sends to auditors.
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.
Requirements
============
* Users should be able to review all the information that
a misbehavior proof would reveal.
Proposed Solution
=================
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.
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")
|
