Share article

Bitcoin$62,580.18 just got its first on-chain "clean-up" signal, and it did not take long for the other side to clap back. A block mined by Ocean included support for BIP-110, a proposal aimed at curbing arbitrary data usage on Bitcoin$62,580.18, and critics responded with a 66 KB image embedded directly in a transaction as a very public protest.[1]
The immediate market reaction looked muted, with Bitcoin$62,580.18 around $69,223 at the time of CoinDesk's report, but the governance temperature jumped fast. This is not just a bikeshed about blockspace, it is a re-run of Bitcoin's oldest argument: who gets to decide what the chain is "for."[2]

Enjoy articles without ads?

Register for free and get unlimited access to all articles.

What happened, and why this block mattered

CoinDesk reported that the first block signaling support for BIP-110 has now appeared on-chain, mined by Ocean, a mining pool that has positioned itself as more opinionated about transaction selection than the "include everything that pays" norm.[3]
"Signaling" here is the key word. This is not the same as a network-wide rules change flipping on. It is a coordination move, a visible flag that says: some miners are willing to enforce a policy that makes certain transactions harder (or more expensive) to get confirmed, even if those transactions are technically valid under current consensus rules.
That difference between valid by consensus and accepted by policy is where most of the fighting happens, because Bitcoin can be permissionless at the base layer while still being shaped by what miners, pools, and node software treat as standard.

What BIP-110 is trying to do (the "clean-up" pitch)

BIP-110 has been framed by supporters as a temporary soft fork (CoinDesk described a one-year window) designed to cap or limit non-financial data being stuffed into Bitcoin transactions.[4]

The target is not subtle. Over the last couple of years, Bitcoin has seen recurring waves of blockspace demand from inscriptions and other data-heavy uses, enabled by taproot-era transaction formats and a fee market that does not discriminate between "payments" and "artifacts." When blockspace gets scarce, fees rise. When fees rise, the user experience for simple payments can degrade.

So the pro-BIP-110 argument is basically:

  • Bitcoin's base layer should prioritize monetary transfers.
  • Data-heavy activity crowds out typical usage and inflates fees.
  • A timeboxed "clean-up" could reset incentives and discourage spam-like behavior.

Critics hear something else:

  • This is value judgment baked into protocol policy.
  • It sets precedent for censorship by category.
  • Once you normalize "Bitcoin is for X, not Y," the definition of X keeps shrinking.

Both sides can point to precedent. Bitcoin has always had policy rules. It has also always had people trying to route around them.

The miner incentive problem, and the "miner's paradox" angle

One reason this fight is getting traction is that it lands right on miner incentives, not just ideology.

Miners are rational fee maximizers most of the time. If someone is willing to pay to put bytes in a block, miners generally do not care whether those bytes represent a payment, a JPEG, or a poem. That is the neutral, market-driven story.

BIP-110 supporters argue that neutrality breaks down when the chain becomes a data landfill and long-term node costs creep up. Opponents argue that today's fee pressure is the point, especially in a post-halving world where security increasingly depends on fees, not issuance.
This is where the "miner's paradox" framing shows up in community writeups: miners benefit from high fees in the short run, but could harm the network's long-run decentralization if high-volume data usage pushes up bandwidth, storage, and verification costs for everyone. The paradox is not that miners are evil, it is that the incentives are not perfectly aligned across time horizons.[5]
Ocean mining a signaling block is notable because it implies at least one pool is willing to take a stance that could, at the margin, reduce certain kinds of fee revenue in exchange for a cleaner mempool and a more payments-centric chain.

The pushback was immediate, and it was on-chain

Opponents did not just quote-tweet. Per CoinDesk, critics responded with experiments including embedding a roughly 66 KB image in a transaction specifically to protest the idea of restricting data.[6]

That protest matters for two reasons:

  1. It demonstrates capability. If someone can get a chunky image confirmed today, they are showing that "non-financial" use is not hypothetical, it is live and measurable.
  2. It tests enforceability. Any proposed cap, filter, or standardness change has to contend with the reality that data can be encoded in multiple ways. Clamp down on one method and people will probe the edges of another.

If BIP-110 is implemented as a soft fork, it would tighten what is allowed by consensus. If it is implemented as policy, it would tighten what nodes relay and what miners include by default. Those are very different battles, with very different "route around it" possibilities.

What this means for fees, blockspace, and regular users

The practical question is whether Bitcoin wants its fee market to be fully general-purpose, or whether it wants to privilege payments at the base layer.

If BIP-110 gains traction:
  • Some data-heavy transactions could become harder to mine, pushing them to pay higher fees, find miners willing to include them, or move to other chains.
  • Average fee pressure could ease during heavy inscription cycles, depending on how much demand is actually displaced versus simply repriced.
  • Policy fragmentation risk rises, because not every pool or node operator will enforce the same standards at the same time.

If BIP-110 stalls:

  • The status quo continues, meaning blockspace stays a neutral auction.
  • Expect periodic fee spikes when new meta trends arrive, because people will keep testing what Bitcoin can be used for when demand is strong enough.

Neither path is free. "Clean-up" can look like censorship. Pure neutrality can look like letting the chain get congested for reasons many users did not sign up for.

What to watch next (and what would change the narrative)

This story is early, and signaling is cheap compared to activation. Here are the checkpoints that will tell you whether BIP-110 is a flashpoint or a real governance shift:

  • More signaling blocks, especially from other major pools. One pool is a headline, broad participation is leverage.
  • Client and node operator alignment, because miners can signal all they want, but enforcement depends on what software people actually run.
  • Mempool and fee behavior around future data-heavy waves. If proponents can point to measurable relief (lower median fees, less congestion), they gain credibility.
  • Evidence of censorship externalities, like innocent transactions getting caught by overly broad filters, or a clear rise in private relay and out-of-band mining deals.

Takeaway: the culture war is back, and the chain will show receipts

The first BIP-110 signaling block mined by Ocean is less about immediate protocol change and more about coordination and norms. Supporters are testing whether Bitcoin can defensively narrow what "standard" looks like. Opponents are testing whether that narrowing is technically enforceable and socially acceptable.

Risk is straightforward: if the network splits into competing transaction policies, users could see more unpredictability in confirmation behavior, and miners could end up pressured to pick sides. The clean invalidation line is simple too. If signaling does not spread beyond a small minority of hashpower, BIP-110 becomes a footnote. If major pools join and node software follows, the "Bitcoin is for payments" camp just found its first real on-chain momentum in years.