Currently the genesis files for CL and EL are generated using complex starlark files.
When some parameters change in the upstream (ethereum-genesis-generator) these changes have to be imported into the starlark files.
Instead of doing it this way, it would be better to feed an env file to the ethereum-genesis-generator docker file, and let it generate all the files. As it has this functionality already built into it.
Currently the genesis files for CL and EL are generated using complex starlark files.
When some parameters change in the upstream (ethereum-genesis-generator) these changes have to be imported into the starlark files.
Instead of doing it this way, it would be better to feed an env file to the ethereum-genesis-generator docker file, and let it generate all the files. As it has this functionality already built into it.
Technically we could get rid of: https://github.com/kurtosis-tech/eth-network-package/blob/main/static_files/genesis-generation-config/el/genesis-config.yaml.tmpl https://github.com/kurtosis-tech/eth-network-package/blob/main/static_files/genesis-generation-config/cl/mnemonics.yaml.tmpl https://github.com/kurtosis-tech/eth-network-package/blob/main/static_files/genesis-generation-config/cl/config.yaml.tmpl
And just replace it all with an env where we import the the fork_epochs and other parameters like slots per second.