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 0EF6F1355 for ; Tue, 15 Sep 2015 12:56:30 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com [209.85.192.47]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1C89E12E for ; Tue, 15 Sep 2015 12:56:28 +0000 (UTC) Received: by qgez77 with SMTP id z77so141886829qge.1 for ; Tue, 15 Sep 2015 05:56:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sci.ventures; s=google; h=date:sender:mime-version:message-id:in-reply-to:references:from:to :cc:subject:content-type; bh=Xmn3Gr27Gmhbpes/KFLHgLBWvw5BncNfRfZI3eeqgTo=; b=AOyJMKlrCtYR9ZZpu1h+bbRUfG5TDH+tAlY/7m1DG/meXogwVwHpnAzFGo1/lZLddz z3Z3eNsxWYn66HTTP/7cdFBQfkg+QWz+QYfdK5k/AGqdzpqSKvc/BtHQpL1ZutFGFSnU gpM0FsGLvwymO3HaM22VU64ANnoodZ8Tg/72s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sci.ph; s=google; h=date:sender:mime-version:message-id:in-reply-to:references:from:to :cc:subject:content-type; bh=Xmn3Gr27Gmhbpes/KFLHgLBWvw5BncNfRfZI3eeqgTo=; b=H2fHdW31RAF/4TnEy3av2oh0JNgipq57FJnrBsdlhVUaUvg4nVSsalGBWrU1sm2Cqr QosfhjzWNP786zvtzIaKSnnMxHAi4Rc+YyuwaKMZPTP6OEuFRxWBhbLWQqi+zCkq0Wd1 L1ycxODO/hr8WjcWyDsohJ2S7odEEbTx7K9Qg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:sender:mime-version:message-id:in-reply-to :references:from:to:cc:subject:content-type; bh=Xmn3Gr27Gmhbpes/KFLHgLBWvw5BncNfRfZI3eeqgTo=; b=fB26jyqqf8dHFztneFKuFEGb80JmVMolAjqJ4I3ND9b3BzbNSWlvWemlXuJFlW1jYw 4a5NG7BvtHBeVSrEFodsHxNtcbROyvX4pK2+j9+El9vpxVUKHiC5NdxOpuqw1ktmdOWu uwBf9WycdIqw0YEgNM22+uPIJNu4xMYvustjWEWLJFC0Gt6JK+MuAIPnDv5EUpU5CyxG QHT/ArEwEv8e+zjKXnj5EY3/otW695Z1f6tsnZ37nQrXRvTx2uf6G0UFQsC0ADrwXiFN 6c0Anch722NTs3iilR8Xrz0cHanuAfrE6eam+mqMVEc6N+KR/Ttd0G6IbLBjl5om8ssF /wcA== X-Gm-Message-State: ALoCoQknwWox7XjAlfztwMBu/jruiKX3czaMri/DQwCVZKukdFf3YJGo6kFcu45Wn8MpZp7Yz3mr X-Received: by 10.140.101.110 with SMTP id t101mr31079833qge.20.1442321788196; Tue, 15 Sep 2015 05:56:28 -0700 (PDT) Received: from hedwig-51.prd.orcali.com (ec2-54-85-253-165.compute-1.amazonaws.com. [54.85.253.165]) by smtp.gmail.com with ESMTPSA id v10sm7910370qgv.32.2015.09.15.05.56.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Sep 2015 05:56:27 -0700 (PDT) Date: Tue, 15 Sep 2015 05:56:27 -0700 (PDT) X-Google-Original-Date: Tue, 15 Sep 2015 12:56:27 GMT Sender: John Bailon MIME-Version: 1.0 X-Mailer: Nodemailer (0.5.0; +http://www.nodemailer.com/) Message-Id: <1442321787241.25b10266@Nodemailer> In-Reply-To: References: X-Orchestra-Oid: B4AB91FB-12F3-46FC-9743-7D09EFCB7859 X-Orchestra-Sig: 6ba8f4f9ab595de99d758909d9201ca246d29dba X-Orchestra-Thrid: TECD6BC8B-F1DF-4416-9B83-7350B377AFD5_1512377369530741589 X-Orchestra-Thrid-Sig: 418fb5fe2f5e56a69bdf9ef61c0b87202e3659d4 X-Orchestra-Account: 0eb95feedd80495877c654d5ae19b81c9701267f From: "John Bailon" To: "Angel Leon" Content-Type: multipart/alternative; boundary="----Nodemailer-0.5.0-?=_1-1442321787482" 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 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 12:56:30 -0000 ------Nodemailer-0.5.0-?=_1-1442321787482 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Wouldn't need to. The is of BTC to . BTC is the = intermediary currency, as is basically how it becomes in this =22payment = rails=22 method. To the receiver, it wouldn't matter what currency the transaction came from= . On Tue, Sep 15, 2015 at 8:48 PM, Angel Leon wrote: > might want to specify there that the rate being sent is out of USD. > http://twitter.com/gubatron > On Tue, Sep 15, 2015 at 7:10 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=3Fcurrency=3Dxau&rate=3D0.= 2084&expires=3D1458432000 >> >> 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=3F >> >> >> Regards, >> John >> >> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F >> bitcoin-dev mailing list >> bitcoin-dev@lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >> >> ------Nodemailer-0.5.0-?=_1-1442321787482 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Wouldn't need to. The <rate> is of BTC to <currency>. BTC = is the intermediary currency, as is basically how it becomes in this = =22payment rails=22 method.
To the receiver, it wouldn't matter what currency the transaction came= from.=C2=A0



On Tue, Sep 15, 2015 at 8:48 PM= , Angel Leon <gubatron@gmail.com> = wrote:

might want to specify there that the rate being sent = is out of USD.


On Tue, Sep 15, 2015 at 7:10 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=3Fcurren= cy=3Dxau&rate=3D0.2084&expires=3D1458432000

Wherein:
<= currency> : =C2=A0the 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=3F


Regards,
John

=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.= org/mailman/listinfo/bitcoin-dev



------Nodemailer-0.5.0-?=_1-1442321787482--