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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tamas@bitsofproof.com>) id 1YMddY-0000Bm-F8
for bitcoin-development@lists.sourceforge.net;
Sat, 14 Feb 2015 14:24:00 +0000
X-ACL-Warn:
Received: from wp059.webpack.hosteurope.de ([80.237.132.66])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1YMddW-0003mL-8Y
for bitcoin-development@lists.sourceforge.net;
Sat, 14 Feb 2015 14:24:00 +0000
Received: from [37.143.74.116] (helo=[192.168.0.100]); authenticated
by wp059.webpack.hosteurope.de running ExIM with esmtpsa
(TLS1.0:RSA_AES_128_CBC_SHA1:16)
id 1YMddN-0003OE-Ne; Sat, 14 Feb 2015 15:23:49 +0100
Content-Type: multipart/signed;
boundary="Apple-Mail=_0E121890-22E4-4DE9-B27C-BECB7D5AA04D";
protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Tamas Blummer <tamas@bitsofproof.com>
In-Reply-To: <20150214131320.GA26731@savin.petertodd.org>
Date: Sat, 14 Feb 2015 15:23:47 +0100
Message-Id: <3D4F2E23-CADE-4FE7-B960-3F79815E868C@bitsofproof.com>
References: <CABm2gDpReRty6TdfMDssjF27XgC_SYs_U__SFBNdsYW24Mzh8w@mail.gmail.com>
<54CC0E1D.7030409@voskuil.org>
<CABm2gDqM6q24tPEBKSHbbVQu-mvfV37PNc4hD=VjyRHk2jujZw@mail.gmail.com>
<54D0414F.6030806@voskuil.org>
<CABm2gDo_sYjNWU6EEsKmOXt5uUu87Lj1oFzqio79MxSx2SYrNg@mail.gmail.com>
<54DE7601.4070509@voskuil.org>
<CABm2gDpt60B=Sf_2X9xt4fPH7x4fff7K4h36XfosHigV5tP+4Q@mail.gmail.com>
<54DF07A5.1060004@voskuil.org>
<CABm2gDoS+XOR7Ugt91kNWNdvwsb1_Zb-aO0sma_Xps2Sx-0N5g@mail.gmail.com>
<54DF2E80.5060506@voskuil.org>
<20150214131320.GA26731@savin.petertodd.org>
To: Peter Todd <pete@petertodd.org>
X-Mailer: Apple Mail (2.1878.6)
X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1423923838;
0957cf39;
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 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [80.237.132.66 listed in list.dnswl.org]
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1YMddW-0003mL-8Y
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
libbitcoin@lists.dyne.org
Subject: Re: [Bitcoin-development] On Rewriting Bitcoin (was Re:
[Libbitcoin] Satoshi client: is a fork past 0.10 possible?)
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: Sat, 14 Feb 2015 14:24:00 -0000
--Apple-Mail=_0E121890-22E4-4DE9-B27C-BECB7D5AA04D
Content-Type: multipart/alternative;
boundary="Apple-Mail=_25250DA5-E021-449D-A3D3-C4C4CE1A5E22"
--Apple-Mail=_25250DA5-E021-449D-A3D3-C4C4CE1A5E22
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
Peter,
You did not address me but libbitcoin. Since our story and your =
evaluation is probably similar, I chime in.
On Feb 14, 2015, at 2:13 PM, Peter Todd <pete@petertodd.org> wrote:
> So stop wasting your time. Help get the consensus critical code out of
> Bitcoin Core and into a stand-alone libconsensus library,
We have seen that the consensus critical code practically extends to =
Berkley DB limits or OpenSSL laxness, therefore
it is inconceivable that a consensus library is not the same as Bitcoin =
Core, less its P2P service rules, wallet and RPC server.
On Feb 14, 2015, at 2:13 PM, Peter Todd <pete@petertodd.org> wrote:
>=20
> Or you can be stereotypical programmers and dick around on github for
> the next ten years chasing stupid consensus bugs in code no-one uses.
The Core code base is unfriendly to feature extensions because of its =
criticality, legacy design and ancient technology. It is also a =
commodity
that the ecosystem takes for granted and free.=20
I honestly admire the core team that works and progresses within these =
limits and perception.
I am not willing to work within the core=92s legacy technology limits. =
Does it mean I am dicking around? I think not.
It was my way to go down the rabbit hole by re-digging it and I created =
successful commercial products on the way.
It is entirely rational for me to focus on innovation that uses the core =
as a border router for this block chain.=20
I am rather thankful for the ideas of the side chains, that enable =
innovation that is no longer measured on unapologetic compatibility with =
a given code base, but its services to end user.
Tamas Blummer
Bits of Proof
--Apple-Mail=_25250DA5-E021-449D-A3D3-C4C4CE1A5E22
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div><div>Peter,</div><div><br></div><div>You did =
not address me but libbitcoin. Since our story and your evaluation is =
probably similar, I chime in.</div><div><br></div><div>On Feb 14, 2015, =
at 2:13 PM, Peter Todd <<a =
href=3D"mailto:pete@petertodd.org">pete@petertodd.org</a>> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">So stop wasting your time. Help get the consensus critical =
code out of<br>Bitcoin Core and into a stand-alone libconsensus =
library,</blockquote></div><div><br></div><div>We have seen that the =
consensus critical code practically extends to Berkley DB limits or =
OpenSSL laxness, therefore</div><div>it is inconceivable that a =
consensus library is not the same as Bitcoin Core, less its P2P service =
rules, wallet and RPC =
server.</div><div><br></div><div><br></div><div><div>On Feb 14, 2015, at =
2:13 PM, Peter Todd <<a =
href=3D"mailto:pete@petertodd.org">pete@petertodd.org</a>> =
wrote:</div><blockquote type=3D"cite"><br>Or you can be stereotypical =
programmers and dick around on github for<br>the next ten years chasing =
stupid consensus bugs in code no-one =
uses.<br></blockquote></div><div><br></div><div><br></div><div>The Core =
code base is unfriendly to feature extensions because of its =
criticality, legacy design and ancient technology. It is also a =
commodity</div><div>that the ecosystem takes for granted and =
free. </div><div><br></div><div>I honestly admire the core team =
that works and progresses within these limits and =
perception.</div><div><br></div><div>I am not willing to work within the =
core=92s legacy technology limits. Does it mean I am dicking around? I =
think not.</div><div>It was my way to go down the rabbit hole by =
re-digging it and I created successful commercial products on the =
way.</div><div><br></div><div>It is entirely rational for me to focus on =
innovation that uses the core as a border router for this block =
chain. </div><div><br></div><div>I am rather thankful for the ideas =
of the side chains, that enable innovation that is no longer measured on =
unapologetic compatibility with a given code base, but its services to =
end user.</div><div><br></div><div apple-content-edited=3D"true">
<div 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;">Tamas =
Blummer</div><div 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;">Bits of Proof</div></div><div><div><br></div></div></body></html>=
--Apple-Mail=_25250DA5-E021-449D-A3D3-C4C4CE1A5E22--
--Apple-Mail=_0E121890-22E4-4DE9-B27C-BECB7D5AA04D
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 - https://gpgtools.org
iQEcBAEBCgAGBQJU31pzAAoJEPZykcUXcTkcs7wIAKiuvMoz5tmUYEh9YseclYGI
20g4sjQXFvhHZh9xvMPzhdpkykcw47JFQ/s5I1txFHNPTntNJ/9KA4PRgZNtB/b+
j3foN2f3C7ShVuMBbL9sh8aTdYcUS6LdDaeOWQVFyhIjDi+8xz6BNlMiXbtVDdT8
CfHXWnmumwth5vuHYgoiQxhztqu90xwO8b7ji6Aqmhjfy/j7kB/RGkI0RPs0CTZf
EdLV0Hw8Uvd/hiac1ZdZANY7OByon+20kmMmAjKkiu8DqNrbbbe8YJDHkD4rTKqN
tjjKIg8r28nUTw8NiFYg28V4AKzAe0FHW93NmGUDQiAmqamwTyFa23EvweqhY/c=
=j/tO
-----END PGP SIGNATURE-----
--Apple-Mail=_0E121890-22E4-4DE9-B27C-BECB7D5AA04D--
|
