MIME-Version: 1.0
In-Reply-To: <CA+Y+xvT6Qn0zNT4=vKgyQBwF4n3m+bRp=F7zq2CtwK+dQAmgzg@mail.gmail.com>
References: <CA+Y+xvT6Qn0zNT4=vKgyQBwF4n3m+bRp=F7zq2CtwK+dQAmgzg@mail.gmail.com>
Date: Tue, 15 Sep 2015 15:40:44 +0100
Message-ID: <CAHv+tb7LPz4PiTu9JLLMbKu_i5U3LytRDmAeDLtV+-7ps+CPXA@mail.gmail.com>
From: Thomas Kerin <thomas.kerin@gmail.com>
To: John Bailon <john@sci.ph>
Content-Type: multipart/alternative; boundary=089e0115fd30be0c25051fca2ac8
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Instant exchange rates URI scheme
Precedence: list

--089e0115fd30be0c25051fca2ac8
Content-Type: text/plain; charset=UTF-8

Something very similar was posted not too long ago.

Long and sort of it is, there is no point in saying you priced in GBP, etc,
because it can vary from exchange to exchange.

To be honest, adding more things to consider at checkout time confuses
things; why not just specify the amount of Bitcoin you wish to be paid?
On 15 Sep 2015 11:11 am, "John Bailon via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hello,
>
> I'd like to propose a BIP for a standard URI scheme to allow wallet
> operators that implement instant exchange or pegging to other currencies,
> cryptocurrencies or asset classes to allow for interoperable communications
> of rates and other pertinent information.
>
> The idea is to include in the wallet address as parameters information
> that supplements the presentation of a proposed transaction.
>
> For example, a wallet operator that instantly exchanges bitcoin to gold
> would present a wallet address as follows:
>
> bitcoin:1JohnxNT6jRzhu3H1wgVFbSGKmHP4EUjUV?currency=xau&rate=0.2084&expires=1458432000
>
> Wherein:
> <currency> :  the currency, cryptocurrency or asset that the transaction
> will end up as encoded in ISO 4217 if applicable.
> <rate> : the bitcoin to <currency> rate as dictated by receiving wallet
> <expires> : unix timestamp of when the rate loses validity
>
> This would allow the sending wallet the ability to present up-to-date
> exchange rates. When, for example, a wallet operator that pegs to the USD
> scans the address above, it would be able to present to the user the
> following information:
>
> 1. USD to XAU rate
> 2. How much XAU will be received by the address
> 3. How long before the rates expires
>
>
> Thoughts?
>
>
> Regards,
> John
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

--089e0115fd30be0c25051fca2ac8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Something very similar was posted not too long ago. </p>
<p dir=3D"ltr">Long and sort of it is, there is no point in saying you pric=
ed in GBP, etc, because it can vary from exchange to exchange. </p>
<p dir=3D"ltr">To be honest, adding more things to consider at checkout tim=
e confuses things; why not just specify the amount of Bitcoin you wish to b=
e paid?</p>
<div class=3D"gmail_quote">On 15 Sep 2015 11:11 am, &quot;John Bailon via b=
itcoin-dev&quot; &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.or=
g">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br type=3D"attribut=
ion"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">


Hello,<div><br>I&#39;d like to propose a BIP for a standard URI scheme to a=
llow wallet operators that implement instant exchange or pegging to other c=
urrencies, cryptocurrencies or asset classes to allow for interoperable com=
munications of rates and other pertinent information.<br><br>The idea is to=
 include in the wallet address as parameters information that supplements t=
he presentation of a proposed transaction.<br><br>For example, a wallet ope=
rator that instantly exchanges bitcoin to gold would present a wallet addre=
ss as follows:<div>bitcoin:1JohnxNT6jRzhu3H1wgVFbSGKmHP4EUjUV?currency=3Dxa=
u&amp;rate=3D0.2084&amp;expires=3D1458432000<br><br>Wherein:<br>&lt;currenc=
y&gt; : =C2=A0the currency, cryptocurrency or asset that the transaction wi=
ll end up as encoded in ISO 4217 if applicable.<br>&lt;rate&gt; : the bitco=
in to &lt;currency&gt; rate as dictated by receiving wallet<br>&lt;expires&=
gt; : unix timestamp of when the rate loses validity<br><br>This would allo=
w the sending wallet the ability to present up-to-date exchange rates. When=
, for example, a wallet operator that pegs to the USD scans the address abo=
ve, it would be able to present to the user the following information:<br><=
br>1. USD to XAU rate<br>2. How much XAU will be received by the address<br=
>3. How long before the rates expires<br><br></div><div><br></div><div>Thou=
ghts?<br><br><br>Regards,<br>John<br></div></div></div>
<br>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
<br></blockquote></div>

--089e0115fd30be0c25051fca2ac8--