eCash has activated its scheduled November network upgrade, completing a coordination event that separates older Bitcoin ABC nodes from the current chain. Bitcoin ABC's official releases page changed its status to activated on November 15 and warned that nodes running software earlier than version 0.34.0 are no longer synchronized with the network. The activation followed a median-time-past threshold tied to 12:00 UTC, rather than occurring at one exact wall-clock moment. The project had said the threshold would usually be crossed about an hour later, after enough newer block timestamps entered the rolling median.
Replay protection advances without a new protocol feature
The upgrade does not add a transaction type, consensus rule for users or other new protocol feature. Its active change advances eCash's automatic replay-protection marker to timestamp 1810382400, corresponding to May 15, 2027 at 12:00 UTC. Replay protection helps distinguish transactions across upgrade boundaries so that activity intended for one chain state is not unintentionally repeated in another. eCash uses a six-month upgrade cadence, making the protection update a mandatory coordination point even when the release carries no new user-facing protocol capability.
Related reporting: Three Mining Pools Produce 60% of Bitcoin Blocks in Weekly Snapshot
Full-node operators carry the upgrade obligation
Operators of Bitcoin ABC full nodes, including miners, exchanges and Avalanche staking nodes, were instructed to install the 0.34.x series before activation. The latest published build is 0.34.3, which Bitcoin ABC describes as containing additional bug fixes and performance improvements. The network rule itself requires version 0.34.0 or later. Release 0.34.0 also fixed a command-line reporting bug that could incorrectly describe an invalid Avalanche proof delegation as valid, but Bitcoin ABC lists that as a software correction rather than a consensus feature switched on by this upgrade. Operators who missed the cutoff must update and restart their node before it can follow the same rules as the upgraded network. The project's instructions do not require ordinary holders to move tokens, claim an asset or change an Electrum ABC wallet.
Exchanges are handling the event as maintenance
MEXC suspended XEC deposits and withdrawals from 11:00 UTC ahead of the upgrade while leaving trading open. Its support notice said the event would not create a new forked asset and that transfers would resume after the network was stable. ChangeNow separately placed XEC-related maintenance in progress and warned that payouts and exchanges could take longer than usual. Those service controls are operational decisions by the platforms; they do not show a chain failure, and their reopening times may differ from the protocol's activation time.
Activation is confirmed, but service normalization remains separate
The official activation notice establishes that the network crossed its software boundary. It does not prove that every exchange, wallet backend or infrastructure provider has completed its own checks. Users should therefore distinguish between chain activation and the restoration of a particular platform's deposit or withdrawal service. Median time past also deliberately smooths individual block-clock variation by using the median timestamp of the previous 11 blocks, which is why the upgrade page did not promise activation at precisely noon. The next useful signals are updated exchange status pages and evidence that operators on older releases have migrated. For now, the verified result is narrow: eCash's planned replay-protection upgrade is active, compatible 0.34.x nodes remain on the current network, and pre-0.34 nodes require an update to regain synchronization.
Sources
- eCash network upgrade information
- Bitcoin ABC releases and activation notice
- Bitcoin ABC 0.34.0 release notes
- MEXC support notice for the eCash network upgrade
- ChangeNow XEC network upgrade maintenance status
AI-generated editorial image; not a photograph of the reported event. Prepared with AI assistance and source verification.
