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

Client design: add "one database per key" alternative

This commit is contained in:
teor 2021-02-17 10:12:41 +10:00 committed by Deirdre Connolly
parent 55613db846
commit 20486be042
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
book/src/dev/rfcs/0009-zebra-client.md
View File

@ -279,6 +279,10 @@ Supporting a wallet assumes risk. Effort required to implement wallet functiona
- light client protocol as currently implemented requires stack assumptions - light client protocol as currently implemented requires stack assumptions
such as protobufs and a hardcoded lightserver to talk to such as protobufs and a hardcoded lightserver to talk to
- What about having one database per key?
- easy to reliably delete or backup all data related to a single key
- might use slightly more space/CPU
- slightly harder to delete all the keys
# Unresolved questions # Unresolved questions
[unresolved-questions]: #unresolved-questions [unresolved-questions]: #unresolved-questions