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 D7FA2142F for ; Tue, 15 Sep 2015 11:10:55 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com [209.85.213.178]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 093AEAF for ; Tue, 15 Sep 2015 11:10:54 +0000 (UTC) Received: by igcrk20 with SMTP id rk20so11717904igc.1 for ; Tue, 15 Sep 2015 04:10:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sci.ventures; s=google; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=QJfXXOlKJVeUaj6AsthF6JY2RadsLD4AUwhdmu6VF34=; b=Ggr0B+WSZE77xNVVUfndonbUCBj67rEuqIt9zeBP0EnpNIYrppVy/vxa4jWerbG/9a nWYWIQFUs5DhHvs1QXXHHJdKCTN/KlEsYSx25TwwlbmuFbyMj7VqZ2fWIMtFX+eOl7ae sd4+DjO5sx/U9WeU1elGEQ0I9j+YqUif28sTA= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sci.ph; s=google; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=QJfXXOlKJVeUaj6AsthF6JY2RadsLD4AUwhdmu6VF34=; b=CTqmjSH+to7j9KwcJ7qOroZXrnBK5sjYPvP/pREd9olukQ6J+FoP5wjFCYiRZaYDF1 Bq8vyF2U9zu7e58Lt1Sfn9QWMc+ruACoqFzVqSUj8dI9FHUrWmqanrFRiIkpxNjyWlzh j61DVYOBcP8E/Y8JkdaD9j4dk8HnfxJrF1B9U= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to:content-type; bh=QJfXXOlKJVeUaj6AsthF6JY2RadsLD4AUwhdmu6VF34=; b=bMSo1UsJKxjjVZbChnk3tsqttoLpZrEObwDk5TQhb/jZSEdf2RpD3zI3iA7pgXhdgB dhehKxMccdMR2jnBCu9RD7u95LKKM1dRePeaN1RbooUB8/n7nyhUCYiR0C/LRAoDcjxG 2DNbtNLrtzqcMA0TEpv+K9BoAem8Okw/LG8h1P+uomKg48x7/1ArZNcA77LOJSIF20ph PekiGV7TreMRnvm15Y+F9JNZdXq+SIdPrKL8MoO6pSRC0544LXllHFDMetAo882Tlyto Ce3YBIJGlCYYlBxYLwTEeWRZisngBfX35w2gkHlnvTaYMF+14HoHyqx2qK4WNOPMC+3G pzaQ== X-Gm-Message-State: ALoCoQn3LriNgmHM4FydQeRaKd89OSs4c3AVOPjmtqd3u2hGaO2VXUynimzlfiN+iHgSXDkrZFMp MIME-Version: 1.0 X-Received: by 10.50.124.4 with SMTP id me4mr4736166igb.34.1442315454143; Tue, 15 Sep 2015 04:10:54 -0700 (PDT) Sender: john@sci.ventures Received: by 10.107.168.3 with HTTP; Tue, 15 Sep 2015 04:10:54 -0700 (PDT) Date: Tue, 15 Sep 2015 19:10:54 +0800 X-Google-Sender-Auth: 62Y5n_t5sbuMuATEXSTeqf_19hM Message-ID: From: John Bailon To: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary=089e0111d0c84c8c10051fc73c4f X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 Subject: [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 11:10:56 -0000 --089e0111d0c84c8c10051fc73c4f Content-Type: text/plain; charset=UTF-8 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 --089e0111d0c84c8c10051fc73c4f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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
--089e0111d0c84c8c10051fc73c4f--