Ethereum Classic Agharta Hard-Fork Announcement

Stevan Lohja
Jan 2 · 3 min read

Dear Ethereum Classic stakeholders,

The Ethereum Classic (ETC) network will be undergoing a planned hard-fork at block 9,573,000 mil or around January 12, 2020.

The Ethereum Classic test networks (Morden, Mordor, and Kotti) have successfully implemented the Agharta hard-fork.

As a Miner, Exchange, or User, what do I need to do?

To ensure a successful fork, we ask users to upgrade their clients to a fork-compatible version if they have not already done so. The specification proposed for the hard fork is being implemented in the following clients:

🛑 Classic Geth will reach END OF LIFE on January 12th, 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.

🛑 Parity recently announced, “We have investigated reports of some Parity Ethereum nodes not syncing and believe there may be an attack underway. New releases v2.6.8-beta & v2.5.13-stable protect against this.”

The hard-fork can be watched at the hard-fork dashboard located here.

📡 If you are an exchange, wallet provider, infrastructure provider, developer, or anyone else operating Ethereum Classic nodes, then please sign-up to be coordinated with hard-fork alerts and related events here.

What is a hard fork in Ethereum Classic?

A hard fork is a change to the underlying Ethereum Classic protocol, creating new rules to improve the system. The protocol changes are activated at a specific block number. All Ethereum Classic clients need to upgrade, otherwise, they will be stuck on an incompatible chain following the old rules.

What is Agharta?

Agharta is a planned Ethereum Classic protocol upgrade. Agharta is occurring at block number 9,573,000 mil. Agharta implements Ethereum’s Constantinople upgrades to the Ethereum Classic network and has been adopted as an accepted Ethereum Classic Improvement specification which can be found at ECIP-1056.

What changes are included in the Agharta hard fork?

Enable the following three hard fork features:

What if something goes wrong?

In the event that a critical bug is discovered, the following communication channels will be utilized:

A big thanks to the Ethereum Classic development community across all clients and platforms who came together to provide input, thoughts, and contributions for this upgrade.

DISCLAIMER This is an emergent and evolving highly technical space. If you choose to implement the recommendations in this post and continue to participate, you should make sure you understand how it impacts you. You should understand that there are risks involved including but not limited to risks like unexpected bugs. By choosing to implement these recommendations, you alone assume the risks of the consequences. This post and recommendations are not a sale of any kind and do not create any warranties of any kind including but not limited to any relating to the Ethereum Classic network or the Ethereum Classic clients referred to herein.

Stevan Lohja

Written by

Technology Coordinator at ETC Core. Previously Tech Writer at ETCDEV.

etc-core

etc-core

A leading Ethereum Classic core development team.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade