by dathonohm
Hi all,
Following up on the BIP-110 proposal from October, I am announcing the most recent stable release (v0.4.1) and the submission of an implementation of BIP-110 to Bitcoin Core.BackgroundBackground
BIP-110 was initially proposed in October 2025, and the first version of the official activation client was released at the end of January as a fork of Bitcoin Knots. It was accepted into the BIPs repo shortly thereafter.
For those new to BIP-110, it is a proposal to temporarily limit the size of data fields at the consensus level, in order to reject the standardization of data storage as a supported use case by consensus. It achieves this by temporarily limiting all officially supported methods of data storage (and methods that could be or become perceived as officially supported) to 256 bytes or less, while preserving all known monetary use cases.
This has several desirable effects, including but not limited to:
- Reducing demand for arbitrary data storage by frustrating attempts to monetize and gamify arbitrary data.
- Bringing consensus and policy back into closer alignment, by restoring still-popular policy limits from a few years ago in consensus.
- Protecting the decentralization of the node network by eliminating unnecessary costs and (in some cases, extreme) risks introduced by making arbitrary data storage an officially supported function of Bitcoin.
- Making Bitcoin better money by preventing Bitcoin payments from having to compete at an unfair disadvantage against gamified data spam.
...read more at delvingbitcoin.org
pull down to refresh
related posts
Nothing jumped out at me as a big change, so I guess this is mostly bug fixes and a chance to get it in front of people again.
I haven't looked at the changes either, but I thought the same!
Release the implementations muhahaha