Bitcoin Core · Policy

BIP 110

Not really about spam. About how Bitcoin adapts — and who gets to decide.

The question

Is this a fight about spam?
Or a fight about evolution?

The surface debate is dick pics and ordinals on the chain. The real debate is how Bitcoin ultimately adapts to resist quantum.

How it happened
  • May 5, 2025 — PR #32406 opened: uncap datacarrier by defaultProposed by Greg Sanders, longtime core developer
  • Jun 9, 2025 — PR #32406 merged into masterDefault -datacarriersize raised from 83 bytes to 100,000 bytes
  • Oct 2025 — Bitcoin Core v30.0 ships with the change
83 → 100,000

bytes — the default data-carrier limit, raised by roughly 1,200× in a single merge

The reaction

“This legitimizes spam.”

— The opposition, on the merge

The deeper concern

It wasn't the bytes.
It was the process.

A controversial policy change was merged despite significant community opposition — without broad consensus.

5

core maintainers held the keys to this decision

Who was in the room

Greg Sanders

Longtime core developer who proposed the BIP.

Gloria Zhao

27-year-old core maintainer who merged it in.

Samson Mow & Luke Dashjr

Prominent voices in the opposition.

Bitcoin Knots

Saw a significant increase in adoption as the alternative.

Why it really matters

The stakes aren't spam.
They're quantum.

The same governance muscle that merged this change is the one Bitcoin will need to resist quantum attacks. This was a stress test of how it decides.

The takeaway

BIP 110 is a preview.

How five maintainers handled a policy fight tells you how Bitcoin will handle its hardest upgrades to come. Watch the process, not just the bytes.

Made with xavior.ai