Bitcoin eCash Fork Enters Alpha Testing Ahead of October Mainnet Launch

The mainnet split targets block 973,728, estimated around October 31 — a calendar date that moves with network hash rate. Block height, not date, is the operational variable to track.

Protocol mechanics and unresolved parameters

Three phases structure the deployment roadmap. Alpha at block 963,648. Beta near block 967,680, projected around September 20. Mainnet near block 973,728. Explorer data shows the alpha chain progressed from block 963,648 to at least 963,650, with a competing block visible at the starting point. Mempool.space recorded Bitcoin's block 963,648 at a timestamp of 01:48:47 UTC on August 23, 2026. Parallel chains at identical block heights indicate a test network running alongside mainnet, not a replacement of the consensus mechanism.

The integration guide, updated August 11, remains in pre-launch status. It references block 963,648 as the production fork point. Critical values are marked as drynet4 parameters. The final fork hash, software branch or tag, and replay mechanism have not been announced. The current coin-splitting method uses an optional nLocktime value of 499999999 for ECX transactions. Integration partners must verify the final method before launch.

Replay protection is the critical open issue. The new network copies Bitcoin's full transaction history. A BTC-signed transaction could execute on the ECX chain without dedicated safeguards. Recent technical examinations have flagged replay security as unresolved. Mainnet deployment must demonstrate users can move BTC without broadcasting identical signatures to the eCash network. Absent that proof, every BTC transaction carries secondary execution risk on ECX.

Custodial exposure and allocation path

Project founder Paul Sztorc indicated test units may be exchangeable for real ECX post-mainnet, citing 1,000 pECX redeemable for 10 ECX as an example ratio. Current documentation does not confirm alpha balances or transaction history will carry over to beta or mainnet. That gap means alpha participation does not guarantee future ECX allocation.

Japanese exchange posture reflects broader uncertainty. GMO Coin announced it will not support pECX or ECX transactions during alpha and beta. Coincheck, SBI VC Trade, and Zaif have not issued definitive decisions on listing, crediting, or processing ECX. Custodial users will not see split coins unless their platform explicitly supports the fork. Self-custody holders controlling private keys can claim ECX directly once allocation software ships. Exchange account holders depend entirely on third-party platform policy.

Verdict

Block 973,728 is the binary trigger. Hash rate fluctuations will shift the estimated date. Replay protection documentation must appear before mainnet — without it, moving BTC becomes a risk vector for unintended ECX exposure. Exchange announcements from Coincheck, SBI VC Trade, and Zaif will determine whether custodial holders participate at all. Speculative positioning tracked through live crypto trading signals offers secondary market context, but fork economics remain decoupled from price action until allocation mechanics are finalized. The project is live on testnet but operationally incomplete on mainnet.