BIP-110 has moved to the center of Bitcoin’s technical debate. In the source article, Justin Bechler argues the proposal targets a growing flood of non-monetary data on the network, data that consumes block space and increases the burden on full nodes. His case is simple: if node operation becomes heavier and more expensive, Bitcoin’s decentralized validation model gets weaker.
The article cites a simulation covering 10 days of mainnet activity, from block heights 929,592 to 931,032. Across 4.7 million transactions, BIP-110 allegedly filtered 1,957,896 transactions, or 41.5% of the total, while reclaiming 747.85 MB of block space, equal to about 36%. It also claims that zero legitimate financial transactions were blocked in the sample.
The dispute centers on node accessibility
The piece frames Bitcoin’s value around three pillars: fixed supply, censorship-resistant transfers, and decentralized verification. From that view, the ability of ordinary users to run validating nodes is not a side issue. It is part of the monetary guarantee itself. If chain data keeps expanding because of non-financial uses, the cost of downloading, verifying, and storing the blockchain rises with it.
The article traces the problem to a route opened through Taproot-era transactions. It argues that Ordinals exploited a gap in Bitcoin Core’s spam filtering rules, allowing images, text files, BRC-20 mints, and other data to be embedded through Tapscript witness space. The source specifically references CVE-2023-50428, registered in the NIST database with a severity score of 5.3.
What BIP-110 is designed to block
According to the article, BIP-110 contains several rules, but rule 7 does most of the work. It would prohibit OP_IF and OP_NOTIF in Tapscript execution, directly targeting the OP_FALSE OP_IF wrapper commonly associated with Ordinals-style inscriptions. The simulation says rule 7 alone caught 1,954,477 transactions, equal to 99.8% of all filtered transactions.
The source also argues that Ordinals inscriptions and OP_RETURN spam are often treated as separate issues when they are closely linked on-chain. In the transactions caught by BIP-110, 94.6% were described as mixed transactions carrying both Tapscript inscription wrappers and OP_RETURN outputs with rune-related metadata.
Bitcoin Core and Knots are presented as taking opposite paths
The article contrasts Bitcoin Core with Bitcoin Knots. It says Knots patched the relevant issue in version 25.1 in late 2023, and that Ocean mining pool deployed the fix, while Bitcoin Core did not. It also points to Core 30 removing the long-standing OP_RETURN size limit, a change the author sees as making arbitrary data insertion easier rather than harder.
Bechler’s position is direct. Bitcoin should prioritize monetary transactions, not evolve into a general-purpose data relay and storage system. In that framing, BIP-110 is described as a proposal with a one-year activation window, meant to reduce non-monetary chain usage without interfering with payments, exchange withdrawals, Lightning channel opens, CoinJoin transactions, or multisig spends observed in the simulation.
The broader conflict is left unresolved but clearly defined. One side wants block space optimized for Bitcoin’s monetary role and low-cost node verification. The other accepts wider on-chain experimentation even if node requirements rise. BIP-110 has become a focal point for that split.