A temporary soft fork, titled Reduced Data Temporary Softfork, that would limit the size of data fields in new transactions for about a year, aimed at inscriptions and other data storage. Author: Dathon Ohm; assigned December 3, 2025.

Did BIP 110 activate?

No. It needed 55% of blocks to signal (1,109 of 2,016). In the period before mandatory signaling, 51 blocks (2.53%) signaled, according to press coverage. Its status in the BIP repository is Closed.

Was there a chain split?

Yes. From block 961,632 in August 2026, nodes enforcing BIP 110 rejected non-signaling blocks and followed a minority chain, which mined two blocks in about eight hours and then stalled.

What did BIP 110 restrict?

New outputs over 34 bytes (OP_RETURN up to 83 bytes), data pushes and witness items over 256 bytes, undefined witness versions, the Taproot annex, control blocks over 257 bytes, OP_SUCCESS opcodes, and OP_IF/OP_NOTIF in Tapscript.

What does BIP 110 mean for miners?

It is a case study in miner signaling: pools that did not signal stayed on the main chain with almost all the hashrate, and the minority chain could not find blocks at mainnet difficulty.

BIP 110 explained

The Reduced Data Temporary Softfork: what it tried to do, and how it split off a minority chain in 2026.

BIP 110 in plain English

BIP 110 tried to push back on using Bitcoin blocks to store data, such as Ordinals inscriptions. For about a year it would have made new transactions with large data fields invalid, while leaving coins people already held spendable. Supporters, many running Bitcoin Knots, saw it as anti-spam; opponents saw a rushed consensus change that could split the network.

What it would have changed

New output scripts over 34 bytes invalid, except OP_RETURN up to 83 bytes.
Data pushes and witness items over 256 bytes invalid.
Spending undefined witness versions, the Taproot annex, control blocks over 257 bytes, OP_SUCCESS opcodes, and OP_IF/OP_NOTIF in Tapscript invalid.
Outputs created before activation exempt; the rules expire after 52,416 blocks (about a year).

How the activation played out

The deployment used version bit 4 with a low 55% threshold and a mandatory signaling period: from block 961,632, BIP 110 nodes would reject blocks that did not signal. Barefoot Mining, through Ocean, mined the first signaling block on March 1, 2026. By the last period before the deadline, 51 of 2,016 blocks (2.53%) signaled, and F2Pool publicly declined.

When mandatory signaling began in August 2026, the network split. The main chain, with about 99.85% of the hashrate, carried on; the BIP 110 chain mined block 961,633 and one more in about eight hours, then stalled, with no difficulty adjustment in sight for months. No major exchange listed the minority chain at the time.

Since then, the project's own site describes a proof-of-work change on that chain to BLAKE2b, which takes it outside SHA-256 mining altogether. aPanel tracks it as a separate coin: BIP110 on aPanel.

What miners can take from it

Signaling is not a vote that obliges anyone: a soft fork with low support and mandatory enforcement splits off its supporters rather than moving the network. For pools, the practical lesson is to know exactly which rules your node enforces before a deadline block.

Questions

What is BIP 110?: A temporary soft fork, titled Reduced Data Temporary Softfork, that would limit the size of data fields in new transactions for about a year, aimed at inscriptions and other data storage. Author: Dathon Ohm; assigned December 3, 2025.
Did BIP 110 activate?: No. It needed 55% of blocks to signal (1,109 of 2,016). In the period before mandatory signaling, 51 blocks (2.53%) signaled, according to press coverage. Its status in the BIP repository is Closed.
Was there a chain split?: Yes. From block 961,632 in August 2026, nodes enforcing BIP 110 rejected non-signaling blocks and followed a minority chain, which mined two blocks in about eight hours and then stalled.
What did BIP 110 restrict?: New outputs over 34 bytes (OP_RETURN up to 83 bytes), data pushes and witness items over 256 bytes, undefined witness versions, the Taproot annex, control blocks over 257 bytes, OP_SUCCESS opcodes, and OP_IF/OP_NOTIF in Tapscript.
What does BIP 110 mean for miners?: It is a case study in miner signaling: pools that did not signal stayed on the main chain with almost all the hashrate, and the minority chain could not find blocks at mainnet difficulty.

Sources

Meet the people who build and mine Bitcoin

Soft forks only happen when miners, node operators and developers line up. Mining Disrupt 2027 puts the miners in the room, March 22–24 at the Irving Convention Center, Dallas. Get a pass or exhibit.

More: All BIPs · Taproot · BIP 39 · Drivechain · BIP 110 · Hashrate today

Three days. One floor. The whole industry.

March 22–24, 2027 · Irving Convention Center · Dallas

Buy tickets Secure a booth

Important Notice & Disclaimer

Mining Disrupt is NOT affiliated with any other brands, groups, events, meetups, individuals, sponsors, exhibitors, agents, or referrals, except the Industry Ambassadors listed on this site. We do not sell any lists. Beware of scams claiming otherwise.

There are imitators and scammers using our name to solicit sponsors and attendees. Always verify directly through our official Telegram group. Stay vigilant!

General Policy

Mining Disrupt Policy: No refunds. No outside food or drinks. No third-party event solicitations.

Marketing & Distribution Policy

Unauthorized solicitation, sales, advertising, product demonstrations, or distribution of promotional materials, including magazines, brochures, flyers, catalogs, business literature, and promotional giveaways, is strictly prohibited anywhere within the event venue unless expressly authorized by Mining Disrupt.

Marketing activities are reserved exclusively for approved exhibitors, sponsors, and authorized event partners. Attendees found engaging in unauthorized promotional activities may be required to cease immediately, surrender promotional materials, and may have their event credentials revoked without refund at the sole discretion of event management.