Skip to content

Commit

Permalink
eip 158 handling
Browse files Browse the repository at this point in the history
  • Loading branch information
@g11tech
g11tech committed Feb 9, 2024
1 parent 74ed493 commit 8e4a928
Showing 1 changed file with 9 additions and 0 deletions.
9 changes: 9 additions & 0 deletions EIPS/eip-2935.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,15 @@ Edge cases:
* for activation at block `1`, only genesis hash will be written at slot `0` as there is no additional history that needs to be persisted.
* for activation at block `32`, block `31`'s hash will be written to slot `31` and additonal history for `0..30`'s hashes will be persisted, so all in all `0..31`'s hashes.

### EIP-158 exception

Check failure on line 69 in EIPS/eip-2935.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

the first match of the given pattern must be a link 

error[markdown-link-first]: the first match of the given pattern must be a link
  --> EIPS/eip-2935.md
   |
69 | ### EIP-158 exception
   |
   = info: the pattern in question: `(?i)(?:eip|erc)-[0-9]+`
   = help: see https://ethereum.github.io/eipw/markdown-link-first/

This address is currently exempt from [EIP-158](./eip-158.md) cleanup in Kaustinen Verkle Testnet but there are two ways this could be addressed before this EIP is adopted by ACD:

* Update the nonce to 1 in the fork block, or
* Deploy a contract à la [EIP-4788](./eip-4788.md) with `BLOCKHASH` opcode delegating call to this contract with appropriate args.

While the second option looks more elegant, but it has higher complexity as well as gas consumption considerations.

## Rationale

Very similar ideas were proposed before in [EIP-210](./eip-210.md) et al. This EIP is a simplification, removing two sources of needless complexity:
Expand Down

0 comments on commit 8e4a928

Please sign in to comment.