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
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1Rs9Bg-0006tL-8T
for bitcoin-development@lists.sourceforge.net;
Tue, 31 Jan 2012 08:35:36 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.47 as permitted sender)
client-ip=209.85.160.47; envelope-from=laanwj@gmail.com;
helo=mail-pw0-f47.google.com;
Received: from mail-pw0-f47.google.com ([209.85.160.47])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Rs9Bc-00044v-7E
for bitcoin-development@lists.sourceforge.net;
Tue, 31 Jan 2012 08:35:36 +0000
Received: by pbbb4 with SMTP id b4so429445pbb.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 31 Jan 2012 00:35:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.74.4 with SMTP id p4mr47930877pbv.123.1327998926330; Tue,
31 Jan 2012 00:35:26 -0800 (PST)
Received: by 10.143.8.11 with HTTP; Tue, 31 Jan 2012 00:35:26 -0800 (PST)
In-Reply-To: <jg88ed$i85$1@dough.gmane.org>
References: <1327881329.49770.YahooMailNeo@web121003.mail.ne1.yahoo.com>
<jg88ed$i85$1@dough.gmane.org>
Date: Tue, 31 Jan 2012 09:35:26 +0100
Message-ID: <CA+s+GJDLoUG43hdLKYMwehBO9qqE=YCm7eJ2RN-TTTY_+OLp=A@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=f46d0413911d4419fd04b7ced83a
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Rs9Bc-00044v-7E
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP 21 (modification BIP 20)
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2012 08:35:36 -0000
--f46d0413911d4419fd04b7ced83a
Content-Type: text/plain; charset=UTF-8
I also wonder whether the "send to private address" should be part of this
BIP, or a future one.
IMO (but your mileage may vary) this BIP should only define the bare-bones
URL scheme, AND provide room for future extensions such
as send-to-private-address, send-multiple-signers, and so on. These should
be forwards-compatible (as Luke-Jr says) in the sense that older clients
can detect schemes they don't understand and give the user an appropriate
error message.
Maybe we need a send-type parameter to define the scheme?
Good point on the version parameter. How are clients supposed to handle
this? Refuse to handle the request if their URL scheme parser version is
older than in the URL? This should be in the BIP.
Wladimir
On Tue, Jan 31, 2012 at 9:23 AM, Andreas Schildbach
<andreas@schildbach.de>wrote:
> Generally I prefer BIP 21 over BIP 20.
>
> I'm neutral on the 'send' parameter - present in both BIPs - which I
> don't understand. I think a practical usecase should be given in the BIP.
>
> Also, the 'version' parameter is unclear. What does it mean? Is an oder
> defined on versions (1.0b > 1.0)? Why is it an ";" parameter rather than
> a normal "&" parameter?
>
>
> On 01/30/2012 12:55 AM, Amir Taaki wrote:
> > Matt Corallo posted a modification of BIP 20 in an earlier email and I
> > asked him if he wanted to become the champion of that BIP he submitted.
> >
> > It is a modification of BIP 20 sans the alternative non-decimal number
> > stuff.
> >
> > https://en.bitcoin.it/wiki/BIP_0021
> >
> > Right now, I will ask the GUI client implementations like MultiBit or
> > Bitcoin-Qt, not different codebases like BitCoinJ or libbitcoin if they
> > support BIP 20 or BIP 21. Feel free to raise any objections.
> >
> > More weight will be given to GUIs with actual URI sche me
> > implementations and it's good to have a general consensus.
> >
> >
> >
> ------------------------------------------------------------------------------
> > Try before you buy = See our experts in action!
> > The most comprehensive online learning library for Microsoft developers
> > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> > Metro Style Apps, more. Free future releases when you subscribe now!
> > http://p.sf.net/sfu/learndevnow-dev2
> >
> >
> >
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--f46d0413911d4419fd04b7ced83a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div><br></div>I also wonder whether the "send to private address"=
; should be part of this BIP, or a future one.<div><br></div><div>IMO (but =
your=C2=A0mileage=C2=A0may vary) this BIP should only define the bare-bones=
URL scheme, AND provide room for future extensions such as=C2=A0send-to-pr=
ivate-address, send-multiple-signers, and so on. These should be forwards-c=
ompatible (as Luke-Jr says) in the sense that older clients can detect sche=
mes they don't understand and give the user an appropriate error messag=
e.</div>
<div><br></div><div>Maybe we need a send-type parameter to define the schem=
e?</div><div><br></div><div>Good point on the version parameter. How are cl=
ients supposed to handle this? Refuse to handle the request if their URL sc=
heme parser version is older than in the URL? This should be in the BIP.=C2=
=A0</div>
<div><br></div><div>Wladimir</div><div><br><div class=3D"gmail_quote">On Tu=
e, Jan 31, 2012 at 9:23 AM, Andreas Schildbach <span dir=3D"ltr"><<a hre=
f=3D"mailto:andreas@schildbach.de">andreas@schildbach.de</a>></span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Generally I prefer BIP 21 over BIP 20.<br>
<br>
I'm neutral on the 'send' parameter - present in both BIPs - wh=
ich I<br>
don't understand. I think a practical usecase should be given in the BI=
P.<br>
<br>
Also, the 'version' parameter is unclear. What does it mean? Is an =
oder<br>
defined on versions (1.0b > 1.0)? Why is it an ";" parameter r=
ather than<br>
a normal "&" parameter?<br>
<div><div class=3D"h5"><br>
<br>
On 01/30/2012 12:55 AM, Amir Taaki wrote:<br>
> Matt Corallo posted a modification of BIP 20 in an earlier email and I=
<br>
> asked him if he wanted to become the champion of that BIP he submitted=
.<br>
><br>
> It is a modification of BIP 20 sans the alternative non-decimal number=
<br>
> stuff.<br>
><br>
> <a href=3D"https://en.bitcoin.it/wiki/BIP_0021" target=3D"_blank">http=
s://en.bitcoin.it/wiki/BIP_0021</a><br>
><br>
> Right now, I will ask the GUI client implementations like MultiBit or<=
br>
> Bitcoin-Qt, not different codebases like BitCoinJ or libbitcoin if the=
y<br>
> support BIP 20 or BIP 21. Feel free to raise any objections.<br>
><br>
> More weight will be given to GUIs with actual URI sche me<br>
> implementations and it's good to have a general consensus.<br>
><br>
><br>
</div></div><div class=3D"im">> ----------------------------------------=
--------------------------------------<br>
> Try before you buy =3D See our experts in action!<br>
> The most comprehensive online learning library for Microsoft developer=
s<br>
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC=
3,<br>
> Metro Style Apps, more. Free future releases when you subscribe now!<b=
r>
> <a href=3D"http://p.sf.net/sfu/learndevnow-dev2" target=3D"_blank">htt=
p://p.sf.net/sfu/learndevnow-dev2</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Bitcoin-development mailing list<br>
> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-d=
evelopment@lists.sourceforge.net</a><br>
> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo=
pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco=
in-development</a><br>
<br>
<br>
<br>
</div>---------------------------------------------------------------------=
---------<br>
Keep Your Developer Skills Current with LearnDevNow!<br>
<div class=3D"im">The most comprehensive online learning library for Micros=
oft developers<br>
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,<br=
>
Metro Style Apps, more. Free future releases when you subscribe now!<br>
</div><a href=3D"http://p.sf.net/sfu/learndevnow-d2d" target=3D"_blank">htt=
p://p.sf.net/sfu/learndevnow-d2d</a><br>
<div class=3D"HOEnZb"><div class=3D"h5">___________________________________=
____________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--f46d0413911d4419fd04b7ced83a--
|
