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
|
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 D7FA2142F
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 15 Sep 2015 11:10:55 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com
[209.85.213.178])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 093AEAF
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 15 Sep 2015 11:10:54 +0000 (UTC)
Received: by igcrk20 with SMTP id rk20so11717904igc.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 15 Sep 2015 04:10:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sci.ventures; s=google;
h=mime-version:sender:date:message-id:subject:from:to:content-type;
bh=QJfXXOlKJVeUaj6AsthF6JY2RadsLD4AUwhdmu6VF34=;
b=Ggr0B+WSZE77xNVVUfndonbUCBj67rEuqIt9zeBP0EnpNIYrppVy/vxa4jWerbG/9a
nWYWIQFUs5DhHvs1QXXHHJdKCTN/KlEsYSx25TwwlbmuFbyMj7VqZ2fWIMtFX+eOl7ae
sd4+DjO5sx/U9WeU1elGEQ0I9j+YqUif28sTA=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sci.ph; s=google;
h=mime-version:sender:date:message-id:subject:from:to:content-type;
bh=QJfXXOlKJVeUaj6AsthF6JY2RadsLD4AUwhdmu6VF34=;
b=CTqmjSH+to7j9KwcJ7qOroZXrnBK5sjYPvP/pREd9olukQ6J+FoP5wjFCYiRZaYDF1
Bq8vyF2U9zu7e58Lt1Sfn9QWMc+ruACoqFzVqSUj8dI9FHUrWmqanrFRiIkpxNjyWlzh
j61DVYOBcP8E/Y8JkdaD9j4dk8HnfxJrF1B9U=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:sender:date:message-id:subject:from
:to:content-type;
bh=QJfXXOlKJVeUaj6AsthF6JY2RadsLD4AUwhdmu6VF34=;
b=bMSo1UsJKxjjVZbChnk3tsqttoLpZrEObwDk5TQhb/jZSEdf2RpD3zI3iA7pgXhdgB
dhehKxMccdMR2jnBCu9RD7u95LKKM1dRePeaN1RbooUB8/n7nyhUCYiR0C/LRAoDcjxG
2DNbtNLrtzqcMA0TEpv+K9BoAem8Okw/LG8h1P+uomKg48x7/1ArZNcA77LOJSIF20ph
PekiGV7TreMRnvm15Y+F9JNZdXq+SIdPrKL8MoO6pSRC0544LXllHFDMetAo882Tlyto
Ce3YBIJGlCYYlBxYLwTEeWRZisngBfX35w2gkHlnvTaYMF+14HoHyqx2qK4WNOPMC+3G
pzaQ==
X-Gm-Message-State: ALoCoQn3LriNgmHM4FydQeRaKd89OSs4c3AVOPjmtqd3u2hGaO2VXUynimzlfiN+iHgSXDkrZFMp
MIME-Version: 1.0
X-Received: by 10.50.124.4 with SMTP id me4mr4736166igb.34.1442315454143; Tue,
15 Sep 2015 04:10:54 -0700 (PDT)
Sender: john@sci.ventures
Received: by 10.107.168.3 with HTTP; Tue, 15 Sep 2015 04:10:54 -0700 (PDT)
Date: Tue, 15 Sep 2015 19:10:54 +0800
X-Google-Sender-Auth: 62Y5n_t5sbuMuATEXSTeqf_19hM
Message-ID: <CA+Y+xvT6Qn0zNT4=vKgyQBwF4n3m+bRp=F7zq2CtwK+dQAmgzg@mail.gmail.com>
From: John Bailon <john@sci.ph>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=089e0111d0c84c8c10051fc73c4f
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
Subject: [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 11:10:56 -0000
--089e0111d0c84c8c10051fc73c4f
Content-Type: text/plain; charset=UTF-8
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
--089e0111d0c84c8c10051fc73c4f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">
Hello,<div><br>I'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&rate=3D0.2084&expires=3D1458432000<br><br>Wherein:<br><currenc=
y> : =C2=A0the currency, cryptocurrency or asset that the transaction wi=
ll end up as encoded in ISO 4217 if applicable.<br><rate> : the bitco=
in to <currency> rate as dictated by receiving wallet<br><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>
--089e0111d0c84c8c10051fc73c4f--
|
