John Bailon [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2015-09-15 to 2015-09-15
💬 Posted a total of 3 messages
📚 Participated in the following categories: bitcoin-dev
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 17:40:25

- reply

📅 Original date posted:2015-09-15
📝 Original message:This scheme would mostly be beneficial to end users of instant exchange wallets and would be implemented by the operators. None of the parameters would be filled up by the user by hand. It's more of enabling different wallet operators to communicate with each other and to be able to present to their end users the rates they are getting when sending from their pegged wallet to another pegged wallet. Abstracting bitcoin rates from both end users.
To illustrate, imagine Alice who has a USD wallet wants to send JPY 10,000 to Bob who has a JPY pegged wallet.
Alice's wallet scans Bob's wallet which tells Alice's wallet the following info:
1. Bob's BTC address
2. Bob's wallet currency is JPY
3. Bob's wallet operator is pricing BTC 1 at JPY 27,779 for the next 5 minutes.
With these info, Alice's wallet can already derive the following:
Alice needs to send 0.35998416 BTC to send JPY 10,000. Alice's wallet can also show how much 0.35998416 BTC is in USD, which is USD 83.27. Alice's wallet can present it as follows;
"You are sending JPY 10,000 for USD 83.27 to Bob's wallet."
On Tue, Sep 15, 2015 at 10:40 PM, Thomas Kerin <thomas.kerin at gmail.com>
wrote:
> 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 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/cc6163fa/attachment.html>

2023-06-07 17:40:25

- reply

2023-06-07 17:40:24

- reply

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

2023-06-07 17:40:24

- reply

📅 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>

2023-06-07 17:40:24

- reply

2023-06-07 17:40:24

- reply