octo
/
Zebra
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Document that zebra isn't intended for light wallets 

zebra-state can't be used to implement light wallets, because it keeps a
copy of the chain state.

Document this design choice in the design doc.

Closes #425.
This commit is contained in:
teor 2020-06-04 08:24:52 +10:00 committed by Deirdre Connolly
parent dff4f12aca
commit eef76c7c84
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
design/design.md
View File

@ -30,6 +30,12 @@ The following are general desiderata for Zebra:
* Zebra should checkpoint on Sapling activation and drop all * Zebra should checkpoint on Sapling activation and drop all
Sprout-related functionality not required post-Sapling. Sprout-related functionality not required post-Sapling.
### Non-Goals
* Zebra keeps a copy of the chain state, so it isn't intended for
lightweight applications like light wallets. Those applications
should use a light client protocol.
Internal Structure Internal Structure
================== ==================
@ -200,7 +206,7 @@ for Zcash script inspection, debugging, etc.
### Responsible for ### Responsible for
- implementation of some event a user might trigger - implementation of some event a user might trigger
- would be used to implement a wallet - would be used to implement a full wallet
- create transactions, monitors shielded wallet state, etc. - create transactions, monitors shielded wallet state, etc.
### Notes ### Notes