2018-06-26 12:55:06 -07:00
|
|
|
# Selective Disclosure
|
|
|
|
|
|
|
|
|
|
2018.06.26 14:10-15:10 - Jack (Dodger) Gavigan
|
|
|
|
|
|
|
|
|
|
Possible Disclosures:
|
|
|
|
|
- Payment Disclosure
|
2018-06-26 15:30:40 -07:00
|
|
|
- For zAddress payments to prove the payment
|
|
|
|
|
- proof for shielded payment (receipt)
|
|
|
|
|
- should be saved before the software throws away the proof
|
|
|
|
|
- Discloses everything (Recipient, amount, memo)
|
2018-06-26 12:55:06 -07:00
|
|
|
|
|
|
|
|
- Selective Disclosure (Not yet merged)
|
2018-06-26 15:30:40 -07:00
|
|
|
- Only disclose a selective section (only amount, recipient or ...)
|
|
|
|
|
- might make shielded transactions less efficient, requires changes in the protocol/cryptography
|
|
|
|
|
- If this happen (Selective Disclosure tuple), it's possible to get rid of transparent transactions all together
|
2018-06-26 12:55:06 -07:00
|
|
|
--
|
|
|
|
|
|
|
|
|
|
... // Missing notes
|
|
|
|
|
|
|
|
|
|
|
2018-06-26 15:30:40 -07:00
|
|
|
- How to identify who leaked information in case there are multiple parties receiving the receipts.
|
2018-06-26 12:55:06 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
- what is available in Zcash today?
|
2018-06-26 15:30:40 -07:00
|
|
|
- Payment disclosure: Recipients, Amount, Memo
|
|
|
|
|
- Some options to do read only keys in new SPV implementations -- Coming soon --
|
2018-06-26 12:55:06 -07:00
|
|
|
|
|
|
|
|
- One of the main issues with Selective disclosure is inadvertently disclose informations that they do not want disclosed
|
2018-06-26 15:30:40 -07:00
|
|
|
- such as UI misuse
|
|
|
|
|
- Device seizure
|
|
|
|
|
- ...
|
