From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 07AAC1132 for ; Tue, 15 Sep 2015 14:40:47 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-la0-f45.google.com (mail-la0-f45.google.com [209.85.215.45]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 243A3217 for ; Tue, 15 Sep 2015 14:40:46 +0000 (UTC) Received: by lagj9 with SMTP id j9so110646651lag.2 for ; Tue, 15 Sep 2015 07:40:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ogO0dEGpy7UPDstcfoC6rMPcxSLjrZggJAp6wW/zx0o=; b=N51IQ+nB7ONcAotjFZhmRjI5ZP00R2htzpQJ3DIu0bpvSsOi8EjwGrHTebNyLP42el VeemFHbrv9tcoPUIhWCEIMgkYieVTYJ2NQqmfRyDrTV85I383CAAKqR7luy/4zqbfb+m KX2WzQNxszKlyO0VR6StS7Xs7sq+WIG1IZy6bGINkAtfrDC+yDfSpUidBGVuYYvGWZQO hR1ujGRZxep77/wF99CzIsPlFxTfeR1fJ00ggVXTN5LBX1oDeLkPDDLidCAHDhX4o+rX fArx6Hy7H3hyvKkXb5e2OI2C0qXElH6tUVNhzYdJ/2EURaNfGVENMrEu2KzYcSelCaCi YC2w== MIME-Version: 1.0 X-Received: by 10.112.136.170 with SMTP id qb10mr22161019lbb.34.1442328044503; Tue, 15 Sep 2015 07:40:44 -0700 (PDT) Received: by 10.112.167.103 with HTTP; Tue, 15 Sep 2015 07:40:44 -0700 (PDT) Received: by 10.112.167.103 with HTTP; Tue, 15 Sep 2015 07:40:44 -0700 (PDT) In-Reply-To: References: Date: Tue, 15 Sep 2015 15:40:44 +0100 Message-ID: From: Thomas Kerin To: John Bailon Content-Type: multipart/alternative; boundary=089e0115fd30be0c25051fca2ac8 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] Instant exchange rates URI scheme X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 14:40:47 -0000 --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: > : the currency, cryptocurrency or asset that the transaction > will end up as encoded in ISO 4217 if applicable. > : the bitcoin to rate as dictated by receiving wallet > : 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

Something very similar was posted not too long ago.

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.

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?

On 15 Sep 2015 11:11 am, "John Bailon via b= itcoin-dev" <bitcoin-dev@lists.linuxfoundation.org> wrote:
Hello,

I'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.

The idea is to= include in the wallet address as parameters information that supplements t= he presentation of a proposed transaction.

For example, a wallet ope= rator that instantly exchanges bitcoin to gold would present a wallet addre= ss as follows:
bitcoin:1JohnxNT6jRzhu3H1wgVFbSGKmHP4EUjUV?currency=3Dxa= u&rate=3D0.2084&expires=3D1458432000

Wherein:
<currenc= y> : =C2=A0the currency, cryptocurrency or asset that the transaction wi= ll end up as encoded in ISO 4217 if applicable.
<rate> : the bitco= in to <currency> rate as dictated by receiving wallet
<expires&= gt; : unix timestamp of when the rate loses validity

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>1. USD to XAU rate
2. How much XAU will be received by the address3. How long before the rates expires


Thou= ghts?


Regards,
John

_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.= linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev

--089e0115fd30be0c25051fca2ac8--