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.

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 and running:

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¶

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¶

uv run execute eth-config --network Mainnet --rpc-endpoint http://localhost:8545

Testing a Sepolia Client¶

uv run execute eth-config --network Sepolia --rpc-endpoint http://localhost:8545

Using a Custom Network Configuration¶

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:

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¶

Configuration Loading: The command loads the network configuration from the YAML file.
RPC Connection: Connects to the specified client RPC endpoint.
eth_config Call: Calls the eth_config RPC method to get the client's current configuration.
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 for the expected response description.