From: "John Bailon" <john@sci•ph>
To: "Angel Leon" <gubatron@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Instant exchange rates URI scheme
Date: Tue, 15 Sep 2015 05:56:27 -0700 (PDT) [thread overview]
Message-ID: <1442321787241.25b10266@Nodemailer> (raw)
In-Reply-To: <CADZB0_ZLAFUYSghfNi5t=cM1+Lv8dxdh-BaRAFNTt9AH30Z8-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2098 bytes --]
Wouldn't need to. The <rate> is of BTC to <currency>. BTC is the intermediary currency, as is basically how it becomes in this "payment rails" 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 <gubatron@gmail•com> 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?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
>>
>>
[-- Attachment #2: Type: text/html, Size: 3056 bytes --]
next prev parent reply other threads:[~2015-09-15 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 11:10 John Bailon
2015-09-15 12:48 ` Angel Leon
2015-09-15 12:56 ` John Bailon [this message]
2015-09-15 14:40 ` Thomas Kerin
2015-09-15 15:02 ` John Bailon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1442321787241.25b10266@Nodemailer \
--to=john@sci$(echo .)ph \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gubatron@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox