How to Use Bitcoin BIP110 Safely

Bitcoin BIP110 Users Guide

This guide provides practical information for anyone seeking to understand, access, and safely use Bitcoin BIP110. It covers ownership following the Bitcoin BTC chain split, wallet and exchange support, coin separation, compatibility with existing Bitcoin BTC features, security risks, and the current operational status of the network.

Bitcoin BIP110 is live under BLAKE2b proof of work. Wallet support, exchange support, network infrastructure, and other services may still be coming operational. BitcoinBIP110.org will document verified support and provide guidance as that infrastructure becomes available.

Ownership and Access

I own Bitcoin BTC. How do I know if I have Bitcoin BIP110?

Bitcoin BTC and Bitcoin BIP110 share the same blockchain history through block 961,631. Their block histories diverged beginning at block 961,632.

If you held Bitcoin BTC before the time of the split, roughly 8 August 2026, you should also have corresponding Bitcoin BIP110 coins on the Bitcoin BIP110 blockchain.

If you held Bitcoin in self-custody

If your Bitcoin BTC was controlled by a self-custody wallet for which you hold the private keys or seed phrase, and those coins existed before the chain split, you should also own the corresponding Bitcoin BIP110 coins.

Your Bitcoin BTC does not need to be converted, exchanged, registered, or redeemed to create Bitcoin BIP110. Your Bitcoin BIP110 coins are already on the Bitcoin BIP110 chain. You will be able to control them using the same private keys that controlled your Bitcoin BTC before the split.

If your Bitcoin was held by an exchange or custodian

If an exchange, broker, ETF, wallet service, or other custodian controlled the private keys at the time of the split, then that service controls the corresponding keys on the Bitcoin BIP110 chain. See the Exchange Support selction for more details.

If you received Bitcoin BTC after the split

Bitcoin BTC received from transactions occurring after block 961,631 does not automatically have a corresponding Bitcoin BIP110 balance.

From block 961,632 onward, Bitcoin BTC and Bitcoin BIP110 are on seperate branches.

How can I check my Bitcoin BIP110 balance?

Bitcoin BIP110 blocks, transactions, and addresses can be inspected using Mempool.Guide.

You can enter a Bitcoin-style address and inspect the corresponding activity on the Bitcoin BIP110 chain. Because BTC and BIP110 share compatible-looking address formats, make sure you are using the Bitcoin BIP110 explorer and network context.

The verified explorer currently referenced by BitcoinBIP110.org is Mempool.Guide.

How do I access my Bitcoin BIP110?

If you controlled Bitcoin BTC before the chain split, the corresponding pre-split coins may already exist under the same keys in the Bitcoin BIP110 ledger.

You do not need to register, redeem, convert, or claim them from another party.

Accessing these coins requires a Bitcoin BIP110-compatible wallet software capable of recognizing the Bitcoin BIP110 network and creating valid transactions for it. See the Wallet Support section for more details.

We strongly recommend you perform safely seperate your Bitcoin BIP110 from your Bitcoin BTC before attempting to move either coin. See the Coin Seperation section for more details.

Your Bitcoin seed phrase or private keys may control valuable coins on both Bitcoin BTC and Bitcoin BIP110.

Entering those credentials into an unverified wallet, website, claiming tool, or third-party service could expose coins on both networks.

It is often safer to wait until your existing wallet client or your existing exchange supports Bitcoin BIP110 before attempting to access it.

Be especially cautious of websites or individuals offering to "claim your Bitcoin BIP110" in exchange for your seed phrase, private keys, wallet file, or an upfront payment.

Exchange Support

What if I held Bitcoin on an exchange or with a custodian?

Holding Bitcoin BTC through an exchange or custodian is different from holding Bitcoin BTC in self-custody.

The party controlling the private keys at the time of the split controls the corresponding Bitcoin BIP110 coins.

If your Bitcoin BTC was held by an exchange, broker, custodial wallet, ETF, or similar service, you should not assume that you personally have direct access to the corresponding Bitcoin BIP110. Whether you receive access to any Bitcoin BIP110 associated with your account depends on the custodian's policies and support for the network.

