Discussion topic for EIP-8357.
Abstract
This EIP creates a fixed-address system contract containing the canonical EVM verification key for each registered L1 feature fork. Each entry maps one exact verification key to the activation timestamp of the fork-specific EVM program bound by that key.
The contract stores one current_verification_key. A caller may retrieve either the current entry or an exact historical entry. This lets a native rollup follow L1 EVM upgrades automatically or deliberately remain on a historical EVM fork.
1 post - 1 participant
Read full topic
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | EIP-8337: Validated EVM Code | 0 | 6.96 | 14-07-2026 |
| 2 | EIP-8361: Transaction Validity Proofs | 0 | 19.28 | 04-08-2026 |
| 3 | EIP-8374: Persist Warm Access Sets Across Reverts | 0 | 9.96 | 07-08-2026 |
| 4 | EIP-8347: Offline state migration to the PBT | 0 | 9.58 | 24-07-2026 |
| 5 | Deterministic Random Number in EVM for Independent Recomputability | 0 | 12.36 | 30-07-2026 |
| 6 | EIP-8375: eMBER, ePBS Mandatory Burn of Execution Rewards | 0 | 18.86 | 10-08-2026 |
| 7 | EIP-8367: Balance sunset for retired BLS validators | 0 | 13.19 | 05-08-2026 |
| 8 | EIP-8341: Partial Execution Payload Commitments | 0 | 18.4 | 17-07-2026 |
| 9 | EIP-8384: Deterministic sync committee aggregators | 0 | 21.11 | 20-08-2026 |
| 10 | [Idea / Meta EIP] Protocol Maturity and Ossification Framework | 0 | 6.5 | 10-08-2026 |