Files
terence 651b9bc290 Implement spec V1.7.0 alpha.7 and pass spec tests (#16750)
- Bump consensus spec to `v1.7.0-alpha.7` and refresh spec tests
- Add EIP-8061
- Add `parent_beacon_block_root` on `ExecutionPayloadEnvelope`
- Add `dependent_root` to `ProposerPreferences` protobuf only
- Increase minimal preset `PTC_SIZE` from 2 to 16

---------

Co-authored-by: satushh <satushh@gmail.com>
2026-05-08 05:07:30 +00:00
..
2025-11-12 19:53:39 +00:00

Spec Tests

Spec testing vectors: https://github.com/ethereum/consensus-spec-tests

To run all spectests:

bazel test //... --test_tag_filters=spectest

Adding new tests

New tests must adhere to the following filename convention:

{mainnet/minimal/general}/$fork__$package__$test_test.go

An example test is the phase0 epoch processing test for effective balance updates. This test has a spectest path of {mainnet, minimal}/phase0/epoch_processing/effective_balance_updates/pyspec_tests. There are tests for mainnet and minimal config, so for each config we will add a file by the name of phase0__epoch_processing__effective_balance_updates_test.go since the fork is phase0, the package is epoch_processing, and the test is effective_balance_updates.

Running nightly spectests

Since PR 15312, Prysm has support to download "nightly" spectests from github via a starlark rule configuration by environment variable. Set --repo_env=CONSENSUS_SPEC_TESTS_VERSION=nightly or --repo_env=CONSENSUS_SPEC_TESTS_VERSION=nightly-<run_id> when running spectest to download the "nightly" spectests. Note: A GITHUB_TOKEN environment variable is required to be set. The github token does not need to be associated with your main account; it can be from a "burner account". And the token does not need to be a fine-grained token; it can be a classic token.

bazel test //... --test_tag_filters=spectest --repo_env=CONSENSUS_SPEC_TESTS_VERSION=nightly
bazel test //... --test_tag_filters=spectest --repo_env=CONSENSUS_SPEC_TESTS_VERSION=nightly-21422848633