fix markdown nested lists
This commit is contained in:
parent
3526cb4526
commit
bb850aba2c
|
@ -8,25 +8,27 @@ The workshop was mainly a discussion on what kind of libraries and tools are nee
|
|||
|
||||
The state of ZCash Libraries now:
|
||||
- Zcash libraries are mostly ported from Bitcoin ones
|
||||
-- Libraries with t-address support
|
||||
- Libraries with t-address support
|
||||
- Bitcore
|
||||
- python-bitcoinlib
|
||||
- z-nomp
|
||||
-- Shielded Addresses
|
||||
--- Nothing!
|
||||
|
||||
- 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
|
||||
- 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
|
||||
- In-browser Signing / Creation of transactions
|
||||
- cross-language tools
|
||||
- Need for a curated list of dev tools
|
||||
- APIs for humans and machines
|
||||
|
||||
|
||||
|
||||
|
|
|
@ -4,28 +4,28 @@
|
|||
|
||||
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)
|
||||
- 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
|
||||
- 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.
|
||||
- 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 --
|
||||
- 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
|
||||
-- ...
|
||||
- such as UI misuse
|
||||
- Device seizure
|
||||
- ...
|
||||
|
|
Loading…
Reference in New Issue