Merge pull request #3 from shayanb/master

Selective Disclosure and Developer Libraries workshop notes
This commit is contained in:
Richard Littauer 2018-06-26 16:26:37 -04:00 committed by GitHub
commit ab1f7d1711
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 80 additions and 0 deletions

49
developer-libraries.md Normal file
View File

@ -0,0 +1,49 @@
# Developer Libraries
2018.06.26 13:00-14:00 Jack (Str4d) Grigg
The workshop was mainly a discussion on what kind of libraries and tools are needed in the ZCash ecosystem
The state of ZCash Libraries now:
- Zcash libraries are mostly ported from Bitcoin ones
-- Libraries with t-address support
- Bitcore
- python-bitcoinlib
- z-nomp
-- Shielded Addresses
--- Nothing!
- Most of the codes are in Rust
-- Librustzcash
--- Libwallet-zcash
---- What functionalities do we want it to do?
--- Also used in Zcash Fullnode
- Discussion on what do we need?
-- In-browser Signing / Creation of transactions
-- cross-language tools
-- Need for a curated list of dev tools
-- APIs for humans and machines
- Back to where dev tools are required:
-- Low friction - Convenience:
--- Browser
--- Docker
--- Packages with every language (npm, pip)
- Operations required for such libraries to do:
-- Address creation
--- ZIP32
-- Address (key) Management
-- Signing
--- Multi-signature Architecture
-- Proving
-- Payment detection
-- UTXO Management
-- Serialization

31
selective-disclosure.md Normal file
View File

@ -0,0 +1,31 @@
# Selective Disclosure
2018.06.26 14:10-15:10 - Jack (Dodger) Gavigan
Possible Disclosures:
- Payment Disclosure
-- 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)
- Selective Disclosure (Not yet merged)
-- 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
--
... // Missing notes
-- How to identify who leaked information in case there are multiple parties receiving the receipts.
- what is available in Zcash today?
-- Payment disclosure: Recipients, Amount, Memo
-- Some options to do read only keys in new SPV implementations -- Coming soon --
- One of the main issues with Selective disclosure is inadvertently disclose informations that they do not want disclosed
-- such as UI misuse
-- Device seizure
-- ...