Fact Checked by Coinsbeat Editorial Team | Expert Reviewed by Themiya

Bitcoin is having a governance crisis again. Shocking, right? A chart from Jameson Lopp showing a suspicious spike in BIP-110 signaling nodes has ripped open a wound that never really healed after the SegWit2x wars. The question on the table is brutally simple: are those nodes real support, or is someone spinning up cheap Tor instances to manufacture consensus?

Let’s be real. The answer probably doesn’t matter as much as the fight itself does.

What BIP-110 Actually Wants, And Why Core’s Team Already Fired the First Shot

Here’s the thing. This whole mess didn’t start with BIP-110. It started when Bitcoin Core 30.0 shipped in October 2025 and quietly raised the default -datacarriersize to 100,000 bytes and allowed multiple OP_RETURN outputs. For the anti-spam faction inside Bitcoin, that wasn’t a technical tweak. It was a declaration of values.

BIP-110 is the counter-punch. Filed by Dathon Ohm, with Luke-Jr credited for original drafting, the proposal would impose a temporary consensus-layer tightening with some genuinely aggressive constraints:

• New output scripts capped at 34 bytes (except OP_RETURN, which gets 83 bytes)

• Data pushes and witness elements limited to 256 bytes

• Taproot control blocks capped at 257 bytes

• OP_SUCCESS opcodes invalidated, plus executed OP_IF and OP_NOTIF disallowed in Tapscript during the deployment window

That last point is where it gets spicy. These aren’t cosmetic restrictions. They reach directly into Taproot’s upgrade path and would freeze out BitVM-style large Taptrees entirely. Some wallets generating Miniscript would need code updates. In narrow edge cases, the proposal itself acknowledges that funds could be frozen during the window. The BIP-110 site calls that “extremely unlikely.” Opponents call it unacceptable.

The activation design is what makes this a genuine governance fight and not just a forum argument. A modified BIP9 mechanism with a 55% signaling threshold and a deadline around September 1, 2026. That threshold is low. Very low. Standard soft fork expectations historically require something far closer to supermajority hashrate. Activating at 55% means 45% of miners could be producing blocks that the activated chain would reject outright. That’s not a theoretical chain split risk. It’s a concrete one.

Lopp’s Chart, The Sybil Problem, and Why Node Counts Have Always Been Political Theater

Jameson Lopp captioned his chart “Spot the Sybil Attack.” That’s not a subtle framing. He’s explicitly accusing the BIP-110 support campaign of manufacturing visible consensus rather than building real economic weight behind the proposal.

His argument is architectural and it’s hard to dismiss. Running a node costs almost nothing at scale, especially on Tor where addresses are practically free. The chart showed BIP-110 signaling jumping sharply while Bitcoin Knots nodes whipsawed, which is the kind of pattern you’d expect from a coordinated deployment campaign, not organic grassroots adoption spreading person by person.

The data itself is messy depending on where you look:

• Coin Dance (correcting for duplicates and non-listening nodes) shows 23,189 total public nodes, with 17,961 running Core and 5,193 running Knots. Knots sits at roughly 22% of the reachable set.

• Smart Wicked Bitcoin (including listening and non-listening nodes) tracked 22,362 Core v30 nodes, 11,997 Knots nodes, and 10,361 BIP-110 signaling nodes as of March 23.

Same network. Completely different picture depending on methodology. That’s the trick here. The BIP-110 camp can point to the broader count and claim momentum. Critics point to the corrected count and say it’s nowhere close to parity with Core.

Lopp’s deeper point, though, is that this entire argument is beside the point. Bitcoin’s governance has never actually run on node counts. It runs on economic weight: miners, exchanges, custodians, wallet operators. The entities that can actually enforce a rule change with real consequence. Reachable-node tallies represent none of that. They never have. Bitcoin Unlimited learned this the hard way. SegWit2x learned it even harder.

