BIP-110 Bitcoin Soft Fork: What It Means for DeFi

Bitcoin is on the verge of its most contentious protocol change in years. A proposal called BIP-110 — officially the Reduced Data Temporary Softfork — could activate as early as September 6, 2026, restricting how Ordinals inscriptions, BRC-20 tokens, and Runes are stored on the Bitcoin blockchain. If you hold Bitcoin, use DeFi, or move BTC across chains, this is worth understanding before it happens.

Bottom Line: BIP-110 is a temporary Bitcoin protocol rule that would ban non-financial data (Ordinals, BRC-20 tokens, Runes) from Bitcoin blocks for roughly one year. It has a clear activation date (~September 6, 2026) but less than 1% miner support as of July 2026, making a contentious chain split a real possibility. For Bitcoin DeFi users and bridge protocols, the key risks are transaction disruption and short-term uncertainty — not a permanent shutdown of the ecosystem.

Key Takeaways:BIP-110 (also called RDTS) is a temporary soft fork proposal drafted by Luke-Jr that would restrict Ordinals, BRC-20 tokens, Runes, and oversized OP_RETURN payloads from Bitcoin blocks for approximately one year (~52,416 blocks post-activation).The UASF activation pathway sets a hard flag day at block 961,632 (~August 9, 2026), with full enforcement at block 965,664 (~September 6, 2026) regardless of miner support — the same mechanism used for SegWit in 2017.Miner support stands at roughly 1% as of July 2026, far below the 55% threshold required for miner-activated soft fork (MASF) — making a chain split a high-likelihood scenario if node adoption proceeds without miners, according to Bitcoin security researcher Jameson Lopp.Bitcoin Core, the dominant reference client, has NOT endorsed BIP-110 — only Bitcoin Knots 29.2 ships the implementation, which means enforcement depends entirely on how many nodes voluntarily upgrade.For DeFi and cross-chain bridge users, BIP-110 does not eliminate trustless Bitcoin transfers — protocols that verify standard Bitcoin transactions using light-client proofs (like TeleSwap's SPV-based bridge) remain unaffected by the data restrictions.

At a Glance: BIP-110 Activation Pathways Compared

Table of Contents

• What Is a Bitcoin Soft Fork, Really?
• What Is BIP-110 and What Does It Actually Do?
• How Does BIP-110 Activation Work?
• Could BIP-110 Split Bitcoin in Two?
• Why Does BIP-110 Matter for Bitcoin DeFi?
• What Does BIP-110 Mean for Bitcoin Bridges?
• What Risks Should You Watch For?
• The BIP-110 Timeline: Key Dates at a Glance
• Frequently Asked Questions

What Is a Bitcoin Soft Fork, Really?

Before diving into BIP-110 specifically, it helps to understand what a soft fork actually is — because the term gets thrown around a lot, and the distinction matters here.

Think of Bitcoin's consensus rules as a shared rulebook that every participant in the network agrees to follow. If you want to change the rules, you have two options. A hard fork is like rewriting the rulebook entirely — old participants who don't update get kicked out of the game. A soft fork adds new restrictions within the existing rules — old participants who don't update can still play, but they might occasionally accept moves that new participants would reject.

In technical terms: a soft fork tightens the rules. Transactions that were valid before might become invalid under the new rules, but transactions valid under the new rules are still valid under the old ones. This matters because it means soft forks don't require everyone to upgrade simultaneously — but they do create pressure to upgrade, since nodes running old software might accept blocks that upgraded nodes reject.

Bitcoin has upgraded this way several times before. SegWit in 2017 was a famous soft fork — it added a new transaction format (witness data) that old nodes couldn't fully validate, but the network upgraded successfully. That history is directly relevant to BIP-110.

What Is BIP-110 and What Does It Actually Do?

BIP-110 — officially titled the Reduced Data Temporary Softfork (RDTS) — was originally numbered BIP-444 before being assigned its current number. The proposal was drafted by Luke-Jr, a long-standing Bitcoin Core contributor with a history of opposing non-financial use cases for Bitcoin block space.

The core idea is simple: Bitcoin blocks have limited space. Since 2023, that space has been increasingly occupied by Ordinals inscriptions (essentially digital art stored directly in Bitcoin transactions), BRC-20 tokens (a fungible token standard built on Ordinals), and Runes (a newer token protocol from the creator of Ordinals). Critics argue this consumes block space that should be reserved for financial transactions, drives up fees for ordinary users, and burdens node operators with storage they didn't sign up for.

BIP-110 would temporarily ban these uses. Specifically, it restricts:

• Ordinals inscriptions — images, text, and arbitrary data embedded in Bitcoin transaction witness fields
• BRC-20 tokens — fungible tokens minted via Ordinals-style inscriptions
• Runes — the newer token protocol using OP_RETURN outputs
• Oversized OP_RETURN payloads — transaction outputs used to store arbitrary data
• Non-financial data in witness data — any data stored in transaction witness sections that isn't required for script validation

Crucially, BIP-110 is designed as a temporary measure. It would automatically expire approximately one year after activation (~52,416 blocks), which means it's framed as a circuit breaker rather than a permanent ban. According to the official BIP-110 specification, the reduced 55% miner activation threshold (versus the standard 95% for permanent changes) is justified precisely because of this temporary nature.

One important nuance: pre-existing UTXOs are grandfathered in. Ordinals and tokens created before BIP-110 activation would not be immediately invalidated — only new inscriptions and token mints created after activation would be restricted.

How Does BIP-110 Activation Work?

There are two pathways to activation, and understanding both is key to understanding why BIP-110 is controversial.

Pathway 1: Miner-Activated Soft Fork (MASF)

Under this pathway, Bitcoin miners signal support for BIP-110 by setting a specific bit in the blocks they mine. If 55% of blocks within any two-week difficulty adjustment period (1,109 out of 2,016 blocks) include this signal, the fork locks in and activates two weeks later. Signaling has been open since December 1, 2025.

The problem? As of July 2026, only ~1% of miners are signaling support — far below the 55% threshold. The first miner to signal was Barefoot Mining via Ocean Pool, starting March 1, 2026. That's essentially been it.

Pathway 2: User-Activated Soft Fork (UASF)

This is where things get contentious. A UASF bypasses miners entirely. Nodes — the computers run by individuals, businesses, and exchanges that validate Bitcoin transactions — simply upgrade to software that enforces the new rules. If enough economically significant nodes upgrade, they can effectively impose the rules regardless of what miners do.

BIP-110's UASF timeline:

1. ~August 9, 2026 (block 961,632): Mandatory signaling window begins
2. ~August 23, 2026 (block 963,648): Lock-in deadline
3. ~September 6, 2026 (block 965,664): Full enforcement begins, regardless of miner support

This is the exact same mechanism used to activate SegWit in 2017. The critical difference: SegWit had overwhelming miner support before the flag day. BIP-110, as of writing, does not. The reference implementation is Bitcoin Knots 29.2 — Bitcoin Core, the dominant client used by most nodes, has not endorsed or implemented BIP-110.

Could BIP-110 Split Bitcoin in Two?

This is the question everyone is actually asking, and the honest answer is: it's a real risk, and the current numbers make it likely rather than theoretical.

Here's the scenario. On September 6, 2026, nodes running Bitcoin Knots 29.2 start rejecting blocks that contain Ordinals inscriptions or Runes. Miners, who are 99% not signaling support for BIP-110, keep mining blocks with those transactions. The BIP-110 nodes reject those blocks as invalid. You now have two chains: the BIP-110 chain (enforced by upgraded nodes) and the original chain (followed by miners and non-upgraded nodes).

What happens then? Jameson Lopp, a prominent Bitcoin security researcher, and independent analyst Wolfgang Amadeus Vitale have both analyzed the chain split scenario. Vitale's analysis suggests the minority chain — whichever one has less hash power — would produce roughly one block every 17 hours instead of every 10 minutes, making it economically unviable for nearly all uses.

The honest nuance here: "soft fork" vs. "chain split" is semantically contested for BIP-110 specifically. Technically, a soft fork should be backward compatible for economic actors who upgrade. But if BIP-110 nodes reject blocks that miners and non-upgraded nodes accept, from a practical standpoint the network experiences a split — even if it's called a soft fork in the BIP specification. This semantic debate is ongoing in the Bitcoin developer community as of mid-2026.

The SegWit comparison is instructive but shouldn't be over-applied. SegWit succeeded because it achieved near-unanimous miner support before the UASF flag day, so the split never happened. BIP-110 is heading into its flag day at ~1% miner support. That's a fundamentally different starting point.

Why Does BIP-110 Matter for Bitcoin DeFi?

If you're using Bitcoin for anything beyond simple peer-to-peer transfers — yield protocols, cross-chain swaps, wrapped BTC on Ethereum — BIP-110 matters in several interconnected ways.

The Direct Impact: BRC-20 and Runes Projects

Projects built on BRC-20 tokens or Runes face the most immediate risk. If BIP-110 activates successfully, new token mints and transfers using these protocols would be invalid under the BIP-110 chain rules. The "Bastiatian effect" — projects preemptively migrating to Ethereum or Solana just to avoid the uncertainty of BIP-110 — is already being observed in the developer ecosystem, according to community analysis. Some crypto projects aren't even waiting for activation; the threat alone is driving migrations.

The Indirect Impact: Fee Dynamics

Ordinals and BRC-20 activity has periodically driven Bitcoin transaction fees to extreme levels. In May 2023, the Bitcoin network briefly saw average transaction fees exceeding $30 due to BRC-20 activity congesting the mempool. If BIP-110 suppresses this activity, fee dynamics change — potentially for the better for ordinary financial transactions, but also reducing miner revenue from those fee spikes, which is one reason miners are reluctant to signal support.

The Uncertainty Impact: Bridge and Wrapping Protocols

Any bridge or protocol that processes Bitcoin transactions needs to know which chain's rules it's following. During a contested activation or chain split period, this becomes operationally complex. Protocols need to decide: which chain do we treat as "real Bitcoin"? This is less a technical problem than an operational and coordination one.

What Does BIP-110 Mean for Bitcoin Bridges?

Here's the key distinction that often gets lost in the BIP-110 coverage: BIP-110 restricts non-financial data in Bitcoin transactions, not financial transactions themselves. Standard Bitcoin transfers — moving BTC from one address to another — are completely unaffected by BIP-110's rules.

For bridge protocols that move BTC to other chains, the relevant question is: do those protocols embed non-financial data in the Bitcoin transactions they create? Most trustless bridge designs don't. They verify standard Bitcoin payment transactions and use light-client proofs (SPV proofs) to confirm those payments happened on-chain.

TeleSwap, for example, uses an SPV light-client proof model — it verifies actual Bitcoin payment transactions rather than embedding data in witness fields. Users bridging BTC to Ethereum, Solana, TON, or other supported chains through TeleSwap are moving value via standard financial transactions, which BIP-110 does not restrict. Since launching, TeleSwap has processed over 446,396 bridge transactions totaling $430.7M in volume, according to TeleSwap network stats — volume built on standard Bitcoin payment verification that sits entirely outside what BIP-110 targets.

Where bridges do face risk is if they interact with BRC-20 tokens or Runes-based assets. Any bridge that wraps BRC-20 tokens as ERC-20s, for instance, would face operational questions if the underlying token standard becomes restricted on Bitcoin under BIP-110.

The Custodial vs. Trustless Distinction

It's worth noting that not all wrapped BTC solutions are created equal when it comes to navigating protocol uncertainty. Custodial wrapped BTC solutions — where a centralized custodian holds the BTC and issues tokens on your behalf — depend on the custodian's decision about which chain they recognize during a split. Trustless solutions that verify Bitcoin SPV proofs can be upgraded to recognize the correct chain based on proof-of-work, without a custodian making that call on your behalf.

The practical takeaway: trustless, light-client-verified bridges are structurally better positioned to navigate chain-split scenarios than custodial ones, because the resolution path is cryptographic rather than organizational.

What Risks Should You Watch For?

Beyond the chain split scenario, BIP-110 carries several specific risks that haven't gotten enough attention in mainstream coverage.

The Fund Lockup Risk

This is arguably the most underreported risk. BIP-110 grandfathers existing UTXOs — but that grandfathering has edge cases. According to Jameson Lopp's analysis, some scenarios could result in funds being locked:

• Pre-signed transactions: If a wallet created a pre-signed transaction before BIP-110 activation that uses data structures now prohibited by BIP-110, that transaction may become invalid post-activation even though the UTXO existed pre-activation.
• Experimental Tapleaves: Certain experimental Taproot script paths not yet widely activated could be affected.

Lopp notes directly: "There's no way to be sure of how many wallets could be affected." No comprehensive audit of potentially affected wallets has been published. This is a non-trivial concern, especially for users of advanced Bitcoin scripts, multisig setups, or certain hardware wallet configurations.

The Implementation Fragmentation Risk

Bitcoin Core has not endorsed BIP-110. The only available implementation is Bitcoin Knots 29.2. This creates a fragmented node ecosystem: some nodes enforcing BIP-110 rules, most not. During the activation window, this fragmentation means different nodes may have different views of which transactions are valid — a temporary but disorienting state for wallets, exchanges, and bridges trying to confirm transaction finality.

The Precedent Risk

Even if BIP-110 expires after one year as designed, the precedent it sets matters. If a contentious UASF with minimal miner support successfully activates, it signals that future protocol changes can bypass miner consensus with a sufficiently organized node operator coalition. Depending on your view, this is either a feature (users reclaiming sovereignty from mining pools) or a risk (reduced predictability of Bitcoin's consensus process).

The BIP-110 Timeline: Key Dates at a Glance

Frequently Asked Questions

What is BIP-110 in simple terms?

BIP-110 is a proposed temporary rule change for Bitcoin that would block Ordinals inscriptions, BRC-20 tokens, and Runes from being added to Bitcoin blocks for about one year. It's called a "soft fork" because it tightens existing rules rather than replacing them entirely. Think of it as a temporary ban on using Bitcoin's block space for non-financial data like digital art or token records.

When will BIP-110 activate?

The scheduled enforcement date is approximately September 6, 2026, at Bitcoin block height 965,664. This date is determined by the UASF pathway, which doesn't require miner approval. The mandatory signaling window opens around August 9, 2026 (block 961,632), with lock-in by approximately August 23, 2026 (block 963,648), according to Bitcoin Magazine's coverage.

Is BIP-110 going to split Bitcoin into two chains?

A chain split is a real risk given that miner support is only ~1% as of July 2026, far below the 55% threshold needed for miner-activated activation. If nodes enforcing BIP-110 reject blocks from non-signaling miners, two competing chains could emerge temporarily. The minority chain would produce roughly one block every 17 hours instead of every 10 minutes, making it economically unviable — but the transition period could cause confusion for wallets, exchanges, and DeFi protocols.

Does BIP-110 affect my ability to send and receive Bitcoin?

Standard Bitcoin payments — sending BTC from one address to another — are not affected by BIP-110. The proposal only restricts non-financial data: Ordinals inscriptions, BRC-20 token operations, Runes, and oversized OP_RETURN payloads. If you're just sending or receiving BTC, your wallet and transactions remain fully valid under BIP-110 rules.

What happens to existing Ordinals and BRC-20 tokens if BIP-110 activates?

Existing Ordinals inscriptions and BRC-20 tokens created before BIP-110 activation are grandfathered in — the UTXOs that contain them are not invalidated. What changes is that new inscriptions and new token mints would be rejected by BIP-110-enforcing nodes after activation. However, there are edge cases involving pre-signed transactions that could affect some wallets; Jameson Lopp notes no comprehensive audit of potentially affected wallets exists.

How does BIP-110 affect Bitcoin bridges and wrapped BTC?

Bitcoin bridges that verify standard payment transactions using SPV light-client proofs are not directly affected by BIP-110, since those bridges don't rely on Ordinals or Runes functionality. The main risk for bridges is operational: during a chain split scenario, bridge protocols must determine which chain they recognize. Trustless, collateral-backed bridges that follow proof-of-work have a clearer resolution path than custodial wrapped BTC solutions that rely on a company or committee to decide.

What is a UASF and why does it matter for BIP-110?

A User-Activated Soft Fork (UASF) is a mechanism where Bitcoin node operators — rather than miners — enforce new consensus rules by upgrading their software. BIP-110 uses a UASF pathway with a "flag day" of approximately August 9, 2026, meaning nodes running Bitcoin Knots 29.2 will start enforcing BIP-110 rules automatically on that date regardless of miner support. The same mechanism was used to activate SegWit in 2017, though SegWit had near-unanimous miner support before its flag day — BIP-110 does not.

Is BIP-110 permanent?

No — BIP-110 is explicitly designed as a temporary measure with an automatic expiry approximately one year after activation (~52,416 blocks, or roughly September 2027). This temporary nature is the reason the activation threshold is 55% instead of the standard 95% required for permanent Bitcoin protocol changes. After expiry, the restrictions automatically lift unless a new proposal extends or makes them permanent.

---

BIP-110 is one of the most consequential Bitcoin protocol debates since SegWit, and it's moving fast. Whether it activates cleanly, triggers a temporary chain split, or quietly expires without significant network adoption will shape the near-term trajectory of Bitcoin DeFi, token protocols, and cross-chain infrastructure through 2027.

The clearest takeaway for users right now: standard BTC transfers and trustless bridge activity are not what BIP-110 targets. If you're bridging BTC to access DeFi on other chains, protocols that verify Bitcoin payments via SPV proofs — rather than interacting with Ordinals or BRC-20 data — sit outside the scope of what BIP-110 restricts. Across 13 supported networks and $430.7M in total bridged volume according to TeleSwap network stats, TeleSwap's light-client verified bridge is exactly that kind of infrastructure.

Want to move BTC across chains without relying on custodians — regardless of what Bitcoin's protocol debates bring? Explore TeleSwap at teleswap.xyz and see how trustless Bitcoin bridging works in practice.