{"type":"rich","version":"1.0","author_name":"npub1ac86vemj7ce5z8jyxt39rna3tvwql6xd30ha3vxcd6esysp23d9qrlswfj","author_url":"https://nostr.ae/npub1ac86vemj7ce5z8jyxt39rna3tvwql6xd30ha3vxcd6esysp23d9qrlswfj","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-02-14\n📝 Original message:Strongly with Peter on this.  That its highly complex to maintain strict\nconsensus between bitcoin versions, does not justify consensus rewrite\nexperiments; it tells you that the risk is exponentially worse and people\nshould use and rally around libconsensus.\n\nI would advise any bitcoin ecosystem part, wallet, user to not use software\nwith consensus protocol rw-writes nor variants, you WILL lose money.\n\nYou could view bitcoin as a digital signature algorithm speculatively\ntinkering with the algo is highly prone to binary failure mode and\nunbounded funds loss.\n\nWant to be clear this is not a political nor emotive issue. It is a\ncritical technical requirement for security if users of software people\nwrite.\n\nPlease promote this meme.\n\nAdam\nOn Feb 14, 2015 6:24 AM, \"Tamas Blummer\" \u003ctamas at bitsofproof.com\u003e wrote:\n\n\u003e Peter,\n\u003e\n\u003e You did not address me but libbitcoin. Since our story and your evaluation\n\u003e is probably similar, I chime in.\n\u003e\n\u003e On Feb 14, 2015, at 2:13 PM, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\u003e\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\u003e\n\u003e\n\u003e We have seen that the consensus critical code practically extends to\n\u003e Berkley DB limits or OpenSSL laxness, therefore\n\u003e it is inconceivable that a consensus library is not the same as Bitcoin\n\u003e Core, less its P2P service rules, wallet and RPC server.\n\u003e\n\u003e\n\u003e On Feb 14, 2015, at 2:13 PM, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\u003e\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\u003e\n\u003e\n\u003e\n\u003e The Core code base is unfriendly to feature extensions because of its\n\u003e criticality, legacy design and ancient technology. It is also a commodity\n\u003e that the ecosystem takes for granted and free.\n\u003e\n\u003e I honestly admire the core team that works and progresses within these\n\u003e limits and perception.\n\u003e\n\u003e I am not willing to work within the core’s legacy technology limits. Does\n\u003e it mean I am dicking around? I think not.\n\u003e It was my way to go down the rabbit hole by re-digging it and I created\n\u003e successful commercial products on the way.\n\u003e\n\u003e It is entirely rational for me to focus on innovation that uses the core\n\u003e as a border router for this block chain.\n\u003e\n\u003e I am rather thankful for the ideas of the side chains, that enable\n\u003e innovation that is no longer measured on unapologetic compatibility with a\n\u003e given code base, but its services to end user.\n\u003e\n\u003e Tamas Blummer\n\u003e Bits of Proof\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Dive into the World of Parallel Programming. The Go Parallel Website,\n\u003e sponsored by Intel and developed in partnership with Slashdot Media, is\n\u003e your\n\u003e hub for all things parallel software development, from weekly thought\n\u003e leadership blogs to news, videos, case studies, tutorials and more. Take a\n\u003e look and join the conversation now. http://goparallel.sourceforge.net/\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150214/f093769e/attachment.html\u003e"}