taler
[Top][All Lists]
Advanced

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

Re: [Taler] wallet exchange management


From: Christian Grothoff
Subject: Re: [Taler] wallet exchange management
Date: Thu, 9 Apr 2020 20:34:18 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0

On 4/9/20 6:51 PM, Torsten Grote wrote:
> Hi Florian,
> 
> On 2020-04-09 06:10, Florian Dold wrote:
>> thanks for your constructive comments.  I think we still have some
>> different ideas about how the exchange list management should work
>> conceptually.
> 
> Good we talk about it then :)
> 
>> I thought when we select a different exchange for withdrawal, it doesn't
>> necessarily get added permanently to the list of known exchanges.  This
>> is why it's called "query" and not "add".  It'll get added either by
>> setting it as "trusted" or by accepting a withdrawal.
> 
> My reasoning is that if someone goes through the trouble of manually
> adding an exchange (and the wallet finds that there's nothing with it),
> they would like it saved for later even if they don't end up choosing it
> for a withdrawal right now.

Makes sense. If it was a valid exchange URL (/keys came back with a
well-formed 'version', at least), we probably should remember at least
the URL.

> It might also make things simpler for the implementation and open the
> door for a dedicated management UI that is independent of withdrawals.

I was actually thinking that we'd have _exactly_ the same dialog: list
with all the exchanges for a particular currency, user is expected to
"select the default", showing the fee structure for the selected
exchange (on top, above the list?), and a "confirm/select" (action?)
button. Only if you go to that list via "settings", the button takes you
back to the main settings screen (or the list of all currencies, or from
wherever that dialog is reached), while in a withdraw situation the
button takes you to the ToS (or if ToS was accepted, directly to the
withdraw-confirm) screen.

> Btw. maybe it makes sense to later also introduce an exchange-add
> taler:// Uri to make it easier for people to add different exchanges?

Yes, that's what I was thinking about when I mentioned adding exchanges
via QR code.  We _also_ need an auditor-add taler:// URI while we're at it.

Oh, and we should start an RFC/draft/LSD specifying all the taler://
URIs that are defined.  Florian: if you can provide a very simple list
with syntax examples, I could possibly turn this into a task for Stefan
and/or Buck.

Happy hacking!

Christian

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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