OBTC is Bitcoin-derived and inherits historical Bitcoin UTXO state at the candidate fork height.
Current candidate values
- Fork height:
1000000, provisional - Expiry enable / activation height:
1002016, provisional - Historical expired-backlog threshold under current parameters:
h_create <= 639136
Do not move BTC or expose private keys based on this page. Final claim guidance requires final release artifacts, replay-protection review, wallet readiness, and public safety instructions.
FAQ
Do I automatically have OBTC if I held BTC at the fork height?
OBTC is designed as a Bitcoin-derived system, so historical Bitcoin UTXO state is part of the candidate model. The exact user-facing claim process is not final public guidance yet and depends on final release artifacts, replay-protection review, wallet readiness, and safety documentation.
Do I need to move my BTC?
No public instruction exists yet. Do not make a claim flow before final safety docs are published, and do not expose private keys to experimental tooling.
What does replay protection protect?
Replay protection is intended to reduce cross-chain signature confusion. In plain language, it helps separate OBTC transactions from Bitcoin transactions so one chain's transaction data is not accidentally accepted as the other chain's action.
Is mainnet-candidate production?
No. Mainnet-candidate does not mean production-ready financial infrastructure.