{"type":"rich","version":"1.0","author_name":"npub1ts9hljj3l4yrpdxelpqdup3l46lw40fmkhw3rr0feh6s5ml247vqerfl5y","author_url":"https://nostr.ae/npub1ts9hljj3l4yrpdxelpqdup3l46lw40fmkhw3rr0feh6s5ml247vqerfl5y","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-06-18\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n\nOn Thu, Jun 18, 2015 at 12:00:17PM +0200, Mike Hearn wrote:\n\n\u003e Core is in the weird position where there's no decision making ability at\n\u003e all, because anyone who shows up and shouts enough can generate\n\u003e 'controversy', then Wladimir sees there is disagreement and won't touch the\n\u003e issue in question. So it just runs and runs and *anyone* with commit access\n\u003e can then block any change.\n\nBitcoin Core is completely different from your average open source project in one aspect: where it concerns consensus.\n\nLike in any open source project there is lots of decision making ability for code changes. I'd say look at the changelog for e.g. 0.11 https://github.com/bitcoin/bitcoin/blob/0.11/doc/release-notes.md#0110-change-log, or follow pull requests for a while, to see how many decisions about changes are made from day to day. No, I'm not sitting on my hands, and so is none of the other contributors that you'd like to get rid of.\n\nConsensus changes are *much* more difficult, on the other hand. Even relatively straightforward softforks come with a long discussion process (see BIP62, BIP66). A hardfork is hard to do at the best of times (everyone needs to upgrade their software!), and simply not possible if almost the entire technical community disagrees with you.\n\nBitcoin is supposed to be a robust, global, decentralized network beyond anyone's control. It makes *no sense* to try to run it as a dictatorship. This would create a handy central position where power can be applied, pushing through changes to the behavior of the system, either by force or other ways of motivation. I refuse to take part in that.\n\nHence, anything that is controversial needs to be considered really carefully. If I suddenly start making changes to the consensus code without full agreement, by all means take away my commit privileges.\n\n(a major reason for the ongoing libconsensus work is to separate \"Bitcoin Core, the node software\" and \"The Bitcoin Consensus\" along clear lines, to avoid this kind of nasty confusion)\n\nWladimir\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1\n\niQEcBAEBCgAGBQJVgqfOAAoJEHSBCwEjRsmmFT8H/Rkm29AhLhT8R1Vx8oKUIzID\n+NB7tOps3lIilkDQIC5zHSknx5iugrrAdRf1w7qPj/o8+xhCZw9ruu8eIq+djkRQ\ntvzbHil2pqgT3VHriRlY4lvlmu2NmBcYrAuX9sDhUHBo6cwGajfKMJPfE0haK3K4\n7EmfdGXJYJmiBnhE6ikOiU687M2WgsmIGrBDIxeA5wYwVK9Ph8hfcbuj7AHvIMI9\nZNU/V6uhcTjn5wT+6DHGIOxHipYHyAwKb7jKho0XkM6Yi4ORe1mxF5HDtqA0ztta\nmZPNjNrt/ngK20xRbqkb0GtxoyZq38ZF3Bq1gaWl2v9MBBMD5ZxQAvgCNUQFEo0=\n=W26K\n-----END PGP SIGNATURE-----"}
