What happens to your Bitcoin if Bitcoin’s rules change?
Bitcoin can change through soft forks and hard forks. Most rule changes do not automatically create two lasting versions of Bitcoin.
For clients using collaborative multisig, the practical questions are what happens to the vault, what your wallet provider’s software may support, and when it is safe to act.
This guide explains those mechanics, including why BIP-110 has prompted questions and why TBA would wait for facts before recommending any action.
Two ways Bitcoin’s rules can change
A soft fork adds stricter rules. Older nodes do not enforce those new restrictions, but blocks that follow the stricter rules can still satisfy the older rules.
A hard fork permits something that the previous rules reject. Two chains can continue if both rule sets retain enough technical and economic support.
| Question | Soft fork | Hard fork |
|---|---|---|
| What changes? | The rules become more restrictive. | The rules allow something the previous rules reject. |
| What normally happens? | One chain continues if the stricter rules gain broad adoption. | Two chains can continue if both rule sets retain support. |
| Does it automatically create a separate continuing chain? | No. | No, but incompatible rules make a persistent split more directly possible. |
| What matters to a client? | Whether wallets and providers can construct and relay valid transactions. | Which chains remain usable, supported and economically relevant. |
What happens during a soft fork?
- A proposed rule change defines additional restrictions.
- Nodes choosing to enforce those rules reject blocks or transactions that violate them.
- If the network converges around those rules, one blockchain history continues.
- Bitcoin held before the change remains represented by the same existing UTXOs on that continuing history.
- Wallets and services may need software changes to construct transactions that comply with the new rules.
A soft fork does not automatically create two independent blockchain histories.
If the network converges around the stricter rules, one history continues. A persistent split only develops if incompatible rule enforcement continues across economically and technically significant parts of the network.
BIP-110 is discussed below as a temporary soft-fork proposal. The proposal itself is not proof that a split is imminent.
What does not require you to move Bitcoin
- The existence of a proposal.
- The publication of a BIP.
- A wallet provider updating its software.
- Network disagreement that has not produced a material, persistent split.
Action becomes relevant when the actual network conditions and their implications for your vault are known.
What your wallet provider’s node choice can affect
TBA clients may use Theya or Unchained as the software and infrastructure around a collaborative multisig vault. If a provider chooses a node policy during a disputed rule change, that choice can affect how you use its app.
It can affect
- What you see: which blockchain history, transactions and balances the app displays.
- What the software can build: whether the wallet can construct transactions valid under a particular chain’s rules.
- What can be broadcast: which network the provider’s infrastructure sends transactions to.
- Provider-assisted signing and support: whether provider-assisted services, transaction coordination or support operate on that chain.
- Temporary operating restrictions: the provider may pause some functions while the technical situation is unclear.
It does not, by itself
- Rewrite the vault’s existing multisig spending conditions.
- Change the keys already associated with the vault.
- Transfer ownership of the Bitcoin.
- Require the client to choose a side immediately.
TBA will not invent Theya’s, Unchained’s or any other provider’s decision in advance. If a provider publishes its technical position, or a split becomes material, TBA can assess the practical effect on client vaults. Until then, there is no need to rush.
Your vault and your provider are not the same thing
The vault exists through Bitcoin’s on-chain spending conditions and the keys authorised to satisfy them.
The provider supplies the software and infrastructure used to view, construct, coordinate and broadcast transactions.
A provider’s software decision can affect how easily you interact with a particular chain. It does not, by itself, rewrite the vault or change who controls its keys.
Guessing early can create more risk than the fork itself
Before a disputed network change settles, transaction replay, changing validity rules, incomplete wallet support, chain reorganisations and thin markets can make unnecessary transactions harder to unwind.
Replay risk is real in some fork scenarios. Bitcoin Core and the wider ecosystem stressed replay protection during contentious chain changes in 2017.
There is no universal fork playbook. The safe response depends on what actually happened.
Until the facts are known, preserving optionality is usually more valuable than acting quickly.
Why BIP-110 has prompted this question
BIP-110 has prompted discussion about Bitcoin consensus rules and what could happen if different parts of the network enforced different policies.
BIP-110 is currently a draft proposal for a temporary soft fork. A soft fork does not itself mean Bitcoin will split into two lasting chains.
A BIP is a technical proposal. Publication does not mean it has achieved network consensus or that adoption is imminent.
TBA takes no position on whether BIP-110 should be adopted. Our concern is narrower: understanding any practical implications for client vaults if a material network split were to develop.
How TBA would respond
TBA would not recommend immediate action merely because competing rules or chains had appeared.
We would assess:
- The consensus and technical characteristics of each chain.
- Whether the split appeared temporary or persistent.
- The published policies and technical capabilities of the relevant vault provider.
- Transaction replay and other chain-specific risks.
- Safe ways to control or separate assets, where applicable.
We would then give clients specific guidance before recommending that Bitcoin be moved.
Our job is not to predict a winner in a consensus dispute.
It is to preserve client optionality, avoid unnecessary action and wait until the technical facts are clear enough to give specific guidance.
Common questions
What would Theya or Unchained do during a fork or chain split?
We cannot know in advance. A wallet or vault provider may choose which network its nodes follow, update its transaction software, pause some functions, or introduce chain-specific procedures.
TBA would not speculate about either provider’s decision before it is published. If a network split became material, we would assess the provider’s actual technical position and explain what it means for affected client vaults.
Would I lose access if my vault provider supported only one chain?
Not necessarily. Provider support and key control are different. A provider may display one chain and let users create and send transactions only on that chain, but that does not remove the existing on-chain spending conditions associated with the vault.
Accessing assets on another chain may require different software, infrastructure or technical procedures. TBA would assess those requirements before recommending action.
What is the difference between a soft fork and a hard fork?
A soft fork adds stricter rules while blocks that follow those rules can still satisfy the older rules. A hard fork permits something the previous rules reject. Neither one automatically creates a separate continuing chain. See the comparison above.
Why shouldn’t I move Bitcoin as soon as a split appears?
Transaction replay, unclear validity rules, incomplete wallet support and thin markets can make early transactions hard to unwind. Waiting preserves your options until the technical facts are clear.
Does TBA support or oppose BIP-110?
Neither. TBA takes no position for or against BIP-110. We focus on practical implications for client vaults if a material network split develops. See why BIP-110 has prompted this question.
Fork and vault glossary
- Consensus rules
- The rules Bitcoin nodes use to decide whether blocks and transactions are valid.
- Soft fork
- A rule change that adds restrictions while remaining compatible with the previous broader rule set.
- Hard fork
- A rule change that permits behaviour the previous rules reject.
- Chain split
- A situation where incompatible blockchain histories continue rather than quickly converging back to one history.
- UTXO
- An individual piece of spendable Bitcoin recorded on-chain.
Questions about your vault?
If you want to understand how collaborative security is structured, or you need client-specific guidance after a material network event, speak with an adviser.
Educational only: general information about forks, chain splits and collaborative multisig vaults. Not financial, tax, legal or investment advice. Not a recommendation about any BIP or consensus change. Seek appropriate licensed professionals where required. See scope, risks & important information.
Also explore
Directory of custody, scam, perimeter and emergency guides.
How TBA 2-of-3 vaults and key agency work in practice.
Device setup and vault signing workflows.
Fees, privacy and spendability inside long-term vaults.
Active incident triage only (scams, stuck txs, lost keys).
Foundational custody models from single-sig to multisig.