BIP-110

BIP-110 rules for transactions are active

Since August 30, 2026 the additional rules BIP-110 for transactions are active in Bitcoin.

BIP-110 has been activated at the block height 961632 on 8 August 2026 20:12 UTC (block hash: 0...7c78dbc16) successfully. The additional rules for transactions are active since block #961640 which came on August 30, 2026 along with the hard-fork Blake2b. Bitcoiners keep running their nodes (Bitcoin Knots v29.4.1) and new blocks are mined.

Consensus (soft fork)

BIP-110:
Protecting Bitcoin's Purpose

Temporarily limit the size of data fields at the consensus level, in order to correct distorted incentives caused by standardizing support for arbitrary data, and to refocus priorities on improving Bitcoin as money.

Read the full BIP
By Dathon OhmCreated 2025-12-03BSD-3-Clause

BIP-110: Also referred to as RDTS (BIP-444)

Key Points

A temporary, focused intervention to protect Bitcoin's core mission

Temporary Protection

A one-year deployment that can be refined or extended based on community feedback.

Limits Data Storage

Restricts arbitrary data embedding that burdens node operators and diverts resources.

Preserves Monetary Use

All known monetary use cases remain fully functional and unaffected.

Refocuses Bitcoin

Signals that Bitcoin's priority is being the world's best money, not data storage.

Run BIP-110

Run a fully (incl. BIP-110) validating node to secure Bitcoin P2P network and mine BTC.

Bitcoin Knots

Official Bitcoin Knots release with BIP-110/RDTS support

Start9

Official Start9 package with an RDTS activation task

Umbrel

One-click install from the Umbrel app store

myNode

Custom Bitcoin Version option with RDTS confirmation

Parmanode

Simple one-click style install for Parmanode users

Docker

For advanced users running their own Docker infrastructure

View detailed installation instructions

Protecting Bitcoin's Purpose

Starting with the 'inscription' hack in 2022, a trend emerged around embedding arbitrary data into Bitcoin transactions. This creates unnecessary burdens on node operators and diverts development focus from Bitcoin's fundamental purpose: being sound, permissionless, borderless money.

Data storage competes unfairly with payments, making Bitcoin transactions unnecessarily costly. This encourages reliance on third-party payment processors, making Bitcoin payments easier to censor.

By limiting data storage, this proposal liberates developers from endless scope creep, enabling them to focus on what's really important: Bitcoin's success as money.

Evidence archive

WTF Happened in Feb 2023?

Review the blockspace, fee pressure, and node-resource data behind the February 2023 spam wave.

“Bitcoin should do one thing, and do it well.”

How It Works

Simple restrictions that preserve all monetary use cases while limiting data abuse

Output Size Limits

New outputs are limited to 34 bytes, except OP_RETURN which allows up to 83 bytes.

Data Push Limits

Data pushes and witness elements are limited to 256 bytes maximum.

Witness Version Restrictions

Only well-defined witness versions (v0 and Taproot) can be spent during the deployment.

Taproot Restrictions

Taproot annexes, large control blocks, and certain opcodes are temporarily restricted.

Inputs spending UTXOs created before activation are permanently exempt from these rules — there is no deadline to move existing funds.

Inspect the implementation

The commented walkthrough ties each rule to the tagged Bitcoin Knots source.

Open code walkthrough

Common Questions

Answers to frequently asked questions about BIP-110

Articles

Start with the background, then continue into the BIP-110 analysis

Image

CAPTURE: The Network

Part one documents the people, institutions, and incentives that hodlonaut argues shaped Bitcoin Core's informal power structure before the OP_RETURN controversy.

hodlonautMar 27, 2026
Image

CAPTURE: The Lever

Part two examines how funding, review influence, and institutional weight can sideline inconvenient contributors without a formal governance process.

hodlonautApr 29, 2026
Image

CAPTURE: The Merge

Part three of hodlonaut's CAPTURE series traces how a documentation change, Luke's filter patch, and the OP_RETURN uncap PRs built toward Bitcoin Core's contested 2025 merge.

hodlonautJun 15, 2026
Image

The OP_RETURN Limit Removal: Gaslighting or Technical Necessity?

Melvin Carvalho's research report weighs the stated technical case for removing Bitcoin's 80-byte OP_RETURN limit against process concerns, conflicts of interest, and BIP-110's response.

Melvin CarvalhoFeb 2026
Code WalkthroughFull Reading Path

Important Considerations

Honest assessment of limitations and risks

BitVM & Advanced Contracts

The 257-byte control block limit makes Tapleaves deeper than 7 levels unspendable during the deployment. Larger or unbalanced Taptrees must keep every required script-path leaf within that depth. Advanced smart contracts like BitVM may need to wait until expiry or use testnet/sidechains.

Wallet Compatibility

Some wallets like Nunchuk allow arbitrary Miniscript and may create Tapleaves with OP_IF or place required scripts deeper than 7 levels. These wallets would need to update before activation to avoid both patterns. UTXOs created before activation are permanently exempt, so existing funds are unaffected regardless of wallet software. Wallet developers have until mandatory lock-in (~August 2026) plus a two-week grace period to update. Even after activation, only newly created UTXOs are subject to the new rules. Wallets can split OP_IF branches into separate Tapleaves and keep every required script-path leaf at depth 7 or less.

Upgrade Hooks

Upgrade hooks via undefined witness versions and OP_SUCCESS are unavailable during deployment. Since softforks take over a year to coordinate, this shouldn't be a practical issue.

Deployment Timeline

Key dates and milestones for BIP-110 activation

December 1, 2025

Optional signaling begins

Miners signal readiness using bit 4. Early lock-in option expired as of few blocks included the signal in a retarget period.

8 August 2026 20:12 UTC

Mandatory signalling at block height 961632

Mandatory signaling began - blocks that don't signal are rejected as invalid.

Block height 961640 (along with hard-fork Blake2b)

Activation of all new rules

New consensus rules take effect. Blocks and transactions violating these rules are rejected by all enforcing nodes. Pre-existing UTXOs remain permanently exempt.

~1 year after activation

Expiry

At around 2027-09-01 00:00 UTC all restrictions lift automatically.

Signaling uses bit 4 • Mandatory signaling has begun on the 8 August 2026.