📅 Original date posted:2015-02-14
📝 Original message: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 at 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 at 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’s 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150214/e52a0ac4/attachment.html>;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150214/e52a0ac4/attachment.sig>;
Tamas Blummer [ARCHIVE] /
npub1cc…ex8m8
2023-06-07 15:30:33
in reply to nevent1q…lm85
Author Public Key
npub1ccegg9n9lnx6huppxg43m95488yur7pfemkn3pz0agjws5ffvtts0ex8m8Published at
2023-06-07 15:30:33Event JSON
{
"id": "685be10482d59fad1d24994daa4990ac642ad3497a830d5282c36d597d4a7816",
"pubkey": "c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7",
"created_at": 1686151833,
"kind": 1,
"tags": [
[
"e",
"a1e27a9e8f5d88bf32b6a112984bbe10158121e645475e7be21e08ccaa36e778",
"",
"root"
],
[
"e",
"cd1d1a585ae0dbee9edbe482b4671b22379b4d1b243e5ba539837ccb2878cecf",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "📅 Original date posted:2015-02-14\n📝 Original message:Peter,\n\nYou did not address me but libbitcoin. Since our story and your evaluation is probably similar, I chime in.\n\nOn Feb 14, 2015, at 2:13 PM, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\n\u003e So stop wasting your time. Help get the consensus critical code out of\n\u003e Bitcoin Core and into a stand-alone libconsensus library,\n\n\nWe have seen that the consensus critical code practically extends to Berkley DB limits or OpenSSL laxness, therefore\nit is inconceivable that a consensus library is not the same as Bitcoin Core, less its P2P service rules, wallet and RPC server.\n\n\nOn Feb 14, 2015, at 2:13 PM, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\u003e \n\u003e Or you can be stereotypical programmers and dick around on github for\n\u003e the next ten years chasing stupid consensus bugs in code no-one uses.\n\n\n\nThe Core code base is unfriendly to feature extensions because of its criticality, legacy design and ancient technology. It is also a commodity\nthat the ecosystem takes for granted and free. \n\nI honestly admire the core team that works and progresses within these limits and perception.\n\nI am not willing to work within the core’s legacy technology limits. Does it mean I am dicking around? I think not.\nIt was my way to go down the rabbit hole by re-digging it and I created successful commercial products on the way.\n\nIt is entirely rational for me to focus on innovation that uses the core as a border router for this block chain. \n\nI 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.\n\nTamas Blummer\nBits of Proof\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150214/e52a0ac4/attachment.html\u003e\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 496 bytes\nDesc: Message signed with OpenPGP using GPGMail\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150214/e52a0ac4/attachment.sig\u003e",
"sig": "4e9b107fb2960ddf35b1b3eb69a0e1779b44a1497db28c364aea9c49ab5e885c5e130ccc87a0943b6a8f5fd642d339782a4830c72293c9c433a738bf72d2810a"
}