From 20486be042fc0cd300990e74a69f4085b286dc28 Mon Sep 17 00:00:00 2001 From: teor Date: Wed, 17 Feb 2021 10:12:41 +1000 Subject: [PATCH] Client design: add "one database per key" alternative --- book/src/dev/rfcs/0009-zebra-client.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/book/src/dev/rfcs/0009-zebra-client.md b/book/src/dev/rfcs/0009-zebra-client.md index fab1dec7..359d44e8 100644 --- a/book/src/dev/rfcs/0009-zebra-client.md +++ b/book/src/dev/rfcs/0009-zebra-client.md @@ -279,6 +279,10 @@ Supporting a wallet assumes risk. Effort required to implement wallet functiona - light client protocol as currently implemented requires stack assumptions 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