Closed barnabasbusa closed 10 months ago
i think you mean fetch configs from eth-clients
and not from the ethpandaops
org :D
eth-clients have no devnet config
eth-clients
is the canonical source for every public testnet config :D
e,g: holesky should be fetched from here: https://github.com/eth-clients/holesky
testnet config doesn't need to be fetched at all, as it's part of each client. (as I described above )
It would be great if we could try to sync up public testnets/devnets using a single one liner configuration.
In this case, we won't need to run genesis, but rather pull the genesis related metrics into an artifact (if its a devnet).
Ideally I should be able to sync "holesky" with:
In case of a public testnet, no need to pull any data, as its built into the clients. Planning to rework it such
if network_params.network != kurtosis && network == public testnet name
if network_params.network != kurtosis && network != public testnet name
pull network config from
github.com/ethpandaops/<network_params.network | get the first word + append devnets>/network-configs/<network_params.network>/
zip that up into an artifact and use those values.Probably want to split these two up into their own PRs, and test them well.
Public testnet syncing might require persistence. https://github.com/kurtosis-tech/ethereum-package/issues/371