From eef76c7c8430f80205cf2e40895a581c047cda8f Mon Sep 17 00:00:00 2001 From: teor Date: Thu, 4 Jun 2020 08:24:52 +1000 Subject: [PATCH] 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. --- design/design.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/design/design.md b/design/design.md index 5cff7e13..d8296ae5 100644 --- a/design/design.md +++ b/design/design.md @@ -30,6 +30,12 @@ The following are general desiderata for Zebra: * Zebra should checkpoint on Sapling activation and drop all 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 ================== @@ -200,7 +206,7 @@ for Zcash script inspection, debugging, etc. ### Responsible for - 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. ### Notes