#Bitcoin #BIP110 #Fork #Governance #BTC 🟠
The attempt to rewrite Bitcoin's rules failed after two blocks
🟢 What the fight was about
BIP-110 wanted to ban writing "non-financial" stuff into the blockchain for a year - images, text, inscriptions, anything that isn't a payment. Back in late 2025, a Bitcoin Core update lifted the old limit, and gigabytes of junk started pouring into the ledger - junk every node is forced to store. Part of the community saw that as debasing the money and wanted to roll it back.
The catch was in how they tried to switch it on. Normally a rule gets approved by miners signaling through blocks, and you need 55%. BIP-110 got 2.53% - 51 blocks out of 2,016. F2Pool refused, the other pools never showed. So supporters went around them with a UASF - activation by nodes, not miners. Nodes running BIP-110 software started rejecting non-signaling blocks, and the chain split.
🟢 Why it all collapsed in 8 hours
Because you can't force a contentious change through against 97% of the hashrate. Nodes can dig in, but it's miners who forge the blocks. The minority broke off, mined two blocks, and was left with no power behind it. Even Saylor wrote: "Bitcoin is working as designed." Ironically, on this one he's right.
The crowd saw the word "fork" and tensed up: a split, free coins, chaos. What actually happened was the network's immune system kicking in - consensus can't be bought and can't be forced, it can only be assembled. And notice the mirror with Ethereum, which has its own staking war right now: there the rules get changed from the top by foundation researchers, here from the bottom by node operators against miners - but the brawl is about the same thing, who's at the wheel.
What touches you directly: BIP-110 has no replay protection, as Ledger warned. Go chasing "fork coins" and you risk accidentally spending your real BTC.
➡️Crouton.digital | About us⬅️
The attempt to rewrite Bitcoin's rules failed after two blocks
On August 8, the network hit block 961,632, and with it the contentious BIP-110 fork went live. Eight hours later it was over: the forked chain mined exactly two blocks and stalled, while the main chain pushed ahead by nearly 48. But the question this whole scuffle raised didn't go anywhere: who actually governs Bitcoin.
🟢 What the fight was about
BIP-110 wanted to ban writing "non-financial" stuff into the blockchain for a year - images, text, inscriptions, anything that isn't a payment. Back in late 2025, a Bitcoin Core update lifted the old limit, and gigabytes of junk started pouring into the ledger - junk every node is forced to store. Part of the community saw that as debasing the money and wanted to roll it back.
The catch was in how they tried to switch it on. Normally a rule gets approved by miners signaling through blocks, and you need 55%. BIP-110 got 2.53% - 51 blocks out of 2,016. F2Pool refused, the other pools never showed. So supporters went around them with a UASF - activation by nodes, not miners. Nodes running BIP-110 software started rejecting non-signaling blocks, and the chain split.
🟢 Why it all collapsed in 8 hours
Because you can't force a contentious change through against 97% of the hashrate. Nodes can dig in, but it's miners who forge the blocks. The minority broke off, mined two blocks, and was left with no power behind it. Even Saylor wrote: "Bitcoin is working as designed." Ironically, on this one he's right.
The crowd saw the word "fork" and tensed up: a split, free coins, chaos. What actually happened was the network's immune system kicking in - consensus can't be bought and can't be forced, it can only be assembled. And notice the mirror with Ethereum, which has its own staking war right now: there the rules get changed from the top by foundation researchers, here from the bottom by node operators against miners - but the brawl is about the same thing, who's at the wheel.
What touches you directly: BIP-110 has no replay protection, as Ledger warned. Go chasing "fork coins" and you risk accidentally spending your real BTC.
➡️Crouton.digital | About us⬅️