From bb850aba2c1c54a76bc4ccc0b4059bdb8329330b Mon Sep 17 00:00:00 2001
From: Shayan <shayanbahal@gmail.com>
Date: Tue, 26 Jun 2018 18:30:40 -0400
Subject: [PATCH] fix markdown nested lists

---
 developer-libraries.md  | 30 ++++++++++++++++--------------
 selective-disclosure.md | 26 +++++++++++++-------------
 2 files changed, 29 insertions(+), 27 deletions(-)

diff --git a/developer-libraries.md b/developer-libraries.md
index 6059560..352998f 100644
--- a/developer-libraries.md
+++ b/developer-libraries.md
@@ -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
-   - Bitcore
-   - python-bitcoinlib
-   - z-nomp
--- Shielded Addresses
---- Nothing!
+  - 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
+  - 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
 
 
 
diff --git a/selective-disclosure.md b/selective-disclosure.md
index 262b55a..4301f91 100644
--- a/selective-disclosure.md
+++ b/selective-disclosure.md
@@ -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
+  - ...