You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…sit request error (#2832)
**Motivation**
Currently, when we fail to parse a deposit request we simply ignore it
and keep the rest of the deposits, relying on the request hash check
afterwards to notice the missing deposit request. This PR handles the
error earlier and returns the appropriate `InvalidDepositRequest Error`.
This will provide better debugging information and also more accurate
testing via tools such as `execution-spec-tests` which rely on specific
error returns.
We also were not correctly validating the layout according to the
[EIP](https://eips.ethereum.org/EIPS/eip-6110), as we were only checking
the total size and not the size and offset of each request field
<!-- Why does this pull request exist? What are its goals? -->
**Description**
* Check that the full layout of deposit requests is valid (aka the
internal sizes and offsets of the encoded data)
* Handle errors when parsing deposit requests
* Check log topic matches deposit topic before parsing a request as a
deposit request
<!-- A clear and concise general description of the changes this PR
introduces -->
<!-- Link to issues: Resolves#111, Resolves#222 -->
Allows us to address review comment made on execution-specs-test PR
ethereum/execution-spec-tests#1607 + also closes#2132
Uh oh!
There was an error while loading. Please reload this page.
There was an issue when the clients hardforked to Pectra in Sepolia related to the contract address and the logs that are emmited.
This is the change to the EIP: ethereum/EIPs#9453
This is the fix on Geth: ethereum/go-ethereum#31317
This test should pass: ethereum/execution-spec-tests@9084db0#diff-423832c4eebde83349472ade321b211f34bd8659b6a677207da2ae0b78b462e9R22
This is a blog post explaining the issue: https://mariusvanderwijden.github.io/blog/2025/03/08/Sepolia/
The text was updated successfully, but these errors were encountered: