summaryrefslogtreecommitdiff
path: root/da/8a5b0300603e3a37ff6b6317c2fafbb42b5c32
blob: aae88112bd47ed19aab70a33870eb7fd4d41aa20 (plain)
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
Return-Path: <gubatron@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id BC114E1A
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 15 Sep 2015 12:48:55 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f177.google.com (mail-ig0-f177.google.com
	[209.85.213.177])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4F9D21D7
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 15 Sep 2015 12:48:55 +0000 (UTC)
Received: by igcpb10 with SMTP id pb10so13670962igc.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 15 Sep 2015 05:48:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=6znYtbPROlGx9fnLggn9YHYL9KYw7LkesxFOvctdtCE=;
	b=YBcvNoferyHf0nm+7Q/qrvZgW75mVmwOz5KI5fcefmV4SeQHCJOxRiGo9N3HLzjbQV
	XOfIBgWu0BfBoKrJTf9nVEjMTFne1+HtRfFSpJz6KCGz/8ws5rfjzK95Xd3gfKVotBmc
	UI9hNw6G4SquVFVb7a4lg4/mSFfjBHiT+YrEBmKkq8hmjIlyn56L/Gqkh7hrhK+xkgQU
	lbrN2mswutRtkZ2xmRL9N+/pcJliq2Vr2/mZfk0G6Nrvq4QCxf9dV3LFk+7wlw06UI+V
	D4imucLt/mv2tUkslZbBM1vpHf39PdtA3t4BbA2/7wXp5imOgIsyHh8hAbEaoQvKRd6F
	GMhQ==
X-Received: by 10.50.56.84 with SMTP id y20mr5510458igp.89.1442321334730; Tue,
	15 Sep 2015 05:48:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.14.85 with HTTP; Tue, 15 Sep 2015 05:48:35 -0700 (PDT)
In-Reply-To: <CA+Y+xvT6Qn0zNT4=vKgyQBwF4n3m+bRp=F7zq2CtwK+dQAmgzg@mail.gmail.com>
References: <CA+Y+xvT6Qn0zNT4=vKgyQBwF4n3m+bRp=F7zq2CtwK+dQAmgzg@mail.gmail.com>
From: Angel Leon <gubatron@gmail.com>
Date: Tue, 15 Sep 2015 08:48:35 -0400
Message-ID: <CADZB0_ZLAFUYSghfNi5t=cM1+Lv8dxdh-BaRAFNTt9AH30Z8-Q@mail.gmail.com>
To: John Bailon <john@sci.ph>
Content-Type: multipart/alternative; boundary=089e0158aa18cf0896051fc89a3e
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,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:48:55 -0000

--089e0158aa18cf0896051fc89a3e
Content-Type: text/plain; charset=UTF-8

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

--089e0158aa18cf0896051fc89a3e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">might want to specify there that the rate being sent is ou=
t of USD.</div><div class=3D"gmail_extra"><br clear=3D"all"><div><div class=
=3D"gmail_signature"><a href=3D"http://twitter.com/gubatron" target=3D"_bla=
nk">http://twitter.com/gubatron</a><br></div></div>
<br><div class=3D"gmail_quote">On Tue, Sep 15, 2015 at 7:10 AM, John Bailon=
 via bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.=
linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.or=
g</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">







Hello,<div><br>I&#39;d like to propose a BIP for a standard URI scheme to a=
llow wallet operators that implement instant exchange or pegging to other c=
urrencies, cryptocurrencies or asset classes to allow for interoperable com=
munications of rates and other pertinent information.<br><br>The idea is to=
 include in the wallet address as parameters information that supplements t=
he presentation of a proposed transaction.<br><br>For example, a wallet ope=
rator that instantly exchanges bitcoin to gold would present a wallet addre=
ss as follows:<div>bitcoin:1JohnxNT6jRzhu3H1wgVFbSGKmHP4EUjUV?currency=3Dxa=
u&amp;rate=3D0.2084&amp;expires=3D1458432000<br><br>Wherein:<br>&lt;currenc=
y&gt; : =C2=A0the currency, cryptocurrency or asset that the transaction wi=
ll end up as encoded in ISO 4217 if applicable.<br>&lt;rate&gt; : the bitco=
in to &lt;currency&gt; rate as dictated by receiving wallet<br>&lt;expires&=
gt; : unix timestamp of when the rate loses validity<br><br>This would allo=
w 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 abo=
ve, 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>Thou=
ghts?<br><br><br>Regards,<br>John<br></div></div></div>
<br>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
<br></blockquote></div><br></div>

--089e0158aa18cf0896051fc89a3e--