On December 12, 2019 [1], ETC core developers and participating ecosystem stakeholders agreed upon a target block number for mainnet activation as well as a testnet review period for greater assurance. The Agharta hard-fork [2] will be inclusive of the Ethereum Constantinople features.

Kotti testnet will activate the Agharta features at block 1_705_549 or about 30 hrs from now. All other testnets have successfully activated the Agharta features and consensus bugs are a low probability at this point. Since Kotti has not officially activated Agharta at the time of this consensus meeting, core developers agreed on a 7-day testnet review period ending December 19, 2019. Assuming all testnets are running smoothly or any needed configurations are made, then Agharta will proceed to Accepted status, and Final when activated on mainnet across clients.

Latest Hard Fork Scheduled

Core developers agreed to activate Agharta on mainnet at block 9_573_000 which is expected around January 15, 2020.

Morden Testnet, Block 5_000_381 , about Nov/13th, 2019

, about Nov/13th, 2019 Mordor Testnet, Block 301_243 about Nov 20th, 2019

about Nov 20th, 2019 Kotti Testnet, Block 1_705_549 about Dec/14th, 2019

about Dec/14th, 2019 Classic Mainnet, Block 9_573_000 about Jan/15th, 2020

Conclusion & Supporting Clients

Agharta is thus far, on schedule, and anyone running an Ethereum Classic client should ensure their client is up-to-date. The official clients participating in the hard-fork are:

🛑 Official minimum viable client versions will be announced soon. Classic Geth will reach END OF LIFE on January 15th, 2020. The Agharta hard-fork will be the last hard-fork supported by Classic Geth. If you are a Classic Geth user, then migrate to Besu, Multi-Geth, or Parity now.

Listen to the full meeting 🎬

Resources:

[1] https://github.com/ethereumclassic/ECIPs/issues/175

[2] https://github.com/ethereumclassic/ECIPs/blob/master/_specs/ecip-1056.md