summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Dold <florian@dold.me>2021-04-26 23:13:52 +0200
committerFlorian Dold <florian@dold.me>2021-04-26 23:13:52 +0200
commit68e245069a3ba19cd014d9ec82d3b8b6cff7e6a1 (patch)
treee4a82fba76d5f4a46d4c18d880d366d3c094696b
parent2c0769f6e5a37e68cf407f092776ef7317d86973 (diff)
downloaddocs-68e245069a3ba19cd014d9ec82d3b8b6cff7e6a1.tar.gz
docs-68e245069a3ba19cd014d9ec82d3b8b6cff7e6a1.tar.bz2
docs-68e245069a3ba19cd014d9ec82d3b8b6cff7e6a1.zip
expand tombstone explanation
-rw-r--r--design-documents/019-wallet-backup-merge.rst4
1 files changed, 3 insertions, 1 deletions
diff --git a/design-documents/019-wallet-backup-merge.rst b/design-documents/019-wallet-backup-merge.rst
index ceedfb3..3c4541f 100644
--- a/design-documents/019-wallet-backup-merge.rst
+++ b/design-documents/019-wallet-backup-merge.rst
@@ -131,7 +131,9 @@ Q / A
* A: When syncing with a backup server that still has an old version
(but same device ID and wallet root pub), the tombstones ensure
that no old data is re-surfaced that has been deleted in later
- versions.
+ versions. This can happen in practice even with only one device,
+ namely when a backup provider is unavailable for a long time,
+ but then becomes available again.
* Q: Why are tombstones only GCed after exceeding an age threshold?