Skip to content

Update EIP-7799: Validate systemLogsRoot in engine_newPayloadVx instead of forkchoiceUpdated #10529

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update EIP-7799: Validate systemLogsRoot in engine_newPayloadVx instead of forkchoiceUpdated #10529

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion EIPS/eip-7799.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ In the engine API, the `ExecutionPayload` for versions corresponding to forks ad

- `systemLogsRoot`: `DATA`, 32 Bytes

As part of `engine_forkchoiceUpdated`, Execution Layer implementations SHALL verify that `systemLogsRoot` for each block matches the actual value computed from local processing. This extends on top of existing `receiptsRoot` validation.
As part of `engine_newPayloadVx`, Execution Layer implementations SHALL verify that the submitted payload's `systemLogsRoot` matches the value computed from local processing; if it does not, the payload MUST be rejected (e.g., with `INVALID`). This extends on top of existing `receiptsRoot` validation performed at payload acceptance time.

### Consensus `ExecutionPayload` changes

Expand Down