Skip to content

fix: testing_buildBlockV1, deterministic access list, console test#71

Closed
MysticRyuujin wants to merge 12 commits intoMariusVanDerWijden:testing-buildblockfrom
MysticRyuujin:fix-testing-buildblock-v1
Closed

fix: testing_buildBlockV1, deterministic access list, console test#71
MysticRyuujin wants to merge 12 commits intoMariusVanDerWijden:testing-buildblockfrom
MysticRyuujin:fix-testing-buildblock-v1

Conversation

@MysticRyuujin
Copy link
Copy Markdown

  • miner: OnlyProvidedTxs/UseExplicitExtra for testing_buildBlockV1; sync payload when only provided txs
  • eth/catalyst: BuildPayload with OnlyProvidedTxs and UseExplicitExtra for testing API
  • eth/tracers/logger: sort access list addresses and storage keys for deterministic eth_createAccessList
  • internal/ethapi/override: sort addresses for deterministic state override error messages
  • cmd/geth: expect testing:1.0 in console IPC APIs

MariusVanDerWijden and others added 10 commits January 21, 2026 13:13
- miner: OnlyProvidedTxs/UseExplicitExtra for testing_buildBlockV1; sync payload when only provided txs
- eth/catalyst: BuildPayload with OnlyProvidedTxs and UseExplicitExtra for testing API
- eth/tracers/logger: sort access list addresses and storage keys for deterministic eth_createAccessList
- internal/ethapi/override: sort addresses for deterministic state override error messages
- cmd/geth: expect testing:1.0 in console IPC APIs
@MysticRyuujin
Copy link
Copy Markdown
Author

Comment thread eth/tracers/logger/access_list_tracer.go Outdated
Comment thread eth/tracers/logger/access_list_tracer.go Outdated
Comment thread eth/tracers/logger/access_list_tracer.go
Comment thread internal/ethapi/override/override.go Outdated
@MysticRyuujin MysticRyuujin requested a review from jshufro February 5, 2026 15:36
Comment thread miner/payload_building.go
@MariusVanDerWijden
Copy link
Copy Markdown
Owner

I don't like that idea of accepting both transactions via the endpoint and the txpool. We should only do one. Same with the extradata. We should only ever use the extradata provided by the endpoint. Let me try to implement that so we can use []byte{} as extradata as well

@MysticRyuujin
Copy link
Copy Markdown
Author

I don't entirely understand the feedback, this is how the spec is written, if TXs are passed those TXs (and only those TXs) must be included in the block, if an empty array is passed then no TXs can be included in the block, it must be an empty block.

For the API endpoint there is no "accepting both transactions via the endpoint and the txpool" or did I mess something up?

As for extraData the spec says if extraData is passed it must be used as is, but it does not say what to do if extraData is NOT passed, to which I assume it would either be "0x" or the client's default.

@MariusVanDerWijden
Copy link
Copy Markdown
Owner

The AI made some mistakes then.
I pushed a fix on top of my PR which should ™️ solve these issues

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.

3 participants