Why is it that the entire fork wars was framed around big vs small blocks? When it clearly wasn't that at all. It was a clear cut differing of are we going to change the Shelling point of consensus altogether and fork individuals whom otherwise wouldn't know a damn thing about what was going on.. or are we going to maintain the system as it is so that nobody thats already a user gets kicked out of consensus?

Finally starting to really grasp the nuances of the debacle albeit not having it been a lived experience myself.

The entire NY agreement collusion, every exchange and miner, and companies that accepted it at the time wanted an increase of blocksize and it was given that with the new weighted data size limit of segwit but it was clear that wasn't the issue as they still tried to purpose segwit2X (that was dead on the vine with its off by one bug) that you'll need to run OUR version of segwit.

Reply to this note

Please Login to reply.

Discussion

Is is not true Roger Ver wanted bigger blocks and wanted to form b cash as a result ?

I’m not saying what you’ve said is wrong but was it not apart of the fork wars?

From Roger Ver’s account given in “Hijacking Bitcoin”, the big blockers weren’t satisfied by segwit2x either because they anticipate much higher transaction volume. Big blockers want bitcoin to scale on layer 1, instead of via a second layer in the form of Lightning. Roger references a few times where both transaction time and cost became problems and how early failures of Lightning made its ability to solve them questionable.

I understand his misgivings about having a majority of BTC holders never transact either. I agree that keeping those people in (instead of forking them) makes sense, and that it’s up to coiners to make tools and advocate for adoption, so that this majority begins to transact. But his point about UTXOs being a clunky workaround holds , and I’m still unsure about trading security for scale.

Need to read up on the tradeoff in security for scale and how Lightning works these days, tbh. Would love to hear what nostr:nprofile1qqsw4v882mfjhq9u63j08kzyhqzqxqc8tgf740p4nxnk9jdv02u37ncpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3gamnwvaz7tmwdaehgunnv968vcfwdejhgwadg4z thinks.