📅 Original date posted:2015-09-15 📝 Original message:Wouldn't need to. The ...

John Bailon [ARCHIVE] /

npub13y4…ckvz

2023-06-07 17:40:24

in reply to nevent1q…qgvt

📅 Original date posted:2015-09-15
📝 Original message: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 at 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 at 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 at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150915/e632b30d/attachment-0001.html>;

Author Public Key

npub13y4eg8g4clfr2kj8lnc9wrcuh9tnv40dml37jhe36wh0ghf8tadsaxckvz

Show more details

Published at

2023-06-07 17:40:24

Kind type

1 Short Text Note

Event JSON

{ "id": "c06c8134a22f2159d9757779af88cae4c50f458323204bd503a9939f2f1754c6", "pubkey": "892b941d15c7d2355a47fcf0570f1cb9573655eddfe3e95f31d3aef45d275f5b", "created_at": 1686159624, "kind": 1, "tags": [ [ "e", "9b6c3392aaae5050fca592ec61c9ebdb28fc47243b6d590cb7abaa63544aa534", "", "root" ], [ "e", "cd66f37045fb1cebb94c70044c3d4ca6df85a3c663bde407b721b13d4dc4fd79", "", "reply" ], [ "p", "c1d3f07ddbb5e8ccdf7e1a71dc707629a884323a62c7d504be5dc931240f61b9" ] ], "content": "📅 Original date posted:2015-09-15\n📝 Original message:Wouldn't need to. The \u003crate\u003e is of BTC to \u003ccurrency\u003e. BTC is the intermediary currency, as is basically how it becomes in this \"payment rails\" method.\n\nTo the receiver, it wouldn't matter what currency the transaction came from.\n\nOn Tue, Sep 15, 2015 at 8:48 PM, Angel Leon \u003cgubatron at gmail.com\u003e wrote:\n\n\u003e might want to specify there that the rate being sent is out of USD.\n\u003e http://twitter.com/gubatron\n\u003e On Tue, Sep 15, 2015 at 7:10 AM, John Bailon via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e Hello,\n\u003e\u003e\n\u003e\u003e I'd like to propose a BIP for a standard URI scheme to allow wallet\n\u003e\u003e operators that implement instant exchange or pegging to other currencies,\n\u003e\u003e cryptocurrencies or asset classes to allow for interoperable communications\n\u003e\u003e of rates and other pertinent information.\n\u003e\u003e\n\u003e\u003e The idea is to include in the wallet address as parameters information\n\u003e\u003e that supplements the presentation of a proposed transaction.\n\u003e\u003e\n\u003e\u003e For example, a wallet operator that instantly exchanges bitcoin to gold\n\u003e\u003e would present a wallet address as follows:\n\u003e\u003e\n\u003e\u003e bitcoin:1JohnxNT6jRzhu3H1wgVFbSGKmHP4EUjUV?currency=xau\u0026rate=0.2084\u0026expires=1458432000\n\u003e\u003e\n\u003e\u003e Wherein:\n\u003e\u003e \u003ccurrency\u003e : the currency, cryptocurrency or asset that the transaction\n\u003e\u003e will end up as encoded in ISO 4217 if applicable.\n\u003e\u003e \u003crate\u003e : the bitcoin to \u003ccurrency\u003e rate as dictated by receiving wallet\n\u003e\u003e \u003cexpires\u003e : unix timestamp of when the rate loses validity\n\u003e\u003e\n\u003e\u003e This would allow the sending wallet the ability to present up-to-date\n\u003e\u003e exchange rates. When, for example, a wallet operator that pegs to the USD\n\u003e\u003e scans the address above, it would be able to present to the user the\n\u003e\u003e following information:\n\u003e\u003e\n\u003e\u003e 1. USD to XAU rate\n\u003e\u003e 2. How much XAU will be received by the address\n\u003e\u003e 3. How long before the rates expires\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e Thoughts?\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e Regards,\n\u003e\u003e John\n\u003e\u003e\n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e\n\u003e\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150915/e632b30d/attachment-0001.html\u003e", "sig": "3dde7fa53e683e55a43152bfbed9cdc8bc4dd15ed0763eb94e3e194b8eaa3dafc8556c198269ac9b6fb4c4b70e37d36662513ca205edffeb0f76e96303bb99aa" }