Last shared height
The final block present in both histories.
Independent network reference
Bitcoin BIP110
Technical documentation for the independent chain intended to continue the BIP 110 enforcement branch through a BLAKE2b proof-of-work implementation being developed from Bitcoin Knots.
Documentation snapshot: 24 August 2026. Mainnet BLAKE2b activation remains unscheduled.
Network snapshot
One history until height 961,631
Bitcoin mainnet and Bitcoin BIP110 share the Bitcoin ledger through block 961,631. Their block histories diverge beginning at height 961,632.
First divergent height
Enforcing nodes rejected the non-signaling BTC block.
Observed branch tip
SHA-256d enforcement-branch tip observed on 24 August 2026.
Planned proof of work
Testnet implementation exists. Mainnet activation is pending.
Explore the reference
Follow the evidence
Read the chain lineage, verify dated events, and inspect the fields required by node operators, miners, wallets, exchanges, and custodians.
01
From BIP 110 to an independent chain
The original proposal, the enforcement split, and the BLAKE2b continuation.
Read the history →02A dated, verifiable chronology
Separate implemented events from open development work and pending milestones.
Open the timeline →03Integration facts and chain identity
Consensus, address, release, replay, mining, and RPC verification data.
Review technical data →Current state
Development is active. Mainnet parameters are not final.
Verified
The chain split at height 961,632 and the early SHA-256d branch.
Verified on testnet
RC2 BLAKE2b activation at testnet4 height 149,537.
Proposed
BLAKE2b header-v2 proof of work and opt-in unified signatures.
Pending
A signed stable mainnet release, activation height, and first valid block.
Wallet safety
Proof-of-work separation does not prevent transaction replay.
Ordinary transactions can remain valid across compatible histories. The proposedSIGHASH_UNIFIED design is opt-in, signature-specific, and active only in documented RC2 testnet code as of this snapshot.
Do not move inherited coins without understanding replay behavior and verifying the exact software and rules active on both chains.
Review the unified signature-hash proposal