[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Taler] Synchronization and backup

From: Florian Dold
Subject: Re: [Taler] Synchronization and backup
Date: Fri, 16 Feb 2018 04:15:53 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

This does not cover the case where I (or rather normal users that want
to use Taler) have my laptop, my desktop machine, my phone, maybe a
tablet, and I do not want to have different wallets on them, they should
be kept in sync as fast as possible.

I'm all for adding things to give users better anonymity, but at the
core we must design it to be usable.

- Florian

On 02/16/2018 04:09 AM, Jeff Burdges wrote:
> 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

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]