schedule dencun on goerli

[g11tech]

see:

• Update EIP-7569: Add Testnet times ethereum/EIPs#8051

[etan-status]

Proposing to make this repo the canonical one (over eth2-networks repo). Here a PR that makes this loadable from Nimbus (we need the block hash file):

• Sync changes from eth-networks #179
• remove prater config as it has been copied to separate repo eth2-networks#92

[rolfyone]

I could be wrong, but when i loaded it to teku we were missing all the deneb config:

# Deneb
# `2**7` (=128)
MAX_REQUEST_BLOCKS_DENEB: 128
# MAX_REQUEST_BLOCKS_DENEB * MAX_BLOBS_PER_BLOCK
MAX_REQUEST_BLOB_SIDECARS: 768
# `2**12` (= 4096 epochs, ~18 days)
MIN_EPOCHS_FOR_BLOB_SIDECARS_REQUESTS: 4096
# `6`
BLOB_SIDECAR_SUBNET_COUNT: 6
# `uint64(6)`
MAX_BLOBS_PER_BLOCK: 6

and the validator cycle change:

# [New in Deneb:EIP7514] 2**3 (= 8)
MAX_PER_EPOCH_ACTIVATION_CHURN_LIMIT: 8

Is everyone else getting these fields from elsewhere?

[etan-status]

The fields are initialized from the mainnet preset (the config refers to the preset to load defaults from at the start)

[g11tech]

@rolfyone yea we generally keep adding fields to our mainnet config in codebase and any provided config overrides the mainnet fields (or the minimal one depends on the loaded preset), @etan-status these fields (https://github.com/ethereum/consensus-specs/blob/dev/configs/mainnet.yaml#L144) are separate from the preset (https://github.com/ethereum/consensus-specs/blob/dev/presets/mainnet/deneb.yaml) so i guess they should be added here

@parithosh what is the strategy for generating and keep the configs for testnets? all fields are generated and maintained or only those which are overriden?

[parithosh]

Newer testnets are all generated from here: https://github.com/ethpandaops/ethereum-genesis-generator/blob/master/config-example/cl/config.yaml

The older ones like goerli are just manually updated, so we try to keep it up to date with: https://github.com/ethereum/consensus-specs/blob/dev/configs/mainnet.yaml . Its extremely likely that the last time we updated it was during the withdrawals fork. Definitely worth updating the PR to include all the fields in the config explicitly.

[rolfyone]

LGTM!