⚠️ Urgent Action Required: Hot-fix — Post Phoenix Hard-Fork Update ⚠️
Dear Ethereum Classic consumers, the OpenEthereum team recently released v3.0.1.
This release contains a hotfix for #11744 that caused a massive network partition due to faulty FORK_ID generation.
If you are using OpenEthereum for your service or any Parity Ethereum client-based software, then you should migrate your infrastructure to Core-geth as soon as possible. Many consumers are dependent on the Parity Ethereum client family (OpenEthereum), but OpenEthereum v3.0.0 is having degraded syncing performance and when it is synced, it intermediately falls behind, then recovers. While this bug is not splitting the network, it causes large chain reorganizations putting your services and customers at risk. Therefore, you should confidently run Core-geth v1.11.0 or later or cautiously run OpenEthereum v3.0.1 with plans to migrate to Core-geth as soon as possible.
- Core-geth releases: https://github.com/etclabscore/core-geth/releases*
- Open-Ethereum releases: https://github.com/openethereum/openethereum/releases
- Migrating from Parity to Core-geth: https://medium.com/etc-core/migrating-from-parity-to-core-geth-d39606ad00c2
More Phoenix/ network stats:
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.
