Coincheck’s October 9 update gives Bitcoin holders a clear example of how an exchange can continue serving BTC while declining to support an asset created by a planned fork. The company says it currently plans neither to handle eCash, ticker ECX, nor distribute it to customers. BTC trading, deposits and withdrawals are expected to continue, subject to possible protective suspensions. Coincheck’s October 9 notice
The announcement concerns a proposed separate blockchain associated with Paul Sztorc and LayerTwo Labs. ECX is also distinct from the existing cryptocurrency using the eCash name and ticker XEC. Checking the ticker is therefore part of understanding the announcement. Coincheck’s project identification
What the fork would create
The ECX project describes a new ledger starting from a Bitcoin snapshot, with a planned one-for-one allocation. Its launch guidance says BTC itself remains unchanged by that copying process, while BTC and ECX subsequently have separate balances and transaction histories. Matching starting quantities provide no assurance of matching market prices or exchange support. The project’s explanation for BTC holders
For readers, the consequence is that a fork announcement cannot establish an increase in spendable wealth. There are several further questions: whether the chain launches as described, whether the holder can safely access the resulting asset, and whether there is a usable market for it. This article makes no valuation claim about ECX.
Exchanges make their own operational decisions
An exchange notice can address trading, transfers and distributions separately. A customer who reads only that BTC service will continue may miss the decision that matters to a hoped-for fork allocation.
GMO Coin’s September 15 notice illustrates another distinction. It said the beta phase would bring no distribution of new coins or yen equivalent, and no balance check for that purpose. Its response to the permanent launch, including any service suspension, would be announced separately. These were dated decisions about different phases, rather than one blanket commitment covering the project. GMO Coin’s third notice
A useful reading method is to write down the asset, network phase and service covered by each statement. Imagine a hypothetical provider that permits ordinary BTC withdrawals but has made no decision about ECX withdrawals. Those statements can coexist. Asking whether the provider supports the fork is too broad; the answer needs to identify the particular operation a customer expects.
Keep the block target beside the calendar date
The project’s roadmap places the permanent launch around Bitcoin block 973,728, with October 31, 2026 as its approximate calendar target. It identifies alpha and beta as separate rehearsals and says mainnet starts from a fresh Bitcoin snapshot. ECX roadmap
GMO Coin also cautions that block production can shift the indicated dates. A calendar reminder is useful preparation, but checking the relevant block and the latest announcement is necessary before treating the event as completed. Scheduling qualification
Technical details need the same attention to status. The project’s fast-facts page labels its parameters as a betanet reference reviewed September 24, explicitly warning that they are not guaranteed final mainnet parameters. Readers should preserve that qualification when encountering copied specifications elsewhere. Betanet reference and mainnet caveat
Similar addresses can conceal separate networks
That reference lists Bitcoin-style address formats and opt-in replay protection. An address that looks familiar therefore does not, by itself, identify a supported deposit network. ECX technical reference
Coincheck expressly warns customers against sending ECX to its BTC receiving addresses. That is a concrete operational restriction, regardless of whether another application accepts the address’s format. Coincheck’s deposit warning
Replay creates a separate risk. The project’s coin-splitting guidance explains that an ordinary transaction can be copied between the two networks, and that merely changing its destination does not prevent this. It also says a beta split does not separate later mainnet coins, and that only the outputs actually included in a successful split are covered. Replay and splitting limitations
These details call for release-specific wallet guidance. This article is not a transaction procedure: an incomplete understanding of which network, outputs and software are involved is a reason to pause.
Preparation can begin without moving funds
The project says there is no pre-claim registration form and that holders can leave shared coins untouched while they establish a verified procedure. It also warns readers to keep recovery phrases private. The project’s safety guidance
For now, save the relevant exchange notice, check its date, and identify what remains undecided. Treat launch timing, customer distribution and safe transaction handling as separate checks. Coincheck’s update makes one provider’s position clearer. Each holder still needs the policy and software documentation that apply to their own setup.