Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

Repository files navigation

evm-consensus-fixtures

Curated, pinned consensus-test corpus for evm-next-contract's consensus suite (tests/consensus_tests.cpp). It holds exactly the fixtures that suite runs — nothing more — so a clone is ~585 MB instead of the ~2.5 GB a full ethereum/tests checkout costs.

Both subtrees are in the blockchain-test format the harness reads (network / pre / blocks / postState).

Layout

BlockchainTests/GeneralStateTests/   legacy ethereum/tests, GeneralStateTests-as-blockchain-tests
eest/
  prague/                            EEST Prague blockchain_tests
  osaka/                             EEST Osaka  blockchain_tests

Provenance (pinned — update deliberately)

Subtree Source Pin
BlockchainTests/GeneralStateTests ethereum/tests — BlockchainTests/GeneralStateTests only commit 27d9547470b935c40e85a6a60e1d7b92ac846ad8 (frozen, ≤ Cancun)
eest/prague ethereum/execution-spec-tests — fixtures_stable.tar.gz, blockchain_tests/prague release v5.4.0
eest/osaka ethereum/execution-spec-tests — fixtures_develop.tar.gz, blockchain_tests/osaka (the full Osaka set incl. EIP-7594/7823/7918/7934/7939/7951, which fixtures_stable v5.4.0 lacks) release v5.4.0

ethereum/tests is effectively frozen (new development moved to EEST), so the legacy subtree is a permanent snapshot. EEST ships fixtures as release tarballs (not a git tree), so it must be snapshotted here rather than submoduled. To refresh EEST: download a newer tarball, copy its blockchain_tests/<fork> over eest/<fork>/, bump the pin in this table, tag, and bump the submodule pointer in evm-next-contract.

Note on the stable vs develop split: osaka is sourced from fixtures_develop because fixtures_stable v5.4.0 ships only 2 of the 8 Osaka EIP dirs (eip7825, eip7883). The develop set is the full Osaka corpus and includes fixtures we currently skip or that exercise unimplemented features (notably EIP-7951 P256VERIFY, which is stubbed — see skip_list.txt / the consensus harness). It is intentionally complete so coverage can be driven test-by-test (fix vs. skip). When a future fixtures_stable includes the full Osaka set, osaka can move back to stable.

How the harness consumes it

evm-next-contract references this repo as a git submodule. CMake points:

  • ETH_TEST_FOLDER → this repo root (auto-detects BlockchainTests/GeneralStateTests)
  • EEST_FIXTURES_FOLDER → eest/

Run the full suite (legacy ≤Cancun + EEST Prague/Osaka):

cd evm-next-contract/tests/build
./unit_test --run_test=consensus_tests

Or point at this dir explicitly without the bundled-legacy auto-detect:

EVM_TEST_ROOT=/abs/path/to/evm-consensus-fixtures EVM_TEST_NO_LEGACY=1 \
  ./unit_test --run_test=consensus_tests

Pre-Merge forks (Frontier..London) and *To*AtTime* transition forks are handled by the harness (to_rev / to_transition); intentional platform skips (mod_exp host limit, blob txs, EIP-7685 requests-hash validation, etc.) are reported in the end-of-run "skipped tests by category" summary.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors