1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
|
Return-Path: <john@sci.ventures>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 0EF6F1355
for <bitcoin-dev@lists.linuxfoundation.org>;
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 <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 15 Sep 2015 12:56:28 +0000 (UTC)
Received: by qgez77 with SMTP id z77so141886829qge.1
for <bitcoin-dev@lists.linuxfoundation.org>;
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 <john@sci.ventures>
MIME-Version: 1.0
X-Mailer: Nodemailer (0.5.0; +http://www.nodemailer.com/)
Message-Id: <1442321787241.25b10266@Nodemailer>
In-Reply-To: <CADZB0_ZLAFUYSghfNi5t=cM1+Lv8dxdh-BaRAFNTt9AH30Z8-Q@mail.gmail.com>
References: <CADZB0_ZLAFUYSghfNi5t=cM1+Lv8dxdh-BaRAFNTt9AH30Z8-Q@mail.gmail.com>
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" <john@sci.ph>
To: "Angel Leon" <gubatron@gmail.com>
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 <bitcoin-dev@lists.linuxfoundation.org>
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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=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 <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=
.
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=3Fcurrency=3Dxau&rate=3D0.=
2084&expires=3D1458432000
>>
>> 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=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
<div>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.</div>
<div>To the receiver, it wouldn't matter what currency the transaction came=
from.=C2=A0</div>
<div class=3D=22mailbox=5Fsignature=22><br></div>
<br><br><div class=3D=22gmail=5Fquote=22><p>On Tue, Sep 15, 2015 at 8:48 PM=
, Angel Leon <span dir=3D=22ltr=22><<a href=3D=22mailto:gubatron@gmail.=
com=22 target=3D=22=5Fblank=22>gubatron@gmail.com</a>></span> =
wrote:<br></p><blockquote class=3D=22gmail=5Fquote=22 style=3D=22margin:0 0=
0 .8ex;border-left:1px #ccc solid;padding-left:1ex;=22><div>
<div dir=3D=22ltr=22>might want to specify there that the rate being sent =
is out of USD.</div>
<div class=3D=22gmail=5Fextra=22>
<br clear=3D=22all=22><div><div class=3D=22gmail=5Fsignature=22>
<a href=3D=22http://twitter.com/gubatron=22>http://twitter.=
com/gubatron</a><br></div></div>
<br><div class=3D=22gmail=5Fquote=22>On Tue, Sep 15, 2015 at 7:10 AM, John =
Bailon via bitcoin-dev <span dir=3D=22ltr=22><<a =
href=3D=22mailto:bitcoin-dev@lists.linuxfoundation.org=22>bitcoin-dev@lists=
.linuxfoundation.org</a>></span> wrote:<br><blockquote =
class=3D=22gmail=5Fquote=22 style=3D=22margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex=22>
<div dir=3D=22ltr=22>
Hello,<div>
<br>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.<br><br>The idea is to include in=
the wallet address as parameters information that supplements the =
presentation of a proposed transaction.<br><br>For example, a wallet =
operator that instantly exchanges bitcoin to gold would present a wallet =
address as follows:<div>bitcoin:1JohnxNT6jRzhu3H1wgVFbSGKmHP4EUjUV=3Fcurren=
cy=3Dxau&rate=3D0.2084&expires=3D1458432000<br><br>Wherein:<br><=
currency> : =C2=A0the currency, cryptocurrency or asset that the =
transaction will end up as encoded in ISO 4217 if applicable.=
<br><rate> : the bitcoin to <currency> rate as dictated by =
receiving wallet<br><expires> : unix timestamp of when the rate loses=
validity<br><br>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:<br><br>1. USD to XAU rate<br>2. How much XAU =
will be received by the address<br>3. How long before the rates =
expires<br><br></div>
<div><br></div>
<div>Thoughts=3F<br><br><br>Regards,<br>John<br></div>
</div>
</div>
<br>=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<br=
>
bitcoin-dev mailing list<br><a href=3D=22mailto:bitcoin-dev@lists.=
linuxfoundation.org=22>bitcoin-dev@lists.linuxfoundation.org</a><br><a =
href=3D=22https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev=22=
rel=3D=22noreferrer=22>https://lists.linuxfoundation.=
org/mailman/listinfo/bitcoin-dev</a><br><br></blockquote>
</div>
<br></div>
</div></blockquote></div><br>
------Nodemailer-0.5.0-?=_1-1442321787482--
|
