A proposed registry would help native rollups follow Ethereum upgrades

EIP-8357 proposes a system contract that would expose hashes of Ethereum-approved EVM verification keys and the input schema associated with each one. A native rollup could follow the current key or select a historical entry while it adapts to a fork.

The registry is a companion to proposed proof verification, not the verifier itself. The EIP is a draft; inclusion in the proposal repository does not mean the change is approved or active on mainnet. Its specification says activation requires a hard fork.

For builders, automatic alignment with L1 upgrades could reduce separate governance work, but it introduces a timing choice. The authors warn that following a new key before a rollup can produce compatible proofs could interrupt it, while historical keys may later prove insecure.