feat(clis,pytest-plugins): allow pytest commands from package, addexecute eth-config command (#1863)

* feat(execute): `execute eth-config` command

* feat(forks): Add required forkid forks

* feat(rpc): Add forkid to eth_config

* feat(plugins/eth_config): Fixes and add fork id

* refactor(rpc): Move unit tests file

* refactor(execute): Use pytest_configure

* fix(execute,rpc): Update to latest spec version

* fix(execute,rpc): Update again to latest spec version

* pyproject: Add execute eth-config networks file

* refactor(pytest_commands): Work without having to clone repository

* fix: tests, tox

* refactor: Rename pytest command files

* refactor: Move pytest-fill.ini, refactor PytestCommand

* refactor: Move and package eels_resolutions.json file

* fix: All unit tests

* fix: review comments

* feat(execute): add more granular eth_config testing

* feat(rpc): Add chainId

* fix: Help of all execute commands

* docs: Add eth-config command

* fix(tox.ini): Update commands (sneakily lower benchmark block-gas-limit)

* fix: tox

* docs: Changelog

* docs(execute): minor improvements to docs

---------

Co-authored-by: danceratopz <[email protected]>

Author: marioevz

docs/CHANGELOG.md

@@ -64,6 +64,7 @@ Users can select any of the artifacts depending on their testing needs for their
 
 - ✨ Added new `Blob` class which can use the ckzg library to generate valid blobs at runtime ([#1614](https://github.com/ethereum/execution-spec-tests/pull/1614)).
 - ✨ Added `blob_transaction_test` execute test spec, which allows tests that send blob transactions to a running client and verifying its `engine_getBlobsVX` endpoint behavior ([#1644](https://github.com/ethereum/execution-spec-tests/pull/1644)).
+- ✨ Added `execute eth-config` command to test the `eth_config` RPC endpoint of a client, and includes configurations by default for Mainnet, Sepolia, Holesky, and Hoodi ([#1863](https://github.com/ethereum/execution-spec-tests/pull/1863)).
 
 ### 📋 Misc
 
@@ -91,6 +92,7 @@ Users can select any of the artifacts depending on their testing needs for their
 - 🔀 Add fixture comparison check to optimize coverage workflow in CI ([#1833](https://github.com/ethereum/execution-spec-tests/pull/1833)).
 - 🔀 Move `TransactionType` enum from test file to proper module location in `ethereum_test_types.transaction_types` for better code organization and reusability ([#1763](https://github.com/ethereum/execution-spec-tests/pull/1673)).
 - ✨ Opcode classes now validate keyword arguments and raise `ValueError` with clear error messages ([#1739](https://github.com/ethereum/execution-spec-tests/pull/1739), [#1856](https://github.com/ethereum/execution-spec-tests/pull/1856)).
+- ✨ All commands (`fill`, `consume`, `execute`) now work without having to clone the repository, e.g. `uv run --with git+https://github.com/ethereum/execution-spec-tests.git consume` now works from any folder ([#1863](https://github.com/ethereum/execution-spec-tests/pull/1863)).
 
 ### 🧪 Test Cases
 

docs/filling_tests/debugging_t8n_tools.md

@@ -178,4 +178,4 @@ where the `verify_fixtures.sh` script can be used to reproduce the `evm blocktes
     This means, by default, that the feedback is not as granular as for test case execution. To improve granularity, and get feedback per parametrized test case use `--single-fixture-per-file`.
 
 [^1]: <!-- markdownlint-disable MD053 (53=link-image-reference-definitions) -->
-    This limitation is required to enable support of the [`pytest-xdist` plugin](https://github.com/pytest-dev/pytest-xdist) for concurrent test execution across multiple CPUs. To achieve this we use the we apply the `--dist loadscope` xdist flag in our `pytest.ini`.
+    This limitation is required to enable support of the [`pytest-xdist` plugin](https://github.com/pytest-dev/pytest-xdist) for concurrent test execution across multiple CPUs. To achieve this we use the we apply the `--dist loadscope` xdist flag in our `pytest-fill.ini`.

docs/navigation.md

@@ -61,6 +61,7 @@
       * [Execute Commands](./running_tests/execute/index.md)
           * [Execute Hive](./running_tests/execute/hive.md)
           * [Execute Remote](./running_tests/execute/remote.md)
+          * [Execute Eth Config](./running_tests/execute/eth_config.md)
       * [Useful Pytest Options](running_tests/useful_pytest_options.md)
   * [Developer Doc](dev/index.md)
       * [Managing Configurations](dev/configurations.md)

docs/running_tests/execute/eth_config.md

@@ -0,0 +1,109 @@
+# Execute eth-config Command
+
+The `execute eth-config` command is a specialized testing tool that validates an Ethereum client's configuration against expected network parameters using the `eth_config` RPC endpoint as specified by [EIP-7910](https://eips.ethereum.org/EIPS/eip-7910).
+
+The goal is to test baked-in configurations primarily but it can be used to test that genesis and config files were successfully parsed, in devnets for example.
+
+## Overview
+
+This command verifies that a client is correctly configured for a specific network by checking:
+
+- Current fork configuration.
+- Fork activation times.
+- Chain ID.
+- Precompile addresses.
+- System contract addresses.
+- Fork hashes and IDs.
+
+## Usage
+
+### Standalone, Direct Usage
+
+The `eth-config` sub-command can be ran directly, without cloning @ethereum/execution-spec-tests, by [installing uv](https://docs.astral.sh/uv/getting-started/installation/) and running:
+
+```bash
+uv run --with git+https://github.com/ethereum/execution-spec-tests.git execute eth-config --network Mainnet --rpc-endpoint http://<ETH_RPC_ENDPOINT>
+```
+
+### From within the EEST Repository
+
+```bash
+uv run execute eth-config --network <NETWORK_NAME> --rpc-endpoint <RPC_URL> [OPTIONS]
+```
+
+### Required Arguments
+
+- `--network`: Name of the network to verify (e.g., `Mainnet`, `Sepolia`, `Holesky`, `Hoodi`)
+- `--rpc-endpoint`: RPC endpoint URL of the execution client to test
+
+### Optional Arguments
+
+- `--network-config-file`: Path to a custom YAML file containing network configurations (defaults to `src/pytest_plugins/execute/eth_config/networks.yml`)
+
+## Examples
+
+### Testing a Mainnet Client
+
+```bash
+uv run execute eth-config --network Mainnet --rpc-endpoint http://localhost:8545
+```
+
+### Testing a Sepolia Client
+
+```bash
+uv run execute eth-config --network Sepolia --rpc-endpoint http://localhost:8545
+```
+
+### Using a Custom Network Configuration
+
+```bash
+uv run execute eth-config --network MyCustomNet --rpc-endpoint http://localhost:8545 --network-config-file ./my-networks.yml
+```
+
+## Network Configuration File Format
+
+The network configuration file is a YAML file that defines the parameters for each network. Here's the structure:
+
+```yaml
+MyCustomNet:
+  chainId: 0xabcd                 # Chain ID in hex
+  genesisHash: 0xd4e5674...       # Genesis block hash
+  forkActivationTimes:            # Fork activation block numbers/times
+    0: Cancun                     # Genesis fork, it must be the latest fork activated in the genesis
+    1742999832: Prague
+    1742999833: Osaka
+  bpoForkActivationTimes:         # Optional: Blob parameter only fork definitions
+    1742999834:
+        target: 9
+        max: 12
+        base_fee_update_fraction: 5007716
+    1742999835:
+        target: 12
+        max: 15
+        base_fee_update_fraction: 5007716
+  addressOverrides:               # Optional: Override addresses for precompiles/contracts
+    0x00000000219ab540...: 0x7f02c3e3c98b133...
+```
+
+### Supported Networks
+
+The default configuration file includes:
+
+- **Mainnet**: Ethereum mainnet.
+- **Sepolia**: Public testnet.
+- **Hoodi**: Public testnet.
+- **Holesky**: Public testnet.
+
+## How It Works
+
+1. **Configuration Loading**: The command loads the network configuration from the YAML file.
+2. **RPC Connection**: Connects to the specified client RPC endpoint.
+3. **eth_config Call**: Calls the `eth_config` RPC method to get the client's current configuration.
+4. **Validation**: Compares the client's response against the expected configuration based on:
+   - Current system timestamp.
+   - Fork activation schedule.
+   - Address overrides (if any).
+
+## `eth_config` Expected Response Details
+
+See [EIP-7910](https://eips.ethereum.org/EIPS/eip-7910) for the expected response description.

docs/running_tests/execute/index.md

@@ -6,6 +6,7 @@ See:
 
 - [Execute Hive](./hive.md) for help with the `execute` simulator in order to run tests on a single-client local network.
 - [Execute Remote](./remote.md) for help with executing tests on a remote network such as a devnet, or even mainnet.
+- [Execute Eth Config](./eth_config.md) for help verifying client configurations on a remote network such as a devnet, or even mainnet.
 
 The rest of this page describes how `execute` works and explains its architecture.
 

docs/scripts/generate_fill_help.py

@@ -12,7 +12,6 @@
 import subprocess
 import sys
 import textwrap
-from pathlib import Path
 
 import mkdocs_gen_files
 
@@ -21,17 +20,12 @@
 
 def get_fill_help_output() -> str:
     """Run 'fill --help' and capture its output."""
-    # Get the repository root (assuming script is in docs/scripts/)
-    script_dir = Path(__file__).parent
-    repo_root = script_dir.parent.parent
-
     try:
         result = subprocess.run(
             ["uv", "run", "fill", "--help"],
             capture_output=True,
             text=True,
             check=True,
-            cwd=repo_root,  # Run from repo root where pytest.ini exists
         )
         return result.stdout
     except subprocess.CalledProcessError as e:

pyproject.toml

@@ -116,7 +116,12 @@ exclude = ["tests/static/**"]
 
 [tool.setuptools.package-data]
 ethereum_test_forks = ["forks/contracts/*.bin"]
+"pytest_plugins.execute" = ["eth_config/networks.yml"]
+"pytest_plugins" = [
+    "eels_resolutions.json"
+]
 "cli.eest.make" = ["templates/*.j2"]
+"cli.pytest_commands" = ["pytest_ini_files/*.ini"]
 
 [tool.ruff]
 line-length = 99

pytest-framework.ini

@@ -10,8 +10,4 @@ addopts =
     -p pytest_plugins.eels_resolver
     --ignore=src/pytest_plugins/consume/test_cache.py
     --ignore=src/pytest_plugins/consume/direct/
-    --ignore=src/pytest_plugins/consume/direct/test_via_direct.py
     --ignore=src/pytest_plugins/consume/simulators/
-    --ignore=src/pytest_plugins/consume/simulators/engine/test_via_engine.py
-    --ignore=src/pytest_plugins/consume/simulators/rlp/test_via_rlp.py
-    --ignore=src/pytest_plugins/execute/test_recover.py

src/cli/gentest/tests/test_cli.py

@@ -116,9 +116,11 @@ def get_mock_context(self: StateTestProvider) -> dict:
     ## Fill ##
     with open(generated_py_file, "r") as f:
         pytester.makepyfile(f.read())
-    pytester.copy_example(name="pytest.ini")
+    pytester.copy_example(name="src/cli/pytest_commands/pytest_ini_files/pytest-fill.ini")
 
     args = [
+        "-c",
+        "pytest-fill.ini",
         "-m",
         "state_test",
         "--fork",