-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Gnosis Chain (formerly xDai) #3643
Comments
https://github.com/ledgerwatch/erigon/tree/devel/consensus/aura PoA mainnet is already supported by erigon https://github.com/ledgerwatch/erigon/blob/devel/params/config.go#L274 So, adding support for Gnosis Chain wouldn't be a hassle |
Bumping this issue as well. We just began node operations on gnosis and having to run openethereum as a backup to nethermind isn't something I want to support longer than I have to. Really looking forward to getting erigon in the mix instead! |
Is anyone able to successfully run & sync to head Erigon for Gnosis XDai? |
The ETA for Erigon supporting Gnosis Chain is 3 months after the Merge happens on Ethereum mainnet. See also https://forum.gnosis.io/t/erigon-gnosisdao-proposal/4105. |
Rationale
Currently, the Gnosis Chain (formerly xDai) is supported by two clients: OpenEthereum and Nethermind. OpenEthereum will stop working when The Merge happens, so people should get off it ASAP. On the other side, Nethermind seems to be somewhat of a memory hog and additionally, there should be client diversity, a network should not be in the hands of a single client.
In addition, in https://medium.com/openethereum/gnosis-joins-erigon-formerly-turbo-geth-to-release-next-gen-ethereum-client-c6708dd06dd was touted as the client that all OpenEthereum users should switch to, but for those running a Gnosis Chain node (no matter if a validating or non-validating one), it's not a valid alternative right now.
Implementation
I know the largest issue there is probably the AuRa consensus algorithm used on that chain right now - even more as it will be replaced by the Beacon Chain consensus (hopefully) in the near future. Still it would be great if we could run Erigon at least in a non-validating form before The Merge so client diversity on that chain could be upheld to some degree.
The text was updated successfully, but these errors were encountered: