Bitcoin Core Going Rogue?

3 min read

Bitcoin core are going ROGUE, at least that's what some people are saying about the recent change proposed by Peter Todd...

In this weeks report we're going to cover exactly what is going on there.

But first, let's take a quick look at how the markets been holding up.

Macro Overview

MicroStrategy 2.0?

On 23 April 2025, Strike CEO Jack Mallers unveiled Twenty One Capital, a Bitcoin‑native holding company poised to go public via a SPAC merger with Cantor Equity Partners.

Backed by Tether and SoftBank, the firm will debut with a war chest of 42,000 BTC (~$3.9 B) and a laser‑focus on maximising Bitcoin Ownership Per Share—a deliberate echo of Michael Saylor’s playbook at MicroStrategy.

Should the deal close this quarter, Twenty One would enter the rankings as the third‑largest corporate BTC holder, leap‑frogging Tesla and Block.

Bitcoin Core

Since 2013 Bitcoin Core has enforced a default policy that restricts OP_RETURN outputs to a maximum of 83 bytes. The cap serves two purposes: (i) discouraging arbitrary data storage on‑chain and (ii) allowing nodes to safely prune OP_RETURN outputs because they are provably unspendable.

💡
To keep it simple, this policy has helped stop Bitcoin from being filled with "spam" data, such as ordinals etc. But there has always been ways around it. The reason this is so controversial is it can be seen as a sign that Bitcoin is opening up to other use cases and moving away from it's pure monetary, financial transactions.

On 28 April 2025, veteran developer Peter Todd opened PR #32359 proposing to remove the hardcoded limit entirely. His argument: modern wallets and services already pass larger OP_RETURN payloads via custom relay policies (e.g., Ordinals inscriptions), so the limit is “a source of needless code complexity and inconsistent behaviour.” Todd insists that “policy should live in mempool, not consensus.”

Flash‑Point Issues

  1. Blockchain Bloat: Opponents fear that unlimited OP_RETURN could rekindle the 2023 inscription frenzy, swelling the chain state, stressing archival nodes, and pushing fees higher for regular monetary transactions.
  2. UTXO Set Growth: While OP_RETURN outputs don’t add to the spendable UTXO set, they do persist in the block files. Critics like Luke Dashjr warn this will increase IBD (initial block download) times, especially for resource‑constrained users.
  3. Economic Centralisation: Higher fees may favour large custodial platforms at the expense of individuals, undermining Bitcoin’s decentralised ethos.
  4. Precedent: Relaxing one long‑standing policy could embolden future attempts to loosen others—potentially eroding the narrow “digital‑gold” vision that the majority of Core maintainers support.

Debate Timeline

DateEventNotes
28 AprPR #32359 openedTodd cites “code hygiene” & dev convenience
29 Apr200+ comments in 24 hrsHeated exchanges on Bitcoin‑Dev & GitHub
30 AprMaintainer @sipa floats compromiseAdd soft‑limit in policy, keep default 83 B in consensus
2 MayPR tagged Needs Concept ACKMerged only if broad consensus forms

Outlook

Consensus is weeks away at best. Even if maintainers align on a policy‑flag compromise, major relay networks (mining pools, mempool.space, etc.) would need to upgrade before larger OP_RETURN objects propagate reliably. Expect the topic to dominate developer mailing lists through June’s Core v27.0 release window.

What do you think to this whole situation, has Bitcoin core gone rogue?

Disclaimer: This article is for educational purposes only and does not constitute financial advice. Cryptocurrency investments carry risk; you should always do your own research before making any investment decisions.

On this page