-
Notifications
You must be signed in to change notification settings - Fork 835
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
Allowing Besu to parse a Geth-style genesis like other clients #7273
Comments
@non-fungible-nelson are there testing vectors for this? What doesn't work right now? |
https://discord.com/channels/595666850260713488/1252403393461489704/1252606839787622492 not much context to go on -- we should ask @shemnon or barnabas when is back from OOO |
https://github.com/ethpandaops/pectra-devnets/tree/master/network-configs/devnet-2/metadata/genesis.json the above shows that two separate genesis files are needed for devnet-2, in this case. one for Besu, the other for the remaining clients. |
Reference: Ephemery https://github.com/ephemery-testnet/ephemery-resources |
@non-fungible-nelson in case the extra parsing, needed to detect in which format the genesis file is, will impact in a significant way the work done to parse large genesis file, could be an option to introduce a new dedicated option (for example |
Description
As a node operator, I would like Besu to be able to parse configs in the same way as other clients, so interoperability testing and multi-client network operation is simpler.
The text was updated successfully, but these errors were encountered: