[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Taler] Synchronization and backup
From: |
Jeff Burdges |
Subject: |
Re: [Taler] Synchronization and backup |
Date: |
Fri, 16 Feb 2018 04:09:16 +0100 |
On Fri, 2018-02-16 at 01:49 +0100, Christian Grothoff wrote:
> Any other opinions? Other options I'm missing?
We could assume that wallet loss is rare, record withdrawals for the
reserve in the reserve itself, and provide a rewithdraw function that
users trigger manually with scary warnings. We cannot spend any
rewithdrawn coins of course, but we can slowly over time attempt to
refresh them, and be smart about ordering, etc. It's helpful if we make
the linking protocol safe too, but even if we do we should still warn
users about possible loss of funds to discourage using this.
We must move key material between wallets in advance of course, or maybe
give users a printed key to enter on failure. I think wallets should
actually operate off distinct reserves though because it lessens the
information revealed, saves users from telling their wallet how much to
withdraw, and does not increase the information to move.
Jeff
signature.asc
Description: This is a digitally signed message part
- Re: [Taler] Synchronization and backup, (continued)
- Re: [Taler] Synchronization and backup, Christian Grothoff, 2018/02/16
- Re: [Taler] Synchronization and backup, Jeff Burdges, 2018/02/16
- Re: [Taler] Synchronization and backup, Christian Grothoff, 2018/02/17
- Re: [Taler] Synchronization and backup, Jeff Burdges, 2018/02/17
- Re: [Taler] Synchronization and backup, Jeff Burdges, 2018/02/17
- Re: [Taler] Synchronization and backup, Christian Grothoff, 2018/02/16
Re: [Taler] Synchronization and backup, Christian Grothoff, 2018/02/16
Re: [Taler] Synchronization and backup,
Jeff Burdges <=
Re: [Taler] Synchronization and backup, Raphael Arias, 2018/02/20
Re: [Taler] Synchronization and backup, Christian Grothoff, 2018/02/20
Re: [Taler] Synchronization and backup, Jeff Burdges, 2018/02/21