- Bitcoin Core v30 is set to raise default limits for data in transactions not related to moving bitcoin.
- The update changes the way node operators control how much unrelated data their software accepts.
- The popular “datacarriersize=” configuration option now acts differently than in previous versions.
- Some community members claim these changes could make the network more exposed to spam.
- Future versions are expected to remove user options for limiting this transaction data.
Bitcoin Core will release its version 30 update in October 2025, making significant changes to how its nodes handle non-bitcoin data in transactions. The update will allow much more non-currency data into the network’s mempool by default, reversing limits in place since 2011.
The change notably affects the way node operators use the “datacarriersize=” setting, which decides how much extra data each transaction can carry using OP_RETURN outputs. In v30, the same setting allows nearly nine times more data with multiple OP_RETURN outputs, compared to one output in earlier versions. Knots developer Luke Dashjr explained this by saying that setting “datacarriersize=83” previously limited arbitrary data to 92 bytes per transaction, but now permits up to 830 bytes. Dashjr described the adjustment as a “trick” by what he calls “bad actors” and shared more details in a public statement.
Developers have also decided that the user control for datacarriersize will eventually be removed, or “deprecated.” The default data filter will rise sharply from a few bytes up to nearly 4 megabytes. Some operators and developers, including Knots leaders, have raised concerns, calling the move “malicious code” in the latest public comments.
With these changes, node software will now accept more than one OP_RETURN output per transaction for the first time in more than ten years. OP_RETURN is a command within the bitcoin protocol that lets users attach extra data to transactions, often used to store arbitrary messages or code. Community members warn this could expand opportunities for spam data.
A GitHub update from contributor Instagibbs confirmed that while the ability to set datacarriersize remains in v30, it is officially deprecated—meaning it could be removed in the near future. Chaincode Labs developers are moving forward with the changes, despite protests that the approach is confusing for many users.
Additional background shows that Knots software, an alternative to Bitcoin Core, currently operates on about 16% of active bitcoin nodes. The arrangement of mempool rules influences how easily different kinds of data are stored or transferred across the Bitcoin network.
The development raises ongoing discussions about data storage, network efficiency, and the long-term impact of raising transaction data limits on a decentralized system.
✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.
Previous Articles:
- Paxos Seeks National Charter, Eyes Expansion Amid Stablecoin Moves
- Stargate Token Holders Oppose LayerZero Foundation Acquisition Bid
- Fake XRP Rally Hopes Dashed as Judge Confirms SEC Case Is Closed
- South Korean Investors Shift to Crypto Stocks, BitMine Surges
- Hyperlane Brings Radix Interoperability With 150+ Blockchains