The service may choose to:

• Support Bitcoin BIP110 and provide access to customers.
• Distribute corresponding coins at a later date.
• Support trading without deposits or withdrawal.
• Delay a decision while the network develops.
• Provide no Bitcoin BIP110 support.

Reputable exchanges and custodians should make an official statement describing its Bitcoin BIP110 policy. If your exchange or custodian has not yet provided support for Bitcoin BIP110, either wait till they provide support for Bitcoin BIP110 or contact your exchange or custodian directly to confirm whether they plan to provide access to Bitcoin BIP110.

How do I buy, sell, and trade Bitcoin BIP110?

Bitcoin BIP110 can be transferred peer-to-peer. Exchange availability depends on each service's independent decision to support Bitcoin BIP110 deposits, withdrawals, custody, or trading.

BitcoinBIP110.org publishes exchange support only after the service and its operational network support can be verified.

Which exchanges support Bitcoin BIP110?

The project-declared listing name is Bitcoin BIP110 and the project-declared ticker is BIP110. An exchange may use a different internal or public symbol if required to avoid a ticker collision.

Do not send Bitcoin BIP110 to an exchange unless the exchange has explicitly confirmed support for the Bitcoin BIP110 network. Support for Bitcoin BTC does not imply support for Bitcoin BIP110.

Wallet Support

Which wallets support Bitcoin BIP110?

Bitcoin Knots, the primary node maintainers of Bitcoin BIP110 has a native node and wallet in one.

Can I use my existing Bitcoin BTC wallet with Bitcoin BIP110?

The fact that Bitcoin BTC and Bitcoin BIP110 share historical keys, addresses, and pre-split ownership does not mean that ordinary Bitcoin wallet software is compatible with Bitcoin BIP110.

Some wallets may eventually add native Bitcoin BIP110 support. Others may never support it.

Verify the exact wallet, version, download source, network support, and transaction behavior first.

Do hardware wallets support Bitcoin BIP110?

There are no hardware wallets that currently support Bitcoin BIP110. BitcoinBIP110.org will post it here once a hardware wallet adds support for BitcoinBIP110.

A hardware wallet may be capable of signing Bitcoin BTC style transactions while its companion software, firmware, derivation handling, network identification, or transaction validation does not properly support Bitcoin BIP110.

Do not treat the signing capability as support. Wait until the specific hardware wallet publishes their official support of Bitcoin BIP110.

Coin Separation

What is coin separation?

Coin separation, sometimes called coin splitting, is the process of establishing independent control over corresponding coins on two chains after a blockchain split.

The objective is to reach a state where:

• Bitcoin BTC can be spent without unintentionally spending Bitcoin BIP110
• Bitcoin BIP110 can be spent without unintentionally spending Bitcoin BTC

How do I safely separate my Bitcoin BTC and Bitcoin BIP110?

Currently, the safest way to perform a coin separation is to send your Bitcoin BTC from your pre-split address to a new address that you control with an OP_RETURN of greater than 83 bytes.

The reason this works is because Bitcoin BIP110 does not allow transactions with OP_RETURN greater than 83 bytes. Therefor, only your Bitcoin BTC would move to the new address. See this coin seperation video by Bitcoin University for more details.

Can I move my Bitcoin BTC and still access my Bitcoin BIP110?

Moving Bitcoin BTC after the split does not erase the historical Bitcoin BIP110 ledger.

The two networks have separate block histories beginning at height 961,632. A Bitcoin BTC transaction that occurs only on Bitcoin BTC does not automatically spend the corresponding coins on Bitcoin BIP110.

However, transactions involving pre-split coins can create complexities because similar transactions may be valid on both networks.

If you have pre-split Bitcoin BTC, the best practice is to perform a coin seperation first.

If you have already moved your Bitcoin BTC after the split, this does not necessarily mean your Bitcoin BIP110 is lost. You must keep a record of the addresses and private keys associated with Bitcoin BTC that you moved in order to access the Bitcoin BIP110 that may still be in your account.

