BIP-110 May Trigger Bitcoin Fork Risk: Developer Warns Selling Forked Coins Could Put Real BTC at Risk

A controversial Bitcoin proposal known as BIP-110 has renewed an old but serious concern for BTC holders: if a minority chain splits from Bitcoin without replay protection, attempting to sell “free” forked coins could unintentionally move real BTC on the main Bitcoin network.

Bitcoin developer Kevin Loaec has warned that if a BIP-110-related fork emerges around the expected activation height, users who do not understand how to safely separate assets across chains should avoid making transactions. The core issue is not whether a forked token has market value, but whether a transaction signed on one chain can be copied and broadcast on the other.

For long-term Bitcoin holders, this is a reminder that during contentious forks, doing nothing is often safer than rushing to trade.

What Is the BIP-110 Controversy About?

BIP-110 is associated with a proposed rule change aimed at restricting certain non-payment data in Bitcoin transactions, such as embedded images, text, or other arbitrary data. Supporters argue that Bitcoin block space should primarily serve monetary transactions. Critics, however, view stricter filtering as a form of protocol-level censorship or an unnecessary constraint on how users interact with the network.

The immediate concern is that software supporting BIP-110 may begin rejecting blocks that do not follow the proposed data restrictions from a specific block height, reportedly around block 961,632. If most miners and nodes continue following the existing Bitcoin rules while a small group enforces the BIP-110 rules, the result could be two competing chains with shared history up to the split point.

As of the latest market discussion, miner signaling for BIP-110 remains very low, around 2.6%, far below the level typically needed for a smooth consensus upgrade. That makes a durable fork uncertain. Still, even a small minority chain can create operational risks if exchanges, traders, or miners attempt to give it market value.

For background on how Bitcoin improvement proposals are documented, readers can refer to the official Bitcoin BIPs repository.

Why a Bitcoin Fork Can Create “Duplicate” Balances

When a blockchain splits, both resulting chains initially share the same transaction history. If you held 1 BTC before the split, both chains may recognize that same pre-fork balance after the split.

This does not mean you have magically doubled your Bitcoin. It means there may be two separate ledgers that both acknowledge your historical ownership up to the fork point:

• On the original Bitcoin chain, you still hold BTC.
• On the minority fork chain, you may also appear to hold an equivalent amount of forked coins.

This is why contentious forks can attract short-term traders. Some holders may assume they can sell the forked asset while keeping their BTC untouched. That assumption can be dangerous when the fork lacks replay protection.

The Replay Attack Problem Explained

A replay attack occurs when a valid transaction signed on one chain is copied and broadcast on another chain where it is also considered valid.

In a fork scenario without replay protection, the transaction format and signature rules may remain identical across both chains. If you sign a transaction to sell forked coins, the same signed transaction could potentially be replayed on Bitcoin’s main network.

For example:

1. Alice holds 1 BTC before the fork.
2. After the fork, she appears to have 1 BTC on Bitcoin and 1 unit of the forked coin on the BIP-110 chain.
3. Alice tries to sell the forked coin to Bob.
4. She signs a transaction on the forked chain.
5. If both chains accept the same signature, Bob or another party could broadcast that transaction on the Bitcoin network.
6. Alice may lose her real BTC as well.

This is why replay protection is so important. It makes transactions valid on one chain but invalid on the other, reducing the risk that an action on a forked network affects the original chain. A general explanation of this risk can be found in the Bitcoin Wiki’s replay attack overview.

Why “Do Nothing” May Be the Safest Move

Loaec’s warning centers on a simple security principle: if you do not create a transaction, there is no signed transaction to replay.

Unmoved BTC cannot be stolen through replay alone because a replay attack requires an existing valid signature. If a holder simply keeps their coins where they are and avoids interacting with the forked chain, there is no transaction for an attacker to copy.

This does not eliminate every possible risk in a chaotic market environment, but it significantly reduces the most immediate replay-related threat. For average users, especially those who are not deeply familiar with coin splitting, UTXO management, and chain-specific transaction construction, patience is often the most rational strategy.

