Bitcoin Knots' BIP110, a consensus change that would temporarily cap OP_RETURN sizes and cut down on other blockchain data, is set to start rejecting non-signaling blocks from block 961,632 — expected around Aug 8. But with just 1-2% of hash power signaling support in recent weeks, the upgrade has no consensus behind it, and enforcement could leave some nodes stuck or, worse, split the chain.
What BIP110 actually does
BIP110 is a proposal from Bitcoin Knots, an alternative Bitcoin implementation. It limits how much data can be stuffed into OP_RETURN outputs — the standard way people embed arbitrary data on the blockchain. The stated goal is to reduce other types of data on Bitcoin's ledger, not just OP_RETURN. But Bitcoin Core, the implementation most of the network actually runs, hasn't adopted it. That alone tells you how far from mainstream this idea is.
Why it's contentious
There's no agreement that a problem even needs solving. Not everyone thinks OP_RETURN bloat is a real issue, and even those who do aren't convinced BIP110 is the right fix. The numbers back that up. Only a sliver of miners have signaled support, and there's been no public push from major pools or exchanges to get behind it. This isn't a soft fork with broad buy-in; it's a change pushed by one implementation with almost no network backing.
The Aug 8 enforcement trigger
Starting at block 961,632, nodes running BIP110 will reject any block that doesn't signal support for the upgrade. That's a hard rule baked into the code. If miners keep doing what they've been doing — ignoring it — those nodes will stall the moment they see a non-signaling block. They'll become unusable, stuck on a chain that stops growing. For anyone running Bitcoin Knots, that's a real operational risk.
What could happen next
Three scenarios are on the table. If miners keep ignoring BIP110, enforcing nodes simply stop working. If every miner suddenly signals, the upgrade could technically activate — but signaling doesn't guarantee they'll actually enforce the rules, and if economic nodes don't follow along, you get a split. And if a sizable minority of miners signals, the chain could split immediately. None of those outcomes look good for a network that's supposed to be stable. Miners have until block 961,632 to decide which way they're going. The clock is ticking.
