If you’re a Bitcoin holder who doesn’t pore over GitHub pull requests, here’s the one data point that matters: at block 961,632, the BIP-110 soft fork attempt officially entered its signaling phase, and less than a tenth of the network’s hashrate is even bothering to wave the flag. That’s not just low support; it’s a political death sentence in a system that runs on mining consensus.
But here’s the uncomfortable part. A soft fork with near-zero miner backing can still end up costing you money, in fees, in exchange confusion, or in a weeks-long panic over whether your coins are on the ‘right’ chain. Especially when the proposal’s authors keep pushing even after everyone said no. Sound familiar? It should. We’ve been here before.
The Nuts and Bolts of the BIP-110 Brouhaha
BIP-110, for those of you just tuning in, proposes to alter Bitcoin’s consensus rules in a way its supporters argue will improve privacy and scalability, but critics counter it introduces significant systemic risk and breaks compatibility with certain existing smart contracts. The specific technical changes are less important than the political reality: the proposal has been debated for over a year, major Bitcoin Core developers have publicly opposed it, and mining pools representing over 90% of the network (including F2Pool, AntPool, and ViaBTC via their public statements) have signaled they will not activate it voluntarily.
Yet the team behind BIP-110 isn’t backing down. At block 961,632, a specific height chosen for symbolic or timing reasons, they began publishing signals on the blockchain, hoping to trigger a ‘user-activated soft fork’ (UASF) scenario if enough nodes upgrade. That’s a high-stakes gamble, and one that historically has only increased uncertainty for everyday users.
When Miners Walk Away, Holders Get Nervous
Ask anyone who sat through the SegWit2x drama of 2017 or the BCH split. A contentious fork, even a soft one, creates a window for confusion. Exchanges temporarily halt deposits and withdrawals. Wallets scramble to update their code. And scammers inevitably pop up claiming you need to ‘validate’ your coins on a new website. It’s messy, and it’s stressful.
The numbers right now aren’t comforting. According to pooled mining data from Coin.Dance and other trackers, BIP-110-specific signaling has not exceeded 8% of total hashrate as of block 961,700. That’s up from zero, but still miles from the 95% threshold most soft forks need to be considered uncontroversial. And influential voices are piling on. Pierre Rochard of Riot Platforms tweeted that BIP-110 is ‘unnecessary complexity with no clear payoff.’ Bitcoin developer Luke Dashjr called it ‘a dangerous attempt to push changes without broad consensus.’
When the smart money, and the literal expensive mining gear, says no, retail holders should listen. The real risk isn’t that BIP-110 somehow activates against miners’ will. It’s that the months-long fight distracts from actual network development and opens the door for another contentious chain split down the line.
Historical Echoes and the Specter of UASF
The playbook BIP-110’s supporters are running? It’s straight out of the 2017 UASF playbook, when a small but vocal group of users tried to force SegWit activation before miners finally budged. But that worked because SegWit had broad developer and user buy-in, miners were the only holdouts. Here, the opposition is far wider. Miners, developers, and major exchanges have all expressed skepticism. Even some of the most ardent Bitcoin-only advocates are calling it a distraction.
What might actually happen? Best case: low signaling forces the BIP-110 authors to withdraw the proposal and refine it. Worst case: they trigger a node-fork that leaves a tiny chain running an incompatible rule set, think Bitcoin Satoshi’s Vision scale, not Ethereum Classic scale. That tiny chain would likely have negligible value and minimal exchange support, leaving its holders stuck with frozen funds.
In times like these, you’ll see a predictable shift toward self-custody. As we noted with the surge in hardware wallet adoption among Russian users, uncertainty about network rules accelerates the move away from exchanges. For BIP-110, the same dynamic holds: if you’re worried about chain splits, you want to control your private keys before the chaos begins.
What You Should Actually Do Right Now
First, don’t panic. This is noise, not a crisis. The probability that BIP-110 ever activates against miner opposition is vanishingly small. But, and this is the part most news articles skip, you should still take two practical steps:
One: verify that your wallet software is up to date. Most popular wallets (including Bitcoin Core, Electrum, and hardware wallet companions) will quickly patch any risks from a contentious soft fork, but if you’re running outdated software, you could accidentally accept invalid blocks. Two: keep an eye on your exchange. If BIP-110 signaling passes a certain threshold (some exchanges have said they’ll suspend trading if signaling hits 30% of blocks in a difficulty period), prepare for brief withdrawal halts. Move what you can to a wallet you control beforehand.
Also, and I can’t stress this enough, ignore anyone asking you to ‘upgrade’ to a BIP-110 compatible wallet or send coins to a new address for validation. That’s a scam every single time. The Bitcoin you hold today remains valid on the dominant chain regardless of what a small fork does.
The Bottom Line on Block 961,632
BIP-110 at block 961,632 is a textbook example of protocol politics trying to muscle out economics. The miners have spoken. The devs have spoken. The hash rate has spoken. But the proposal’s proponents are not listening, and that refusal to accept reality is what creates real risk for ordinary Bitcoin users. If the signaling campaign fizzles in the next two weeks (as most analysts expect), this becomes a footnote. If it doesn’t, we’re in for a rocky couple of months.
Keep your keys cold, your software fresh, and your panic button covered. In Bitcoin, contested forks usually end with one chain winning and the other fading into irrelevance. The question is whether your patience, and your node, survive the process intact.
Frequently Asked Questions
What is BIP-110 and why is it controversial?
BIP-110 is a proposed Bitcoin improvement that would change the network’s consensus rules. It’s controversial because top developers and a large majority of miners oppose it, calling it risky and unnecessary. The proposal is being pushed via a user-activated soft fork (UASF) attempt despite lacking broad support.
Will BIP-110 cause a split in the Bitcoin blockchain?
Possibly, but not a dangerous one. If very few miners actually follow the new rules, the BIP-110 chain would be tiny and quickly become worthless. The main Bitcoin chain (running the current rules) will continue as normal. The bigger risk is short-term confusion and exchange halts.
Should I sell my Bitcoin because of this fork attempt?
No. Historically, contentious forks that lack miner support have not caused lasting damage to Bitcoin’s price or network. Selling into fear during a minor protocol spat usually hurts more than it helps. The prudent move is to hold and ensure your self-custody setup is solid.
