{"type":"rich","version":"1.0","author_name":"npub10z4xjfgftd3fm9dfu7dw6mkemgyhxgumcmhd7yd0ggjq7rsaw4wqa3xfzw","author_url":"https://nostr.ae/npub10z4xjfgftd3fm9dfu7dw6mkemgyhxgumcmhd7yd0ggjq7rsaw4wqa3xfzw","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-06-18\n📝 Original message:Let me take a pass at explaining how I see this.\n\n1) Code changes to Bitcoin Core that don't change consensus:  Wladimir is\nthe decider but he works under a process that is well understood by\ndevelopers on the project in which he takes under reasonable consideration\nother technical opinions and prefers to have clear agreement among them.\n\n2) Changes to the consensus rules: As others have said, this isn't anyone's\ndecision for anyone else.  It's up to each individual user as to what code\nthey run and what rules they enforce.  So then why is everyone so up in\narms about what Mike and Gavin are proposing if everyone is free to decide\nfor themselves?  I believe that each individual user should adhere to the\nprinciple that there should be no changes to the consensus rules unless\nthere is near complete agreement among the entire community, users,\ndevelopers, businesses miners etc.  It is not necessary to define complete\nagreement exactly because every individual person decides for themselves.\nI believe that this is what gives Bitcoin, or really any money, its value\nand what makes it work, that we all agree on exactly what it is.  So I\nbelieve that it is misleading and bad for Bitcoin to tell users and\nbusiness that you can just choose without concern for everyone else which\ncode you'll run and we'll see which one wins out.  No.  You should run the\nold consensus rules (on any codebase you want) until you believe that\npretty much everyone has consented to a change in the rules.  It is your\nchoice, but I think a lot of people that have spent time thinking about the\nphilosophy of consensus systems believe that when the users of the system\nhave this principle in mind, it's what will make the system work best.\n\n3) Code changes to Core that do change consensus: I think that Wladimir,\nall the other committers besides Gavin, and almost all of the other\ndevelopers on Core would defer to #2 above and wait for its outcome to be\nclear before considering such a code change.\n\nI'm sure my description of point 2 is not the most eloquent or clear, but\nmaybe someone else can try to elucidate this principle if they've grasped\nwhat I'm trying to say.\n\n\n\n\n\nOn Thu, Jun 18, 2015 at 1:04 PM, \u003cjustusranvier at riseup.net\u003e wrote:\n\n\u003e -----BEGIN PGP SIGNED MESSAGE-----\n\u003e Hash: SHA512\n\u003e\n\u003e On 2015-06-18 16:28, Jeff Garzik wrote:\n\u003e \u003e This is an engineering list.  The quote precisely describes how the\n\u003e \u003e bitcoin\n\u003e \u003e consensus system functions.\n\u003e \u003e\n\u003e \u003e Users' choice is largely binary:  Follow the rules, or bitcoin software\n\u003e \u003e ignores you.\n\u003e\n\u003e\n\u003e Software engineers should understand that they have a binary choice:\n\u003e produce the software that your customers want, or the world will ignore\n\u003e your software.\n\u003e\n\u003e There is *no inherent value* to Bitcoin's software rules. The only value\n\u003e that is exists is that produced by the individuals who voluntarily\n\u003e choose to run the software.\n\u003e\n\u003e Failing to account for all design requirements is bad engineering.\n\u003e Nobody cares about the design features of a bridge to nowhere.\n\u003e\n\u003e -----BEGIN PGP SIGNATURE-----\n\u003e Version: GnuPG v2\n\u003e\n\u003e iQIcBAEBCgAGBQJVgvoDAAoJECpf2nDq2eYj0h4P/0YaTsS963qpb63zvB6WlIPS\n\u003e 2lhCJ9FtAd3II5Et+5c/cisfJ9YI2OnM0y8nQpyB9NEOeueN1L1sLFcayE5aHASd\n\u003e EgF7F81AhQD2iSIVwQNs2qAzrZNC2/Nx+nBzBDcrgZ6gRiPpQdsNLy2p0OuZdOgX\n\u003e yG4xl6tKADB2kNi6tVPtZqUC300uQHvggtm+pexYilT0ojEbeVHCoDV40MNDZC2h\n\u003e 1kcdTnGU2SHJJqeZN2vChJCOMfhmK4JwKgoz7JRXe/GHkUUJKriE6Kb7SVczii9e\n\u003e 9qfcosbnR3gjATMoHFYuJX/nsUx52Q1LM9eQgvE8Ml+6Mim5bj2KCJFh7YISxSq9\n\u003e FhDujfZFCRRQLPJCSkEUePxU/LS7lmoTZXYl3Zz1j9zbq4ncpRHpIFy9QX6iIqK6\n\u003e Dursnge9ELQwB+H6HoosWRzxOZyo+oiGj17OngJvZYcvzrc2wjHbpZfVqSkmZepU\n\u003e SfJZ64O7yjjXjITwhOc4XF2drzvhsjTsHH5BIwdbCn82SoCkJIwXraj7sxIundli\n\u003e LUJBPiAE0csdmsvW/2kkxLsd9JwTw9lJ9Pf8fiqH3itgrkPkO5mf10DPPnay1SNk\n\u003e Wnm1bAJ05WnKXSo0m0SzaFgZkdfFuhWR4fieSzhLpa+s/HHj18NZvJCmCBR6ic9G\n\u003e 0A+51wwSZnAdMIw7lwIb\n\u003e =r4Co\n\u003e -----END PGP SIGNATURE-----\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\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-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150618/bb6ae32f/attachment.html\u003e"}