taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 68e245069a3ba19cd014d9ec82d3b8b6cff7e6a1
parent 2c0769f6e5a37e68cf407f092776ef7317d86973
Author: Florian Dold <florian@dold.me>
Date:   Mon, 26 Apr 2021 23:13:52 +0200

expand tombstone explanation

Diffstat:
Mdesign-documents/019-wallet-backup-merge.rst | 4+++-
1 file changed, 3 insertions(+), 1 deletion(-)

diff --git 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?