The BIP-110 deployment also got a serious infrastructure boost in early 2026. myNode added a “Bitcoin Knots + BIP110 Custom Bitcoin Version” install option on February 6. RaspiBlitz updated its Knots installer to run a BIP110-enabled build on February 19. The official BIP-110 site lists simplified install paths across Start9, Umbrel, myNode, Parmanode, and Docker, and it explicitly encourages users to run signaling nodes to show support.

Honestly, that’s a coordinated distribution campaign. Whether you call it community organizing or manufactured signaling depends entirely on which side of the OP_RETURN debate you sit on.

The Real Stakes: This Is a Fight About What Bitcoin Is For

Strip away the node charts and the signaling theater and you’re left with a question that Bitcoin has been avoiding for years. Is Bitcoin a monetary network with strict, intentional constraints on how its block space is used? Or is it a general-purpose data layer where the market decides what gets included?

Core 30’s OP_RETURN loosening answered that question in one direction. BIP-110 is an attempt to answer it in the opposite direction, but through a governance mechanism that critics say is both technically risky and politically illegitimate.

The coordination failure scenario is the most likely bad outcome here. If BIP-110 fails to reach 55% miner signaling, which is very possible given that miners, exchanges, and major economic actors have not publicly aligned behind it, you get months of network-wide distraction, a poisoned Taproot development environment, and a governance lesson that nobody wanted to repeat. The real policy question about OP_RETURN spam stays unresolved.

Look, Bitcoin has been here before. The difference this time is the sequence. Core changed the defaults first, which put the anti-spam camp in reactive mode. Reactive governance campaigns in Bitcoin have a bad track record. They rely on visible momentum, like node charts, precisely because they lack the institutional backing that makes soft forks stick.

What Investors Need to Watch Right Now

Most retail participants will ignore this entirely until it becomes a price event. That’s a mistake. Here’s what actually matters from a market perspective:

• Miner signaling data over the next 90 days is the only metric worth tracking. If major pools don’t move toward BIP-110 signaling, this proposal dies quietly and Bitcoin gets back to its current narrative cycle.

• If BIP-110 somehow approaches the 55% threshold with major economic actors still opposed, chain split risk becomes a real repricing event. Not a catastrophic one given Bitcoin’s history, but a messy one.

• The Taproot constraint angle matters for Layer 2 and smart contract infrastructure built on Bitcoin. BitVM projects and advanced Miniscript implementations would face genuine technical headwinds during any deployment window. Watch those developer communities for sentiment shifts.

• Luke-Jr’s involvement will drive a specific media narrative. His positions are maximalist and consistently generate controversy. That’s a signal amplifier for retail panic, not a fundamental signal itself.

Risk Factor: The Chain Split Scenario Nobody Is Pricing In

A 55% activation threshold is genuinely dangerous. Past Bitcoin soft forks that stuck, SegWit being the obvious example, built to near-supermajority signaling before activating, specifically to avoid producing blocks that a large minority of hashrate would reject. BIP-110’s threshold lowers that bar significantly. If this activates over the objection of major miners and custodians, you get two chains that both claim to be Bitcoin. The market has seen this movie before with Bitcoin Cash and Bitcoin SV. It wasn’t pretty, and the “loser” chain bled out slowly over years. Any exchange or custodian holding Bitcoin during an unresolved split event becomes exit liquidity for whoever moves fastest.

Pro-Tip: Watch the Exchange Statements, Not the Node Charts

Between you and me, the signal that actually matters here isn’t on any node dashboard. It’s in the silence from Coinbase, Binance, Kraken, and the major Bitcoin ETF custodians. None of them have endorsed BIP-110. None of them endorsed Bitcoin Unlimited either, and that proposal collapsed almost immediately once the economic actors made their position clear. If you start seeing formal statements from major exchanges about which chain they’d support in a split scenario, that’s when this story becomes a trading event rather than a governance argument. Until then, it’s noise with technically important implications.

References & Sources:

• CryptoSlate: BIP-110 Node Surge and Jameson Lopp’s Sybil Concern
• BIP-110 Full Specification on GitHub

Frequently Asked Questions