📅 Original date posted:2015-09-04
📝 Original message:On Friday, September 04, 2015 8:13:18 PM Andy Chase via bitcoin-dev wrote:
> Who makes high-level Bitcoin decisions? Miners, client devs, merchants, or
> users? Let's set up a system where everyone has a say and clear acceptance
> can be reached.
For hardforks (removing consensus rules), economic consensus: people who
accept payment in bitcoins weighted by their actual volume of such payments.
A supermajority subset may arguably be sufficient for some hardforks (which
don't violate Bitcoin's social contract) since they can effectively compel
the remaining economy to comply.
For softforks (adding consensus rules), a majority of miners: they can "51%
attack" miners who don't go along with it.
Anything else does not necessarily need universal agreement, so are
completely up to the whim of individual software projects. If someone doesn't
like a decision in Core (for example), they can safely fork the code. If any
significant amount of people use their fork, then the BIP is accepted whether
or not Core later adopts it.
Note this "system" is really describing a lack of a system - that is, what
naturally must happen for changes to occur. Softforks have a relatively
mature technical method for measuring support and deploying (which I believe
someone else is already working on a BIP describing), but the same thing is
impractical for hardforks. Some formal way to measure actual economic
acceptance seems like a good idea to study, but it needs to be reasonably
accurate so as to not change the outcome from its natural/necessary result.
Luke
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 17:39:38
in reply to nevent1q…vv9v
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nSeen on
wss://relay.nostr.bandPublished at
2023-06-07 17:39:38Event JSON
{
"id": "88237408aa4902dd4d416347db7467fa0f11e688aabf99f517161cfe8ff8411a",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686159578,
"kind": 1,
"tags": [
[
"e",
"9c96b271d28066e4cb9eb50131a2ba9c23f5c1ad1af3e01fa5e76e13c28699d2",
"",
"root"
],
[
"e",
"b26fb3fd454fe5ea7e6259cb43f1b0c196574c5140f669223d574d8925165b28",
"",
"reply"
],
[
"p",
"1b29d94ee81e1ee0479f1db4bc4ac887407bd470a0d7060e76f8ab27fdd57e50"
]
],
"content": "📅 Original date posted:2015-09-04\n📝 Original message:On Friday, September 04, 2015 8:13:18 PM Andy Chase via bitcoin-dev wrote:\n\u003e Who makes high-level Bitcoin decisions? Miners, client devs, merchants, or\n\u003e users? Let's set up a system where everyone has a say and clear acceptance\n\u003e can be reached.\n\nFor hardforks (removing consensus rules), economic consensus: people who \naccept payment in bitcoins weighted by their actual volume of such payments. \nA supermajority subset may arguably be sufficient for some hardforks (which \ndon't violate Bitcoin's social contract) since they can effectively compel \nthe remaining economy to comply.\n\nFor softforks (adding consensus rules), a majority of miners: they can \"51% \nattack\" miners who don't go along with it.\n\nAnything else does not necessarily need universal agreement, so are \ncompletely up to the whim of individual software projects. If someone doesn't \nlike a decision in Core (for example), they can safely fork the code. If any \nsignificant amount of people use their fork, then the BIP is accepted whether \nor not Core later adopts it.\n\nNote this \"system\" is really describing a lack of a system - that is, what \nnaturally must happen for changes to occur. Softforks have a relatively \nmature technical method for measuring support and deploying (which I believe \nsomeone else is already working on a BIP describing), but the same thing is \nimpractical for hardforks. Some formal way to measure actual economic \nacceptance seems like a good idea to study, but it needs to be reasonably \naccurate so as to not change the outcome from its natural/necessary result.\n\nLuke",
"sig": "c362ead6c2c51e2739ddede7492f9da65fcefddd034483d3a115c0f981cc00aa2fd7b1bbe69e0f5a20757a48d181d09509304fd9a0177e3b6e42b6fa3faa5575"
}