OP_RETURN, inscriptions and BIP-110
After the Ordinals wave and Bitcoin Core 30.0 lifting its default OP_RETURN limit, BIP-110 proposed a one-year soft fork to “Temporarily limit the size of data fields at the consensus level”.
Bitcoin Core (relay policy)
“This is not endorsing or condoning non-financial data usage, but accepting that as a censorship-resistant system, Bitcoin can and will be used for use cases not everyone agrees on.”
Bitcoin Knots / BIP-110
Arbitrary data distorts incentives; restrict it at the consensus level with a 55% threshold and mandatory signalling.
The first fork fight since 2017 about what goes in blocks rather than how big they are — and the first to end in an actual split of nodes enforcing a soft fork.
BIP-110 nodes split off at block 961,632 on 8 August 2026. The minority SHA-256d chain made eight blocks in 22 days and became Bitcoin BLAKE2b. BIP-110 was marked Closed on 9 August 2026 “following a chain split with stalled mining”.
- 17 Apr 2025Antoine Poinsot proposes dropping Bitcoin Core’s OP_RETURN limits. [1]
- 2 May 2025PR #32406 to uncap -datacarrier by default is opened; it draws Concept NACKs as well as ACKs. [1]
- 9 Jun 2025PR #32406 is merged; Bitcoin Core 30.0 ships the larger default. [1] [2]
- 3 Dec 2025BIP 110 is assigned. [1]
- 8 Aug 2026BIP-110 nodes split off at block 961,632. [1]
- 9 Aug 2026Murch proposes marking BIP 110 Closed: just shy of 2.5% of blocks signalled. [1]
- Nov 2026Luke Dashjr says the closing was illegitimate and that BIP 110 activated. [1] [2]
“Since the restrictions on the usage of OP_RETURN outputs encourage harmful practices while being ineffective in deterring unwanted usage, i propose to drop them.”
bitcoin-dev · 17 Apr 2025 · source
“Concept NACK. Nodes have no incentive to become free relays between those who want to store arbitrary data and miners.”
GitHub, PR #32406 · 5 May 2025 · source
“Looking forward to closing the door on Bitcoin's decade-long spam debate so that we can move on to more important topics like consensus cleanup, covenants, and quantum preparation!”
X · 30 Jul 2026 · source
“BIP 110 failed to achieve adoption in both phases of its deployment attempt.”
bitcoin-dev · 9 Aug 2026 · source
“In August 2026, Bitcoin Core interests took over the former BIP repository, illegitimately removing the senior BIP editor and closing BIP 110 in violation of BIP 3.”
X · 10 Nov 2026 · source
“BIP110 was a softfork. Softforks don't need consensus, just broad support”
X · 19 Nov 2026 · source
- S17 E17: Lukas Hozda on BIP-110 — Vlad on a possible Knots/BIP-110 fork▶ listen at 1:18:41timestamp transcript-derived, pending a listen
- S17 E42: Bob Summerwill — the BIP-110 chain ground to a halt▶ listen at 38:26timestamp transcript-derived, pending a listen
- S17 E13: Charlie Spears on OP_NEXT and the OP_RETURN debate▶ listen at 1:23:04timestamp transcript-derived, pending a listen
- S17 E42: Bob Summerwill on BIP-110 and data-carrying▶ listen at 1:03:10timestamp transcript-derived, pending a listen
- Casey Rodarmor on Ordinals (6 Feb 2023; transcript titled S13 E3, file s12_e13): inscriptions in the witness▶ listen at 8:44timestamp transcript-derived, pending a listen