Integration Support

Are Lightning, Taproot, SegWit, and other Bitcoin features compatible with Bitcoin BIP110?

Bitcoin BIP110 inherits Bitcoin's transaction model and the consensus features that existed before the chain split, including SegWit and Taproot. The transition to BLAKE2b changes proof-of-work and the block-header format; it does not replace Bitcoin's underlying transaction system.

SegWit

Bitcoin BIP110 continues to recognize standard SegWit constructions. BIP 110 explicitly identifies witness version 0 P2WPKH and P2WSH as defined witness types.

When the reduced-data rules are active, some witness data is subject to additional size restrictions. Standard SegWit therefore remains available, but every possible Bitcoin BTC witness construction may not be compatible.

Taproot

Taproot also remains part of Bitcoin BIP110. Pay-to-Taproot, or P2TR, is explicitly recognized as a defined witness version under BIP 110.

Certain Taproot and Tapscript features are restricted while the reduced-data rules are active, including Taproot annexes, very large control blocks, OP_SUCCESS*, and some Tapscript uses of OP_IF and OP_NOTIF. Taproot key-path spending and permitted script-path constructions remain available.

Lightning Network

Lightning is an additional protocol built on Bitcoin transactions rather than a base-layer consensus feature.

Bitcoin BIP110 retains many of the transaction features that Lightning depends on, so Lightning functionality can potentially be implemented for the network.

Existing Bitcoin BTC Lightning channels should not be treated as automatically portable to Bitcoin BIP110. During a persistent chain split, a Lightning node watching one chain can be unaware of a channel transaction occurring on the other chain. This creates particular risks around revoked channel states and time-sensitive penalty transactions.

BitcoinBIP110.org will document Lightning support when compatible implementations and operational infrastructure have been verified.

Other Bitcoin features

Bitcoin BIP110 inherits much of Bitcoin's existing transaction functionality, but compatibility should be evaluated feature by feature.

Some functionality may be affected by:

• The BIP 110 reduced-data consensus rules.
• The BLAKE2b block-header and proof-of-work transition.
• Wallet and light-client compatibility.
• Differences in network infrastructure.
• Bitcoin BIP110-specific transaction or replay-protection rules.

Software or services that support Bitcoin BTC does not automatically establish support for Bitcoin BIP110.

Does Bitcoin BIP110 support Ordinals, Inscriptions, and Tapscript?

Bitcoin BIP110 retains Taproot and Tapscript functionality, but the reduced-data rules place additional restrictions on certain script constructions and large data pushes. As a result, ordinary Tapscript use remains possible, while the common transaction patterns used for Ordinals and Inscriptions are generally incompatible with the reduced-data rules once they are active.

Tapscript

Tapscript will be supported, but with additional restrictions.

Bitcoin BIP110 continues to recognize the Taproot witness version and the defined Tapscript Tapleaf version. It does not disable Taproot or Tapscript as a whole.

While the reduced-data rules are active, however, several Tapscript constructions are restricted. Among them:

• OP_SUCCESS* opcodes are invalid
• executing OP_IF or OP_NOTIF in Tapscript is invalid
• Taproot annexes are invalid
• Taproot control blocks larger than 257 bytes are invalid
• individual script-argument witness items larger than 256 bytes are invalid

These rules deliberately preserve ordinary monetary and scripting functionality while restricting several methods used for embedding arbitrary data.

Ordinals and Inscriptions

Ordinals and Inscriptions will not be supported under Bitcoin BIP110's reduced-data rules.

The Ordinals protocol itself is an external indexing convention rather than a Bitcoin consensus feature. However, the common inscription method embeds data inside a Taproot script-path spend, typically using a Tapscript envelope involving OP_IF and data pushes.

BIP 110 specifically restricts these mechanisms. Its rules prohibit executing OP_IF or OP_NOTIF in Tapscript and restrict large arbitrary-data pushes. The BIP explicitly describes limiting arbitrary-data storage as one of its purposes.

