This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Massive mainnet reorganizations of the Ethereum Classic chain after Phoenix hard fork #11744
Labels
F2-bug 🐞
The client fails to follow expected behavior.
P0-dropeverything 🌋
Everyone should address the issue now.
Comments
sorpaas
changed the title
Massive mainnet reorganizations of the OpenEthereum chain
Massive mainnet reorganizations of the Ethereum Classic chain after Phoenix hard fork
Jun 1, 2020
It's not Ethereum Classic that reorganizes but the Open Ethereum client. The title might be misleading as other clients are not reorganizing. |
I checked ETC folks' discussions at their Discord, Besu is also suffering some issues after Phoenix hard fork. So looks like the only implementations not affected are Geth-family ones.
We welcome discussions here, but please stop provoking others. |
Excuse my tone. After rereading my initial bug report, it turns out I was not mentioning that bit and redacted the comment accordingly. |
Open Ethereum does not appear peering with the other clients.
|
vorot93
added
F2-bug 🐞
The client fails to follow expected behavior.
P0-dropeverything 🌋
Everyone should address the issue now.
labels
Jun 1, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
F2-bug 🐞
The client fails to follow expected behavior.
P0-dropeverything 🌋
Everyone should address the issue now.
We keep seeing long reorgs on the Ethereum Classic mainnet with the Open Ethereum client only, some are 50 - 90 blocks long. Other clients are not affected.
The text was updated successfully, but these errors were encountered: