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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <melvincarvalho@gmail.com>) id 1UmOMP-0002Lq-U4
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Jun 2013 13:11:41 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.177 as permitted sender)
client-ip=209.85.217.177; envelope-from=melvincarvalho@gmail.com;
helo=mail-lb0-f177.google.com;
Received: from mail-lb0-f177.google.com ([209.85.217.177])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UmOMO-0007pb-KH
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Jun 2013 13:11:41 +0000
Received: by mail-lb0-f177.google.com with SMTP id 10so7007287lbf.36
for <bitcoin-development@lists.sourceforge.net>;
Tue, 11 Jun 2013 06:11:33 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.120.133 with SMTP id lc5mr7414013lab.76.1370956293802;
Tue, 11 Jun 2013 06:11:33 -0700 (PDT)
Received: by 10.112.2.8 with HTTP; Tue, 11 Jun 2013 06:11:33 -0700 (PDT)
Date: Tue, 11 Jun 2013 15:11:33 +0200
Message-ID: <CAKaEYhJ+v0NfbzVEDEUh69D-n_4=Nd544fsm0a++QwsqcS3RVw@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e01176919e50f4504dee0a249
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
(melvincarvalho[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: 1UmOMO-0007pb-KH
Subject: [Bitcoin-development] Bitcoin addresses -- opaque or not
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, 11 Jun 2013 13:11:42 -0000
--089e01176919e50f4504dee0a249
Content-Type: text/plain; charset=ISO-8859-1
There was some confusion on IRC as to whether bitcoin addresses are opaque
or not.
https://en.bitcoin.it/wiki/Address
For the sake of argument let's say that opaque means that you can tell
nothing about the address by examining the characters.
My understanding was that they are NOT opaque, and that if that has
changed, it will invalidate much at least some wiki page, for examples at
least some of the following would now be false:
--------
"A Bitcoin address, or simply address, is an identifier of 27-34
alphanumeric characters" -- FALSE
"with the number 1 or 3" -- FALSE
"you can send bitcoins to a person by sending bitcoins to one of their
addresses" -- FALSE
"Addresses are created simply by generating random numbers and then
performing mathematical operations to derive matching pairs of "public" and
"private" keys" -- FALSE
"The probability that a mistyped address is accepted as being valid is 1 in
232, that is, approximately 1 in 4.29 billion" -- FALSE
"If you would like to validate a Bitcoin address in an application, it is
advisable to use a method from this thread rather than to just check for
string length, allowed characters, or that the address starts with a 1 or
3." -- FALSE
"For most properly-generated Bitcoin addresses, there is at least one
secret number known as a private key" -- FALSE
"They consist of random digits and uppercase and lowercase letters, with
the exception that the uppercase letter "O", uppercase letter "I",
lowercase letter "l", and the number "0" are never used to prevent visual
ambiguity" -- FALSE
"Some Bitcoin addresses can be shorter than 34 characters (as few as 27)"
-- FALSE
"Several of the characters inside a Bitcoin address are used as a checksum
so that typographical errors can be automatically found and rejected" --
FALSE
"The checksum also allows Bitcoin software to confirm that a 33-character
(or shorter) address is in fact valid and isn't simply an address with a
missing character" -- FALSE
--------
I also here that there is a LIKELY change from the base58 encoding ... when
was this established?
There's either been some bit changes to the fundamentals of bitcoin here or
there's been some misunderstandings. It would be good to clear things up
as to what exactly an address is now beleived to be, and reflect that in
the wiki.
--089e01176919e50f4504dee0a249
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div><div>There was some confusion on IRC as to =
whether bitcoin addresses are opaque or not.<br><br><a href=3D"https://en.b=
itcoin.it/wiki/Address">https://en.bitcoin.it/wiki/Address</a><br><br></div=
>
For the sake of argument let's say that opaque means that you can tell =
nothing about the address by examining the characters.<br><br></div>My unde=
rstanding was that they are NOT opaque, and that if that has changed, it wi=
ll invalidate much at least some wiki page, for examples at least some of t=
he following would now be false:<br>
<br>--------<br>"A Bitcoin address, or simply address, is an identifie=
r of 27-34 alphanumeric characters" -- FALSE<br><br>"with the num=
ber 1 or 3" -- FALSE<br><br>"you can send bitcoins to a person by=
sending bitcoins to one of their addresses" -- FALSE<br>
<br>"Addresses are created simply by generating random numbers and the=
n performing mathematical operations to derive matching pairs of "publ=
ic" and "private" keys" -- FALSE<br><br>"The proba=
bility that a mistyped address is accepted as being valid is 1 in 232, that=
is, approximately 1 in 4.29 billion" -- FALSE<br>
<br>"If you would like to validate a Bitcoin address in an application=
, it is advisable to use a method from this thread rather than to just chec=
k for string length, allowed characters, or that the address starts with a =
1 or 3." -- FALSE<br>
<br>"For most properly-generated Bitcoin addresses, there is at least =
one secret number known as a private key" -- FALSE<br><br>"They c=
onsist of random digits and uppercase and lowercase letters, with the excep=
tion that the uppercase letter "O", uppercase letter "I"=
;, lowercase letter "l", and the number "0" are never u=
sed to prevent visual ambiguity" -- FALSE<br>
<br>"Some Bitcoin addresses can be shorter than 34 characters (as few =
as 27)" -- FALSE<br><br>"Several of the characters inside a Bitco=
in address are used as a checksum so that typographical errors can be autom=
atically found and rejected" -- FALSE<br>
<br>"The checksum also allows Bitcoin software to confirm that a 33-ch=
aracter (or shorter) address is in fact valid and isn't simply an addre=
ss with a missing character" -- FALSE<br>--------<br><br></div>I also =
here that there is a LIKELY change from the base58 encoding ... when was th=
is established?=A0 <br>
<br>There's either been some bit changes to the fundamentals of bitcoin=
here or there's been some misunderstandings.=A0 It would be good to cl=
ear things up as to what exactly an address is now beleived to be, and refl=
ect that in the wiki.<br>
<br></div><br></div>
--089e01176919e50f4504dee0a249--
|
