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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tamas@bitsofproof.com>) id 1WcfRv-00042Y-NI
for bitcoin-development@lists.sourceforge.net;
Tue, 22 Apr 2014 18:29:43 +0000
X-ACL-Warn:
Received: from wp059.webpack.hosteurope.de ([80.237.132.66])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WcfRs-00058C-9o
for bitcoin-development@lists.sourceforge.net;
Tue, 22 Apr 2014 18:29:43 +0000
Received: from [37.143.74.116] (helo=[192.168.0.104]); authenticated
by wp059.webpack.hosteurope.de running ExIM with esmtpsa
(TLS1.0:RSA_AES_128_CBC_SHA1:16)
id 1WcfRl-0004jl-FT; Tue, 22 Apr 2014 20:29:33 +0200
Content-Type: multipart/signed;
boundary="Apple-Mail=_5522F33B-E8BB-4F45-B7F5-D63FEEE3A232";
protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Tamas Blummer <tamas@bitsofproof.com>
In-Reply-To: <CABh=4qPsR1YbhJDeAPjr37Zjqawo9ZFAH43scFnEg7p9a7EkeQ@mail.gmail.com>
Date: Tue, 22 Apr 2014 20:29:50 +0200
Message-Id: <F292CC2F-BAA7-45ED-801E-1475D94632AF@bitsofproof.com>
References: <CAC7yFxSE8-TWPN-kuFiqdPKMDuprbiVJi7-z-ym+AUyA_f-xJw@mail.gmail.com>
<CABh=4qNaJht-MnnjEguZ=UOuXN3uQ-s4-dkDUVErbHj6W44J_g@mail.gmail.com>
<1927948.OEZHQcsQ9n@crushinator> <2025496.b5Y3n7qx8B@crushinator>
<1582E990-4E14-4EF7-9C9C-AA505B815104@bitsofproof.com>
<53568B87.8040009@monetize.io>
<11528A13-5D66-4D2B-BEE0-1C26F9987BC8@bitsofproof.com>
<CABh=4qPsR1YbhJDeAPjr37Zjqawo9ZFAH43scFnEg7p9a7EkeQ@mail.gmail.com>
To: jan.moller@gmail.com
X-Mailer: Apple Mail (2.1874)
X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1398191380;
1d4dc40c;
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WcfRs-00058C-9o
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Presenting a BIP for Shamir's Secret
Sharing of Bitcoin private keys
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, 22 Apr 2014 18:29:43 -0000
--Apple-Mail=_5522F33B-E8BB-4F45-B7F5-D63FEEE3A232
Content-Type: multipart/alternative;
boundary="Apple-Mail=_40846A90-2C83-4FD2-807E-AAE35C4F72E8"
--Apple-Mail=_40846A90-2C83-4FD2-807E-AAE35C4F72E8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=iso-8859-1
Yes, it is current norm. I am questioning if we should hang on to it in =
BIPs.
I see testnet as a tool for a certain type of testing. Its existence is =
likely a consequence of Satoshi not writing unit tests and having =
automated integration tests, but creating a shadow chain to try things =
out, mostly manually.
I do not say testnet (as we know) would not be useful for certain tests. =
E.g. as we developed myTREZOR with slush it was useful to have a shared =
chain with worthless tokens and transactions we can both refer to. =
However for our automated tests chains-in-a-box are better as we can =
easily create and exactly re-create wierd situations on-the-fly.
While talking about BIP32 hierarchy use, several people argued to use a =
level of the hierarchy to identify the chain the key is used on. That =
level could identify testnet but as well an alt coin chain.
Above leads me thinking that testnet is far less important than to be =
addressed in every future BIP.
Regards,
Tamas Blummer
http://bitsofproof.com
On 22.04.2014, at 19:07, Jan M=F8ller <jan.moller@gmail.com> wrote:
> Treating testnet differently is quite the norm, we have that in BIP =
32, 38, 70, SIPA private keys (no BIP for that I guess), bitcoin =
addresses etc. At the same time none of them define values for alt coins =
as far as I recall.
>=20
>=20
--Apple-Mail=_40846A90-2C83-4FD2-807E-AAE35C4F72E8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=iso-8859-1
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Yes, =
it is current norm. I am questioning if we should hang on to it in =
BIPs.<div><br></div><div>I see testnet as a tool for a certain type of =
testing. Its existence is likely a consequence of Satoshi not writing =
unit tests and having automated integration tests, but creating a shadow =
chain to try things out, mostly manually.</div><div><br></div><div>I do =
not say testnet (as we know) would not be useful for certain tests. E.g. =
as we developed myTREZOR with slush it was useful to have a shared chain =
with worthless tokens and transactions we can both refer to. However for =
our automated tests chains-in-a-box are better as we can easily create =
and exactly re-create wierd situations =
on-the-fly.</div><div><br></div><div>While talking about BIP32 hierarchy =
use, several people argued to use a level of the hierarchy to identify =
the chain the key is used on. That level could identify testnet but as =
well an alt coin chain.</div><div><br></div><div>Above leads me thinking =
that testnet is far less important than to be addressed in every future =
BIP.</div><div><div apple-content-edited=3D"true"><br style=3D"color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; orphans: 2; widows: 2;"><span =
style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: =
2; float: none; display: inline !important;">Regards,</span><br =
style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: =
2;"><br style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: =
2;"><span style=3D"color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; =
widows: 2; float: none; display: inline !important;">Tamas =
Blummer</span><span style=3D"color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br style=3D"color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; orphans: 2; widows: 2;"><span =
style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: =
2; float: none; display: inline !important;"><a =
href=3D"http://bitsofproof.com">http://bitsofproof.com</a></span>
</span></div>
<br><div><div>On 22.04.2014, at 19:07, Jan M=F8ller <<a =
href=3D"mailto:jan.moller@gmail.com">jan.moller@gmail.com</a>> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr">Treating testnet differently is quite the =
norm, we have that in BIP 32, 38, 70, SIPA private keys (no BIP for that =
I guess), bitcoin addresses etc. At the same time none of them define =
values for alt coins as far as I recall.</div>
<div class=3D"gmail_extra"><br><br></div>
</blockquote></div><br></div></body></html>=
--Apple-Mail=_40846A90-2C83-4FD2-807E-AAE35C4F72E8--
--Apple-Mail=_5522F33B-E8BB-4F45-B7F5-D63FEEE3A232
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJTVrUeAAoJEPZykcUXcTkc3CUIAJ/0Vh69ntF/sPXKY5SBsGqL
rBRrgfxvuG+P4GgTqpHI4q4avhv/tUTha5YWLJEhM+Etpf6ZNsxO8PF27guYBPi1
sUV+dUsxbH0W+debRI6fjVMQ3w0i/pERSfpZctl+NAC4zoO82PXuX+9CCynDPoks
pxse12IhyTcLMvwQDQsbdNLw1ErE8rWPQEARbbmYd4o9+GRZC0+OknzUfA0ZJaKs
iajyAjO2pCxG12BB4HZgVf/byEGQpwT88cnMASHBoIgmqI+DqllHIzPoSQ8UyWQV
ezZMyw/nb66NNhF6DU6pWYDfNWScEWY3GvaS8kan2SOkmsIcXL/13HX8NqSSEK8=
=gqci
-----END PGP SIGNATURE-----
--Apple-Mail=_5522F33B-E8BB-4F45-B7F5-D63FEEE3A232--
|