What Is Coin Splitting?

Coin splitting is the process of separating assets that exist on two chains after a fork so that spending coins on one chain does not spend coins on the other.

In practice, safe splitting may require chain-specific outputs, miner-confirmed transactions, special wallet handling, or receiving coins that exist only on one side of the fork. The exact method depends on how the fork behaves and whether any side implements replay protection after launch.

This is not something users should improvise under time pressure. A mistake can be irreversible.

Bitcoin transactions are final by design once sufficiently confirmed. The same property that makes Bitcoin resistant to chargebacks also means user errors during forks can be costly. For a broader technical background on Bitcoin transaction mechanics, see the Bitcoin developer documentation on transactions.

Why This Matters in 2025

The BIP-110 debate reflects a broader 2025 trend in the Bitcoin ecosystem: disagreement over what Bitcoin block space should be used for.

Over the past few years, Bitcoin has seen growing demand from inscriptions, token experiments, data publishing, and other non-traditional uses of transactions. This has increased fee volatility and intensified debates about spam filtering, miner incentives, censorship resistance, and protocol neutrality.

At the same time, institutional adoption has made BTC custody more important than ever. Spot Bitcoin ETFs, corporate treasuries, and long-term self-custody users have all contributed to a market where operational mistakes can affect larger pools of capital.

A contentious fork, even a small one, can expose users to risks that are not obvious from price charts alone:

• Replay attacks
• Exchange deposit confusion
• Fake forked-coin trading markets
• Phishing campaigns impersonating wallet tools
• Malicious “coin splitting” services
• Premature transactions before the chain situation is clear

In other words, the technical debate may begin among developers and miners, but the consequences can reach ordinary BTC holders quickly.

What BTC Holders Should Consider If a Fork Occurs

If a BIP-110-related split actually appears, BTC holders should avoid rushing into action. The following principles can help reduce risk:

1. Do not move BTC unless necessary

If you do not need to transact, waiting is usually the safest option. Let the network, miners, exchanges, and infrastructure providers determine whether the fork is real, persistent, and economically meaningful.

2. Avoid selling forked coins immediately

The first hours or days after a fork are often the most dangerous. Liquidity may be thin, wallet support may be experimental, and replay protection may be absent.

3. Do not enter your seed phrase into fork-claiming websites

Fork events often attract scams. Any website or tool asking for your recovery phrase should be treated as hostile. Your seed phrase controls your BTC, not just forked assets.

4. Wait for reputable technical guidance

If asset splitting becomes necessary, wait for clear instructions from trusted Bitcoin developers, wallet providers, or infrastructure teams. Do not rely on random social media posts or anonymous tools.

5. Keep keys offline when possible

Hardware wallets help reduce exposure by keeping private keys isolated from internet-connected devices. This does not automatically solve replay risk, but it does reduce the chance of seed theft, malware signing, and phishing-related losses.

Where OneKey Fits In

A hardware wallet cannot change Bitcoin consensus rules or prevent a replay attack by itself. Replay risk comes from chain-level transaction validity, not from the storage device.

However, secure self-custody still matters during uncertain network events. OneKey hardware wallets are designed to keep private keys offline, provide transaction confirmation on a dedicated device, and help users avoid exposing seed phrases to potentially malicious websites or software. During a fork-risk period, that separation between private keys and online environments becomes especially important.

The key takeaway is simple: secure storage protects your keys, but safe decision-making protects your coins.

Final Thoughts

The BIP-110 situation may or may not result in a lasting Bitcoin fork. Current miner support appears far below the threshold normally associated with a successful network-wide rule change, so the most likely outcome remains uncertain.

But the warning from developers is worth taking seriously. If two Bitcoin-like chains temporarily coexist without replay protection, selling forked coins could create a transaction that also moves real BTC. For most holders, the safest response is to wait, avoid signing unnecessary transactions, and ignore “free money” narratives until the technical risks are fully understood.

In Bitcoin, control over your keys is only the first layer of security. Knowing when not to sign is just as important.