This means the standard inscription patterns commonly used on Bitcoin BTC would generally fail the Bitcoin BIP110 reduced-data rules for post-activation outputs.

The only exception applies to inputs spending UTXOs created before the reduced-data activation height. These UTXOs are grandfathered and remain exempt from the new restrictions, preserving their spendability under the pre-activation rules.

Security, Scams, and Risks

What fraud, scams, and risks should I be aware of?

The Bitcoin BIP110 chain split creates opportunities for scammers, malicious software, and costly user mistakes.

You must be especially cautious when attempting to access, move, exchange, or separate coins associated with the two networks.

The following will go over some common scams and risks that the community is already seeing.

Fake claiming tools

Scammers may create websites or applications claiming that they can "claim," "unlock," or "recover" your Bitcoin BIP110.

A legitimate Bitcoin BIP110 balance does not need to be granted by a third party.

Never provide a seed phrase, private key, wallet backup, or wallet file to a claiming service.

Fraudulent wallets

Attackers may distribute fake Bitcoin BIP110 wallets designed to steal private keys or seed phrases.

This risk is particularly serious because the same keys may control valuable coins on both Bitcoin BTC and Bitcoin BIP110.

Only use software whose source, release, version, and authenticity can be independently verified.

Phishing and impersonation

Scammers may imitate Bitcoin BIP110 websites, developers, exchanges, maintainers, or support personnel.

Be cautious of:

• Misleading or misspelled domain names.
• Unsolicited messages offering assistance.
• Links distributed through social media or direct messages.
• Fake software downloads/
• Requests for seed phrases or private keys.
• Claims that immediate action is required.
• Fake announcements claiming wallet or exchange support.

No support representative will ask you for your seed phrase or private keys.

Fake or misleading exchanges

A website may falsely claim to support Bitcoin BIP110 deposits, withdrawals, trading, or distribution.

Before sending funds, independently verify that the service actually supports the Bitcoin BIP110 network and determine exactly which functions are available.

Do not assume that an exchange supporting Bitcoin BTC also supports Bitcoin BIP110.

Sending coins on the wrong network

Bitcoin BTC and Bitcoin BIP110 have separate block histories beginning at height 961,632.

You may lose access to funds by:

• Sending coins to a service that supports only the other network.
• Using incompatible wallet software.
• Misunderstanding which network a wallet is connected to.
• Assuming similar-looking addresses indicate network compatibility.

Always verify the destination service and network before sending.

Loss of access

Users can also lose access without being directly scammed.

Possible causes include:

• Discarded wallet backups.
• Forgotten wallet information.
• Incompatible software.
• Incorrect network configuration.
• Exposing keys to malicious software.
• Misunderstanding replay behavior.
• Sending funds to unsupported services.

What is a replay attack?

After a blockchain split, the same pre-split private keys may control coins on both chains.

If the two networks recognize the same transaction format and signature rules, a transaction created for one network may also be valid on the other. If that transaction is copied and broadcast on the second network, it has been replayed.

For example, a user may intend to spend Bitcoin BTC while leaving the corresponding Bitcoin BIP110 untouched. If the transaction is also valid on Bitcoin BIP110 and is broadcast there, the corresponding BIP110 coins could move as well.

The reverse situation may also be possible.

Bitcoin BIP110 development includes an opt-in SIGHASH_UNIFIED mechanism intended to make certain signatures chain-specific. Users should rely on the final mainnet rules and verified wallet behavior before assuming that a transaction is protected from replay.

Replay attacks only apply to pre-split coins. The best way to prevent a replay attack is to perform a coin seperation. See the Coin Seperation section for more details.

Is there a deadline to access my Bitcoin BIP110?

There is no deadline to access your Bitcoin BIP110 coins. The coins already belong to you if you have access to the private keys associated with your Bitcoin BTC pre-split.

Any person or website asking you to "claim" your Bitcoin BIP110 is fraudulent and should be avoided.