Add EIP: Read BLOCKHASH from storage and update cost

[gabrocheleau]

This EIP extracts the following verkle-specific behavior into a separate EIP to be included in a subsequent hard-fork (the verkle hard fork).

Changes

• Updates the behavior of the BLOCKHASH opcode, which should now be served from the system contract storage
• Updates the gas cost of the BLOCKHASH opcode to reflect the cost of an SLOAD operation
• Specifies that BLOCKHASH storage accesses should be contained in the verkle execution witness

Links

• Ethereum Magicians thread

[eth-bot]

✅ All reviewers have approved.

[github-actions]

The commit 38d94e2 (as a parent of e373909) contains errors.
Please inspect the Run Summary for details.

[HoangTranMap]

hi okayĐược gửi từ iPhone của tôiVào ngày 29 thg 5, 2024, lúc 03:20, g11tech ***@***.***> đã viết: @g11tech commented on this pull request. In EIPS/eip-7709.md:

+* at genesis for testnets/devnets where this EIP could also be activated at genesis

+ +The current proposal is to activate this EIP with Verkle to allow for stateless execution of the block. + +### Gas costs + +As described above, if the `arg` to be resolved is within the correct window, the corresponding `SLOAD` charges and accesses are to be applied for the slot `arg % HISTORY_SERVE_WINDOW`. Note that the `HISTORY_SERVE_WINDOW` and `BLOCKHASH_SERVE_WINDOW` are different. + +### System contract + +Even if the clients choose to resolve `BLOCKHASH` through system call to [EIP-2935](./eip-2935.md) contract, the gas cost for the system code execution (and also the code witnesses if Verkle activated) is not applied. Only the effect of `SLOAD` is applied as described above. + +## Rationale + +* The reason behind the updated gas cost is to match the real operation, which is equivalent to an `SLOAD`. +* The [EIP-2935](./eip-2935.md) system contract execution charges (and accesses) are not applied to keep the gas low and to keep things simple for clients which choose to resolve `BLOCKHASH` in other ways (directly or though memory/maintained history) i think this addresses it: ..re not applied to keep the gas low and to keep things simple for clients which choose to resolve BLOCKHASH in other ways (directly or though memory/maintained history) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[eth-bot]

All Reviewers Have Approved; Performing Automatic Merge...