{"type":"rich","version":"1.0","author_name":"npub10plv6jx6pktpp5ezldnus6kj8ffg045g2kdjl78w23njrlveqy5s3pfaef","author_url":"https://nostr.ae/npub10plv6jx6pktpp5ezldnus6kj8ffg045g2kdjl78w23njrlveqy5s3pfaef","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-07-22\n📝 Original message:So, if consensus shouldn't really be between the developers (which is \nfine), should we empower users to control consensus? I've been working \non a fork framework anyway, which can support reasonably arbitrary \nconsensus changes (currently against block height, but moving towards \nblock time). Theoretically it could be modified to load consensus \nparameters (which block size would have to be added to) from disk at \nstartup, rather than having them hard-coded.\n\nIs that considered desirable? Will raise as a PR if so. If not, where do \nwe draw a line between developer and user consensus?\n\nRoss\n\nOn 22/07/2015 17:52, Pieter Wuille via bitcoin-dev wrote:\n\u003e\n\u003e Hello all,\n\u003e\n\u003e I'd like to talk a bit about my view on the relation between the \n\u003e Bitcoin Core project, and the consensus rules of Bitcoin.\n\u003e\n\u003e I believe it is the responsibility of the maintainers/developers of \n\u003e Bitcoin Core to create software which helps guarantee the security and \n\u003e operation of the Bitcoin network.\n\u003e\n\u003e In addition to normal software maintenance, bug fixes and performance \n\u003e improvements, this includes DoS protection mechanism deemed necessary \n\u003e to keep the network operational. Sometimes, such (per-node \n\u003e configurable) policies have had economic impact, for example the dust \n\u003e rule.\n\u003e\n\u003e This also includes participating in discussions about consensus \n\u003e changes, but not the responsibility to decide on them - only to \n\u003e implement them when agreed upon. It would be irresponsible and \n\u003e dangerous to the network and thus the users of the software to risk \n\u003e forks, or to take a leading role in pushing dramatic changes. Bitcoin \n\u003e Core developers obviously have the ability to make any changes to the \n\u003e codebase or its releases, but it is still up to the community to \n\u003e choose to run that code.\n\u003e\n\u003e Some people have called the prospect of limited block space and the \n\u003e development of a fee market a change in policy compared to the past. I \n\u003e respectfully disagree with that. Bitcoin Core is not running the \n\u003e Bitcoin economy, and its developers have no authority to set its \n\u003e rules. Change in economics is always happening, and should be \n\u003e expected. Worse, intervening in consensus changes would make the \n\u003e ecosystem more dependent on the group taking that decision, not less.\n\u003e\n\u003e So to point out what I consider obvious: if Bitcoin requires central \n\u003e control over its rules by a group of developers, it is completely \n\u003e uninteresting to me. Consensus changes should be done using consensus, \n\u003e and the default in case of controversy is no change.\n\u003e\n\u003e ===\n\u003e\n\u003e My personal opinion is that we - as a community - should indeed let a \n\u003e fee market develop, and rather sooner than later, and that \"kicking \n\u003e the can down the road\" is an incredibly dangerous precedent: if we are \n\u003e willing to go through the risk of a hard fork because of a fear of \n\u003e change of economics, then I believe that community is not ready to \n\u003e deal with change at all. And some change is inevitable, at any block \n\u003e size. Again, this does not mean the block size needs to be fixed \n\u003e forever, but its intent should be growing with the evolution of \n\u003e technology, not a panic reaction because a fear of change.\n\u003e\n\u003e But I am not in any position to force this view. I only hope that \n\u003e people don't think a fear of economic change is reason to give up \n\u003e consensus.\n\u003e\n\u003e -- \n\u003e Pieter\n\u003e\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150722/1b3907fd/attachment.html\u003e"}