mirror of
https://github.com/ethereum/go-ethereum.git
synced 2026-06-12 01:41:36 +00:00
Mark `amsterdam` as `optional` in the blob-schedule fork-validation table
so that a chain config setting `amsterdamTime` no longer requires a
corresponding `blobSchedule.amsterdam` entry to be present.
Why: hive's `clients/<el>/mapper.jq` removed the `amsterdam` block from
the generated `blobSchedule` in ethereum/hive#1387 ("named forks should
not have hard-coded blob defaults"). With strict validation in place,
every hive simulator that activates Amsterdam — including
`eels/consume-engine` against bal-devnet-4 — now fails immediately at
`geth init` with:
Fatal: Failed to write genesis block: invalid chain configuration:
missing entry for fork "amsterdam" in blobSchedule
The bal-devnet-3 branch carried a similar relaxation (commit
|
||
|---|---|---|
| .. | ||
| forks | ||
| bootnodes.go | ||
| config.go | ||
| config_test.go | ||
| dao.go | ||
| denomination.go | ||
| network_params.go | ||
| protocol_params.go | ||
| verkle_params.go | ||