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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1RsEn4-0005mE-BG
for bitcoin-development@lists.sourceforge.net;
Tue, 31 Jan 2012 14:34:34 +0000
X-ACL-Warn:
Received: from mail-bk0-f47.google.com ([209.85.214.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RsEmy-0001KU-Ca
for bitcoin-development@lists.sourceforge.net;
Tue, 31 Jan 2012 14:34:34 +0000
Received: by bke17 with SMTP id 17so8322bke.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 31 Jan 2012 06:34:21 -0800 (PST)
Received: by 10.204.153.206 with SMTP id l14mr11072268bkw.3.1328020461687;
Tue, 31 Jan 2012 06:34:21 -0800 (PST)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.204.123.11 with HTTP; Tue, 31 Jan 2012 06:33:38 -0800 (PST)
In-Reply-To: <1328020046.70720.YahooMailNeo@web121002.mail.ne1.yahoo.com>
References: <1328020046.70720.YahooMailNeo@web121002.mail.ne1.yahoo.com>
From: slush <slush@centrum.cz>
Date: Tue, 31 Jan 2012 15:33:38 +0100
X-Google-Sender-Auth: pSrnmGndya563fH40blCGsvsvqQ
Message-ID: <CAJna-Hhx_JquBCOWA096YDe1HzJhGBrcZvvaDg2_2x9XJM+pNA@mail.gmail.com>
To: Amir Taaki <zgenjix@yahoo.com>
Content-Type: multipart/alternative; boundary=0015175cffd8df942104b7d3dbb3
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(slush[at]centrum.cz)
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1RsEmy-0001KU-Ca
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
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 14:34:34 -0000
--0015175cffd8df942104b7d3dbb3
Content-Type: text/plain; charset=ISO-8859-1
Hi Amir,
> All the HTML, URI and everything uses decimal numbers alone. I see no
reason for breaking with tradition.
excuse me if it was already discussed, but maybe using satoshis instead of
decimal bitcoin would be better choice? We all know about pains with proper
handling decimal numbers across of all implementations - and it's not only
about json-rpc.
Otherwise I agree, BIP 21 is better than BIP 20 because it's easier to
implement all points of the standard.
Best,
slush
On Tue, Jan 31, 2012 at 3:27 PM, Amir Taaki <zgenjix@yahoo.com> wrote:
> BIP 20 really has no support among implementations such as Bitcoin-Qt,
> Electrum, MultiBit or Bitcoin-JS. As the most active and visible user
> facing GUI projects (all with some form of URI Scheme), their opinion
> carries the most weight. To a lesser degree Bitcoin-Qt has the large
> majority of users too (although that's a line of reasoning I'd discourage).
>
> Normally we should probably Reject BIP 21 and re-submit a new standard
> (for history's sake), but as a) BIP 21 is largely a copy paste of BIP 20
> sans some sections b) it is still a draft, probably the best thing here is
> if you all agree on something to run it by BlueMatt and then we'll make it
> the new BIP 21.
>
> I can see a consensus forming on most parts. Just the send private key is
> contentious, and there's the topic of adding a time to expire field for
> merchants (this is a very good idea IMO).
>
> Also BIP 20 is problematic because it is incompatible with about every
> standard on the web. All the HTML, URI and everything uses decimal numbers
> alone. I see no reason for breaking with tradition. Note that everytime I
> have to write Color or Vectorize (as a British speaker) in my code, I die a
> little inside. But it's convention and American English = International
> English. Also it would be cool if all code used a *real* international
> language (like Esperanto) but the world ain't perfect! We live in a
> decimal-counting English-speaking Windows-using God-worshipping world!
>
> (no offense to decimal-counting English-speaking Windows-using
> God-worshipping world- I do half those things too :)
>
>
> ------------------------------------------------------------------------------
> 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
>
--0015175cffd8df942104b7d3dbb3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi Amir,<div><br></div><div><div>>=A0=A0All the HTML, URI and everything=
uses decimal numbers alone. I see no reason for breaking with tradition.=
=A0</div></div><div><br></div><div>excuse me if it was already discussed, b=
ut maybe using satoshis instead of decimal bitcoin would be better choice? =
We all know about pains with proper handling decimal numbers across of all =
implementations - and it's not only about json-rpc.</div>
<div><br></div><div>Otherwise I agree, BIP 21 is better than BIP 20 because=
it's easier to implement all points of the standard.</div><div><br></d=
iv><div>Best,</div><div>slush</div><div><br><div class=3D"gmail_quote">On T=
ue, Jan 31, 2012 at 3:27 PM, Amir Taaki <span dir=3D"ltr"><<a href=3D"ma=
ilto:zgenjix@yahoo.com">zgenjix@yahoo.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">BIP 20 really has no support among implement=
ations such as Bitcoin-Qt, Electrum, MultiBit or Bitcoin-JS. As the most ac=
tive and visible user facing GUI projects (all with some form of URI Scheme=
), their opinion carries the most weight. To a lesser degree Bitcoin-Qt has=
the large majority of users too (although that's a line of reasoning I=
'd discourage).<br>
<br>
Normally we should probably Reject BIP 21 and re-submit a new standard (for=
history's sake), but as a) BIP 21 is largely a copy paste of BIP 20 sa=
ns some sections b) it is still a draft, probably the best thing here is if=
you all agree on something to run it by BlueMatt and then we'll make i=
t the new BIP 21.<br>
<br>
I can see a consensus forming on most parts. Just the send private key is c=
ontentious, and there's the topic of adding a time to expire field for =
merchants (this is a very good idea IMO).<br>
<br>
Also BIP 20 is problematic because it is incompatible with about every stan=
dard on the web. All the HTML, URI and everything uses decimal numbers alon=
e. I see no reason for breaking with tradition. Note that everytime I have =
to write Color or Vectorize (as a British speaker) in my code, I die a litt=
le inside. But it's convention and American English =3D International E=
nglish. Also it would be cool if all code used a *real* international langu=
age (like Esperanto) but the world ain't perfect! We live in a decimal-=
counting English-speaking Windows-using God-worshipping world!<br>
<br>
(no offense to=A0decimal-counting English-speaking Windows-using God-worshi=
pping world- I do half those things too :)<br>
<br>
---------------------------------------------------------------------------=
---<br>
Keep Your Developer Skills Current with LearnDevNow!<br>
The most comprehensive online learning library for Microsoft 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>
<a href=3D"http://p.sf.net/sfu/learndevnow-d2d" target=3D"_blank">http://p.=
sf.net/sfu/learndevnow-d2d</a><br>
_______________________________________________<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>
</blockquote></div><br></div>
--0015175cffd8df942104b7d3dbb3--
|
