A brand new chart from Jameson Lopp has reopened one among Bitcoin’s oldest inner debates: whether or not seen node counts mirror actual help for a rule change.
The fast flashpoint is BIP-110, a draft proposal that might quickly impose a lot tighter consensus-level limits on non-monetary knowledge, following Bitcoin Core 30’s loosening of the default OP_RETURN coverage.
Lopp says the node surge behind it could be Sybil-inflated (i.e., artificially boosted by a single actor working many nodes to simulate broader help).
| Sign | What it might present | What it can not show |
|---|---|---|
| Public reachable node rely | Seen distribution of software program on the community | Actual financial help for a rule change |
| Non-listening / non-public nodes | Broader adoption past public-facing nodes | Whether or not the operators matter for activation |
| Miner signaling | Hashrate help for activation | Full help from exchanges, wallets, customers |
| Node surge on one shopper or BIP | Rising curiosity or coordination | That help is natural relatively than cheaply manufactured |
The node chart that began it
Lopp shared a chart captioned “Spot the Sybil Assault” exhibiting the BIP-110 signaling line rising sharply whereas the Bitcoin Knots line whipsawed.
Present knowledge from Coin Dance exhibits 23,189 public Bitcoin nodes, with 17,961 working Bitcoin Core and 5,193 working Bitcoin Knots, after correcting to omit duplicate and non-listening nodes.
Knots account for roughly 22% of the public-reachable set. The quantity is properly wanting parity with Core.
The numbers look completely different relying on the dashboard used. Sensible Depraved Bitcoin, the platform from which Lopp drew his chart, tracked 22,362 Core v30 nodes, 11,997 Knots nodes, and 10,361 BIP-110 signaling nodes as of Mar. 23.
That hole between Coin Dance’s publicly accessible rely and the one utilized by the Sensible Depraved Bitcoin crew exists as a result of the 2 platforms measure completely different universes. Coin Dance corrects for duplicates and non-listening nodes, whereas Sensible Depraved Bitcoin’s broader rely contains each listening and non-listening nodes.
The identical community can seem both modestly tilted or dramatically surging, relying on methodology.
Bitnodes’ personal documentation gives a source-backed cause to deal with giant all-node totals with warning, no matter intent: its global-node estimates are described as tough counts that will embody spurious nodes gossiped by non-standard or malicious friends.
Lopp’s grievance is exact and architectural. In his BIP-110 explainer, he argues that reachable-node signaling carries no financial weight, that hundreds of nodes may be spun up cheaply, and that Tor addresses are “virtually free.”
His framing sees a cluster of nodes signaling with out financial stake behind them as a governance theater manufactured at low value.
Lopp additionally attracts an specific parallel to earlier Bitcoin governance battles, Bitcoin Limitless and SegWit2x, the place seen node counts had been used to argue for consensus help that by no means translated into precise community adoption.
His core level is that Bitcoin’s governance runs on financial weight, corresponding to miners, exchanges, and pockets operators, which reachable-node tallies can not signify.
A surge in BIP-110 signaling nodes, even a real one, leaves the query of activation totally open.
Core 30 and the OP_RETURN loosening
The set off for BIP-110 was Bitcoin Core 30.0, launched Oct. 10, 2025.
Its launch notes confirmed that the default -datacarriersize was raised to 100,000, successfully eradicating the outdated restrict, and that a number of OP_RETURN outputs are actually permitted for relay and mining.
For the anti-spam camp, that coverage shift crossed a line: loosening defaults on the node stage felt like an endorsement of arbitrary knowledge storage on the Bitcoin community.
BIP-110 is the response and was filed within the BIPs repository as “Decreased Knowledge Short-term Softfork,” authored by Dathon Ohm.
The proposal would tighten knowledge limits on the consensus layer.
The specification units a 34-byte cap on new output scripts aside from OP_RETURN outputs as much as 83 bytes, limits knowledge pushes and witness components to 256 bytes, invalidates Taproot management blocks over 257 bytes, and disallows OP_SUCCESS opcodes plus executed OP_IF and OP_NOTIF in Tapscript throughout deployment.
The BIP additionally credit Luke-Jr with unique drafting and recommendation.
The activation design is what elevates it right into a governance combat. BIP-110 makes use of a modified model of BIP9 with a 55% signaling threshold and a most activation peak round Sept. 1, 2026.
| Subject | Present / post-Core 30 backdrop | BIP-110 proposal |
|---|---|---|
| OP_RETURN coverage | Default -datacarriersize raised to 100,000; a number of OP_RETURN outputs allowed for relay/mining | OP_RETURN restricted to 83 bytes |
| Output scripts | Looser coverage atmosphere after Core 30 | New output scripts capped at 34 bytes, besides OP_RETURN |
| Knowledge pushes / witness components | Broader knowledge flexibility | Capped at 256 bytes |
| Taproot management blocks | Bigger constructions doable | Capped at 257 bytes |
| Tapscript conduct | Present improve flexibility | OP_SUCCESS invalid; executed OP_IF / OP_NOTIF disallowed throughout deployment |
| Activation design | Customary soft-fork expectations often suggest a lot broader consensus | Modified BIP9 with 55% threshold and necessary signaling |
| Supporters’ case | Bitcoin drifting towards arbitrary-data use | Restore financial focus, cut back spam |
| Critics’ case | Coverage dispute might stay at node stage | Dangers chain cut up, constrains Taproot, overweights signaling optics |
A comfortable fork that prompts at 55% miner signaling leaves 45% of hashrate probably producing blocks that the activated chain would reject, making the chain-split danger greater than theoretical.
Alongside the Sybil concern, there are concrete causes BIP-110-related nodes grew to become simpler to deploy in early 2026.
On Feb. 6, myNode launched model 0.3.41, which added “Bitcoin Knots + BIP110 Customized Bitcoin Model” as an set up choice.
A RaspiBlitz pull request on Feb. 19 up to date its Knots installer to obtain and run a BIP110-enabled construct.
The official BIP-110 website lists simplified set up paths throughout Start9, Umbrel, myNode, Parmanode, and Docker, and explicitly encourages customers to run signaling nodes to exhibit help.
The surge possible displays some mixture of real opt-in adoption, simpler platform distribution, non-public non-listening node installs, and Sybil-style inflation.
The chart surfaces the query, whereas the information behind it leaves the reply open.
The stakes past the signaling combat
BIP-110 carries technical penalties that run deep into Bitcoin’s Taproot structure.
The draft would quickly invalidate superior Taproot constructions that depend on OP_SUCCESS improve hooks, limit the execution of OP_IF and OP_NOTIF in Tapscript, and cap management blocks at 257 bytes.
The proposal and the BIP-110 website each acknowledge the tradeoffs.
BitVM-style giant Taptrees would want to attend, wallets producing arbitrary Miniscript would require updates, and in slender edge circumstances, some funds could possibly be frozen or misplaced in the course of the deployment window. The location describes that danger as extraordinarily unlikely and says pre-activation UTXOs stay exempt.
Supporters, corresponding to Ohm, body these constraints as short-term and value tolerating to revive Bitcoin’s financial focus.
The bear case facilities on a coordination failure. If the 55% threshold proves inadequate to convey miners and financial actors alongside, the result’s a failed comfortable fork and a community that spent months arguing over signaling optics. On the identical time, the actual governance query stayed unanswered.
Bitcoin has been right here earlier than. The distinction this time is that Core modified the defaults first, BIP-110’s proponents are working a coordinated node distribution marketing campaign throughout a number of platforms, and the activation threshold is low sufficient to make the chain-split situation concrete.
Whether or not the surge represents a real coalition or an inflated sign, the argument it has triggered is similar one which has outlined Bitcoin’s governance fights for a decade: who counts, who will get counted, and who decides.
