Jameson Ropp’s new chart has reignited one in all Bitcoin’s oldest inside debates: whether or not seen node counts mirror precise help for rule modifications.
The speedy flashpoint is BIP-110. This follows Bitcoin Core 30’s rest of the default OP_RETURN coverage, which is a draft proposal that quickly imposes stricter consensus-level restrictions on non-monetary information.
Ropp says the surge of nodes behind it might have been civilly inflated (i.e. artificially boosted by a single actor working numerous nodes to simulate broader help).
| sign | what it might probably present | one thing that may’t be confirmed |
|---|---|---|
| Variety of publicly reachable nodes | Visualize software program distribution in your community | Substantial monetary help for rule modifications |
| non-listening/personal node | Broad adoption past public nodes | Whether or not the operator is necessary for activation |
| minor signaling | Hashrate help for activation | Full help from exchanges, wallets and customers |
| Node surge on one shopper or BIP | Elevated curiosity and cooperation | Its help is natural, not cheaply manufactured |
Node chart that began it
Ropp shared a chart captioned “Sybil Assault Noticed” that exhibits the BIP-110 sign line spiking whereas the Bitcoin knot line soars.
Coin Dance’s present information, after correcting to exclude duplicate and non-listening nodes, exhibits 23,189 public Bitcoin nodes, of which 17,961 are working Bitcoin Core and 5,193 are working Bitcoin Knot.
Knots make up about 22% of the publishable set. This quantity is way from equal to Core.
The numbers range relying on the dashboard you utilize. Sensible Depraved Bitcoin, the platform on which Ropp created the chart, tracked 22,362 Core v30 nodes, 11,997 Knots nodes, and 10,361 BIP-110 signaling nodes as of March 23.
This hole between Coin Dance’s public counts and the counts utilized by the Sensible Depraved Bitcoin workforce exists as a result of the 2 platforms measure worlds otherwise. Whereas Coin Dance fixes duplicate and non-listening nodes, Sensible Depraved Bitcoin’s broader depend consists of each listening and non-listening nodes.
Relying on the methodology, the identical community can look like trending slowly or spiking dramatically.
Bitnodes’ personal documentation offers well-sourced the explanation why giant all-node sums needs to be handled with warning, no matter intent. Its world node estimate is described as a tough quantity that will embrace faux nodes rumored by non-standard or malicious friends.
Ropp’s enchantment is exact and structured. In his commentary for BIP-110, he argues that reachable node signaling has no financial weight, hundreds of nodes could be launched cheaply, and Tor addresses are “nearly free.”
His framework sees clusters of nodes that sign with none financial curiosity behind them as low-cost, manufactured governance theaters.
Ropp additionally attracts clear parallels with earlier Bitcoin governance battles, Bitcoin Limitless and SegWit2x. There, seen node counts had been used to say consensus help and by no means led to precise community adoption.
His core level is that Bitcoin governance is carried out based mostly on the financial weight of miners, exchanges, pockets operators, and so on., and can’t be expressed by an aggregation of reachable nodes.
The proliferation of BIP-110 sign nodes, even when real, leaves the activation situation utterly open.
Unfastened core 30 and OP_RETURN
The set off for BIP-110 was Bitcoin Core 30.0, launched on October 10, 2025.
Its launch notes confirmed that the default -datacarriersize has been elevated to 100,000, successfully eradicating the previous restrict and permitting a number of OP_RETURN outputs for relaying and mining.
For the anti-spam camp, this alteration in coverage was a purple line. Enjoyable defaults on the node degree felt like authorizing arbitrary information storage on the Bitcoin community.
BIP-110 is a response and has been filed within the BIP repository as a “Decreased Knowledge Momentary Softfork” written by Dathon Ohm.
This proposal tightens information restrictions on the consensus layer.
This specification locations a 34-byte restrict on new output scripts aside from OP_RETURN output as much as 83 bytes, limits information pushes and monitoring parts to 256 bytes, disables Taproot management blocks bigger than 257 bytes, and prohibits the OP_SUCCESS opcode and OP_IF and OP_NOTIF executed in Tapscript throughout deployment.
BIP additionally acknowledges Luke Jr. for drafting and offering recommendation.
Activation design elevates it to a governance wrestle. BIP-110 makes use of a modified model of BIP9 with a 55% signaling threshold and most activation peak round September 1, 2026.
| subject | Present/Core 30 and later background | BIP-110 proposal |
|---|---|---|
| OP_RETURN coverage | default -datacarriersize Elevated to 100,000. A number of OP_RETURN outputs allowed for relay/mining |
OP_RETURN is restricted to 83 bytes |
| output script | Easing the coverage setting after Core 30 | New output scripts are restricted to 34 bytes, aside from OP_RETURN |
| Knowledge push/monitoring parts | Larger information flexibility | restricted to 256 bytes |
| Taproot management block | Bigger scale building potential | restricted to 257 bytes |
| Faucet script conduct | Current improve flexibility | OP_SUCCESS disabled; executed OP_IF / OP_NOTIF Not allowed throughout deployment |
| activation design | Normal tender fork expectations often suggest broader consensus | Modified BIP9 with 55% threshold and obligatory signaling |
| supporter case | Bitcoin Drifting in the direction of Arbitrary Knowledge Utilization | Restore give attention to cash and cut back spam |
| the case of the critics | Coverage conflicts can stay on the node degree | Danger of chain splitting, faucet route constraints, overestimation of sign optics |
A tender fork activated on 55% of miner signaling leaves 45% of the hashrate and will produce blocks that the activated chain rejects, making the danger of chain splitting greater than theoretical.
Along with Sybil’s considerations, there are particular the explanation why BIP-110-related nodes may very well be simply deployed in early 2026.
On February sixth, myNode launched model 0.3.41 and added “Bitcoin Knots + BIP110 Customized Bitcoin Model” as an set up choice.
Within the February nineteenth RaspiBlitz pull request, we up to date the Knots installer to obtain and run BIP110-compatible builds.
The official BIP-110 web site lists a simplified set up path spanning Start9, Umbrel, myNode, Parmanode, and Docker, and explicitly encourages customers to run a signaling node to reveal help.
This surge seemingly displays a mixture of true opt-in adoption, simpler platform distribution, set up of personal non-listening nodes, and Sybil-style inflation.
Charts floor questions, however the information behind them doesn’t present solutions.
Betting Past the Signaling Battle
BIP-110 has deep technical implications for Bitcoin’s Taproot structure.
The draft quickly disables superior Taproot constructs that depend on the OP_SUCCESS improve hook, limits the execution of OP_IF and OP_NOTIF in Tapscript, and limits management blocks to 257 bytes.
Each the proposal and the BIP-110 web site acknowledge trade-offs.
Giant BitVM-style faucet bushes must wait, wallets that generate arbitrary Miniscripts will should be up to date, and if slim, some funds could also be frozen or misplaced in the course of the deployment interval. The location explains that the danger is extraordinarily low and says that pre-activation UTXOs stay exempt.
Ohm and different supporters imagine these restrictions are short-term and price tolerating as a way to restore Bitcoin’s financial focus.
The bearish case facilities round a failed correction. If the 55% threshold proves inadequate to deliver miners and financial actors on board, the consequence can be a failed tender fork and a months-long debate over the sign gentle for the community. On the similar time, actual governance points remained unresolved.
Bitcoin has existed earlier than. The distinction this time is that Core is the primary to alter the default, BIP-110 proponents are working a coordinated node distribution marketing campaign throughout a number of platforms, and the activation threshold is low sufficient to materialize chain-splitting eventualities.
Whether or not this surge represents a real coalition or an exaggerated sign, the controversy it has sparked is similar one which has outlined Bitcoin’s governance struggles for a decade: who issues, who counts, and who decides.