Skip to content

Update testing_buildBlockV1 fixtures#783

Open
newmanifold wants to merge 2 commits intoethereum:mainfrom
newmanifold:fix/testing-buildblock-fixtures
Open

Update testing_buildBlockV1 fixtures#783
newmanifold wants to merge 2 commits intoethereum:mainfrom
newmanifold:fix/testing-buildblock-fixtures

Conversation

@newmanifold
Copy link
Copy Markdown

@newmanifold newmanifold commented Apr 11, 2026

Fixes three issues with the testing_buildBlockV1 test fixtures:

  1. Remove slotNumber: null from responses. The spec defines the response as ExecutionPayloadV3 which does not include slotNumber (that's V4/Amsterdam). The test chain is Prague-only.

  2. Update blockValue to reflect actual priority fees instead of hardcoded 0x0.

  3. Mark build-block-from-mempool as SpecOnly since mempool tx selection varies across clients (ordering, min tip thresholds).

Fixtures regenerated with rpctestgen against ethereum/go-ethereum#34704 (merged). go.mod pin updated.

…only

- Regenerate fixtures against geth with slotNumber omitempty and real blockValue
- Mark build-block-from-mempool as SpecOnly since mempool tx selection is not deterministic
@newmanifold newmanifold force-pushed the fix/testing-buildblock-fixtures branch from 0030bd8 to 5dd2c39 Compare April 11, 2026 16:28
@newmanifold newmanifold changed the title testing: fix testing_buildBlockV1 fixtures Update testing_buildBlockV1 fixtures Apr 11, 2026
MariusVanDerWijden pushed a commit to ethereum/go-ethereum that referenced this pull request Apr 13, 2026
Two fixes for `testing_buildBlockV1`:

1. Add `omitempty` to `SlotNumber` in `ExecutableData` so it is omitted
for pre-Amsterdam payloads. The spec defines the response as
`ExecutionPayloadV3` which does not include `slotNumber`.

2. Pass `res.fees` instead of `new(big.Int)` in `BuildTestingPayload` so
`blockValue` reflects actual priority fees instead of always being zero.

Corresponding fixture update: ethereum/execution-apis#783
@newmanifold newmanifold marked this pull request as ready for review April 13, 2026 11:58
@MysticRyuujin
Copy link
Copy Markdown
Contributor

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants