From bd992fda1275b841839f10deb177c6aa9d373825 Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Mon, 26 Apr 2021 22:57:01 +0200 Subject: Q/A in one place --- design-documents/019-wallet-backup-merge.rst | 27 +++++++++++++-------------- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/design-documents/019-wallet-backup-merge.rst b/design-documents/019-wallet-backup-merge.rst index a5ec9a6f..373fdf4b 100644 --- a/design-documents/019-wallet-backup-merge.rst +++ b/design-documents/019-wallet-backup-merge.rst @@ -30,20 +30,6 @@ backup account. This happens when: In this scenario, the devices have the same device ID and the same wallet root public key. -.. note:: - - Q: Why doesn't the wallet root public key get rotated every time - that a wallet backup is restored on a new device? - - A: Because that would mean that old "paper backups" and Anastasis - backups stop working, because they are based on the wallet root key. - - Q: Why can't the wallet obtain some unique devices identifier to exclude - case 3? - - A: Because we don't have a reliable API for this on many platforms. - Even if we had one, we shouldn't rely on it. - Requirements ============ @@ -152,3 +138,16 @@ Q / A * A: If we deleted them immediately, this might cause data to be re-surface if a user temporarily removes and adds a backup account (say by accident) that hasn't been synced in a while. + +* Q: Why doesn't the wallet root public key get rotated every time + that a wallet backup is restored on a new device? + + * A: Because that would mean that old "paper backups" and Anastasis + backups stop working, because they are based on the wallet root key. + +* Q: Why can't the wallet obtain some unique devices identifier to exclude + case 3 (same device ID, same wallet root pub)? + + * A: Because we don't have a reliable API for this on many platforms. + Even if we had one, we shouldn't rely on it. + -- cgit v1.2.3