Skip to content

feat(test-benchmark): add stub account configuration, with state-actor example config#3203

Open
LouisTsai-Csie wants to merge 1 commit into
ethereum:forks/amsterdamfrom
LouisTsai-Csie:doc-stub-account
Open

feat(test-benchmark): add stub account configuration, with state-actor example config#3203
LouisTsai-Csie wants to merge 1 commit into
ethereum:forks/amsterdamfrom
LouisTsai-Csie:doc-stub-account

Conversation

@LouisTsai-Csie

Copy link
Copy Markdown
Contributor

Description

Stateful benchmarks require pre-deployed contracts and accounts on the network. This PR documents the stub accounts needed for each benchmark (addresses, initcodes, storage patterns, etc.) and provides a complete state-actor configuration example.

Related Issues or PRs

N/A.

Checklist

  • Ran fast static checks to avoid CI fails, see Code Standards & Verifying Changes: just static
  • PR title has the form <type>(<area>): <title>, where <type> and <area> come from an appropriate C-<type>, respectively A-<area>, label. The title should match the target squash commit message.

Cute Animal Picture

Put a link to a cute animal picture inside the parenthesis-->

@LouisTsai-Csie LouisTsai-Csie added A-test-benchmark Area: execution_testing.benchmark and tests/benchmark C-feat Category: an improvement or new feature labels Jul 22, 2026
@LouisTsai-Csie LouisTsai-Csie changed the title doc(test-benchmark): add stub account configuration, with state-actor example config feat(test-benchmark): add stub account configuration, with state-actor example config Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-test-benchmark Area: execution_testing.benchmark and tests/benchmark C-feat Category: an improvement or new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant