The OP_Return limit removal in Bitcoin Core 30 allows larger non-monetary data on-chain and has sparked widespread community backlash, driving many node runners to Bitcoin Knots to enforce stricter data limits and protect decentralization concerns.
OP_Return limit removal in Bitcoin Core 30 has triggered a surge in node migrations to Bitcoin Knots.
Node runners report Bitcoin Knots now accounts for ~20% of nodes versus ~1% in 2024.
Bitcoin ledger size ~680 GB since 2009; critics warn larger OP_Return entries may accelerate growth and centralization.
OP_Return limit change: Bitcoin Core 30 sparks node exodus—read expert analysis, community reaction, and steps node runners take. Learn what this means for decentralization now.
What is the OP_Return limit change in Bitcoin Core 30?
The OP_Return limit change in Bitcoin Core 30 removes the fixed 80-byte restriction for non-monetary data, allowing larger arbitrary data to be embedded on-chain. This decision has provoked strong criticism from developers and node runners concerned about long-term ledger growth and decentralization.
Why are developers and advocates divided over the OP_Return change?
Jimmy Song and other critics argue the change treats non-monetary data as acceptable “spam” and disregards the practical impact on node storage and bandwidth.
‘,
‘
🚀 Advanced Trading Tools Await You!
Maximize your potential. Join now and start trading!
‘,
‘
📈 Professional Trading Platform
Leverage advanced tools and a wide range of coins to boost your investments. Sign up now!
‘
];
var adplace = document.getElementById(“ads-bitget”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexBitget”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesBitget.length) : sessperindex;
adplace.innerHTML = adscodesBitget[adsindex];
sessperindex = adsindex === adscodesBitget.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexBitget”, sessperindex);
}
})();
Proponents counter that defining “spam” is ambiguous and limits can be overly restrictive. The debate echoes the block size wars and centers on design philosophy: strict monetary-only constraints versus permissive data use.
Song accused BTC Core developers of defecting and failing to address widespread community concerns about non-monetary data on the ledger.
Jimmy Song, a Bitcoin developer and advocate, criticized Bitcoin Core developers for removing the OP_Return 80-byte limit in the Bitcoin Core 30 upgrade, calling the rationale “fiat” mentality and accusing maintainers of deflecting community concerns.
‘,
‘
🔒 Secure and Fast Transactions
Diversify your investments with a wide range of coins. Join now!
‘,
‘
💎 The Easiest Way to Invest in Crypto
Dont wait to get started. Click now and discover the advantages!
‘
];
var adplace = document.getElementById(“ads-binance”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexBinance”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesBinance.length) : sessperindex;
adplace.innerHTML = adscodesBinance[adsindex];
sessperindex = adsindex === adscodesBinance.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexBinance”, sessperindex);
}
})();
Song said: “The idea that spam is difficult to define, and because of this ambiguity, we shouldn’t be making any distinctions at all in the software, is a time-wasting argument from fiat politics where you pretend not to know the obvious, so the actual debate can never get off the ground — the non-monetary uses of Bitcoin are spam. You can argue whether that’s something desirable or not, but saying you can’t define it is a stalling tactic meant to avoid the real argument about actual impact — particularly, the long-term impact of this change.”
Node runners have voted with their feet, moving en masse to Bitcoin Knots, an alternative node implementation that enables stricter enforcement of on-chain data limits.
Bitcoin Knots now represents about 20% of nodes, up from roughly 1% in 2024, a near-vertical rise in nine months based on public node software telemetry reported by community tracking projects (Coin Dance cited as plain text).
Supporters of strict limits say maintaining low storage and bandwidth requirements—Bitcoin’s full ledger is ~680 GB since 2009—keeps node operation affordable (~$300 retail hardware) and preserves decentralization.
‘
];
var adplace = document.getElementById(“ads-htx”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexHtx”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesHtx.length) : sessperindex;
adplace.innerHTML = adscodesHtx[adsindex];
sessperindex = adsindex === adscodesHtx.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexHtx”, sessperindex);
}
})();