From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 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: <54CC0E1D.7030409@voskuil.org> <54D0414F.6030806@voskuil.org> <54DE7601.4070509@voskuil.org> <54DF07A5.1060004@voskuil.org> <54DF2E80.5060506@voskuil.org> <20150214131320.GA26731@savin.petertodd.org> To: Peter Todd 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 , 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 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
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:

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. 

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. 

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-- --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--