Deprecate this repo, move to per-network repos about eth2-networks HOT 10 CLOSED

I agree, it makes sense to have long-standing, public networks in their own, contained repositories. sepolia is currently maintained in two places: eth-clients/merge-testnets#22

for mainnet, we should consider hosting it along the spec though, or maybe under the ethereum github org.

from eth2-networks.

for mainnet, we should consider hosting it along the spec though, or maybe under the ethereum github org.

I'm about to suggest the opposite direction in the spec repo: remove the instance-specific variables in the spec examples (ie fork epochs) and replace them with dummy values (ie FAR_FUTURE_EPOCH) - the spec is generic, so I feel it's a bit odd to special-case the mainnet "instance" - also, there is ephemeral information in the configuration such as boot nodes as well as large cached binary blobs (genesis) which I think generally don't belong in a spec repo that describes a protocol.

I believe the mainnet repo is / should be a shared responsibility between the the EF and client teams (which is why eth-clients was set up) - the spec is already under EF control meaning there is no ambiguity in terms of what we're all implementing whereas a chain definition contains the information we want clients to agree on before launching into a hard fork and that largely are maintained by client teams (ie fork epochs, boot nodes etc) - I see it as a net positive that this repo is owned by a wider range of actors.

from eth2-networks.