Chainbench includes generic EVM profiles that work with any EVM-compatible blockchain. These profiles are ideal for testing custom chains, testnets, or any network that implements the Ethereum JSON-RPC specification.
Overview The generic EVM profiles provide:
evm.light : Lightweight profile for basic node testingevm.heavy : Heavy profile for archive nodes with debug/trace methodsUniversal Compatibility : Works with any EVM-compatible chainFlexible Testing : Suitable for both full and archive nodes
Available Profiles evm.light The light profile tests common JSON-RPC methods without resource-intensive operations. Ideal for testing standard node endpoints.
rpc_calls = { EvmUser.eth_get_transaction_receipt: 1 , EvmUser.eth_block_number: 1 , EvmUser.eth_get_balance: 1 , EvmUser.eth_chain_id: 1 , EvmUser.eth_get_block_by_number: 1 , EvmUser.eth_get_transaction_by_hash: 1 , EvmUser.web3_client_version: 1 , }
Wait time : 1 second between requests (using constant_pacing(1))Best for :
Full nodes
Snap sync nodes
Basic infrastructure testing
High-frequency monitoring
evm.heavy The heavy profile tests resource-intensive debug and trace methods. Requires archive nodes with full historical data.
rpc_calls = { EvmUser.debug_trace_block_by_hash: 1 , EvmUser.debug_trace_block_by_number: 1 , EvmUser.debug_trace_call: 1 , EvmUser.debug_trace_transaction: 1 , EvmUser.debug_get_raw_receipts: 1 , EvmUser.eth_get_logs: 1 , EvmUser.trace_replay_block_transactions: 1 , EvmUser.trace_replay_transaction: 1 , EvmUser.trace_transaction: 1 , EvmUser.trace_block: 1 , }
Wait time : 10 seconds between requests (using constant_pacing(10))Best for :
Archive nodes
Debug API testing
Trace API testing
Block explorer backends
Analytics infrastructure
The evm.heavy profile automatically clears debug/trace tag exclusions, enabling these methods without the --debug-trace-methods flag.
Supported RPC Methods All generic EVM profiles support the standard Ethereum JSON-RPC methods:
Light Profile Methods
Heavy Profile Methods
All Supported Methods
eth_blockNumber - Get the latest block numbereth_chainId - Get the chain IDeth_getBalance - Get account balance at latest blocketh_getBlockByNumber - Fetch latest block with full transaction detailseth_getTransactionByHash - Get transaction by hasheth_getTransactionReceipt - Get transaction receiptweb3_clientVersion - Get client implementation version
debug_traceBlockByHash - Trace all transactions in block by hashdebug_traceBlockByNumber - Trace all transactions in latest blockdebug_traceCall - Trace arbitrary contract calldebug_traceTransaction - Trace specific transaction executiondebug_getRawReceipts - Get raw transaction receiptseth_getLogs - Get event logs with filterstrace_block - Get traces for all transactions in blocktrace_replayBlockTransactions - Replay all block transactionstrace_replayTransaction - Replay single transactiontrace_transaction - Get transaction trace The full EvmUser class supports 50+ methods including: Block Methods : eth_getBlockByHash, eth_getBlockByNumber, eth_getBlockTransactionCountByNumber, eth_getBlockTransactionCountByHash, eth_getHeaderByNumber, eth_getHeaderByHash, eth_getBlockReceiptsTransaction Methods : eth_getTransactionByHash, eth_getTransactionReceipt, eth_getTransactionByBlockHashAndIndex, eth_getTransactionByBlockNumberAndIndex, eth_getTransactionCountAccount Methods : eth_getBalance, eth_getCode, eth_getTransactionCountGas Methods : eth_gasPrice, eth_estimateGas, eth_feeHistory, eth_maxPriorityFeePerGasDebug Methods : debug_traceTransaction, debug_traceCall, debug_traceBlock, debug_traceBlockByNumber, debug_traceBlockByHash, debug_getBadBlocks, debug_getRawBlock, debug_getRawHeader, debug_getRawReceipts, debug_getRawTransaction, debug_storageRangeAtTrace Methods : trace_transaction, trace_block, trace_call, trace_callMany, trace_filter, trace_replayTransaction, trace_replayBlockTransactionsNetwork Methods : net_version, net_listening, net_peerCountUtility Methods : web3_clientVersion, web3_sha3, eth_syncing, eth_accounts
Example Commands Light Profile Testing Basic Test
With Latest Blocks
Custom Data Size
chainbench start --profile evm.light \ --users 50 \ --workers 2 \ --test-time 1h \ --target https://your-evm-node-url \ --headless \ --autoquit
Heavy Profile Testing Archive Node Test
With Custom Block Range
Debug/Trace Intensive
chainbench start --profile evm.heavy \ --users 10 \ --workers 2 \ --test-time 1h \ --target https://your-archive-node-url \ --headless \ --autoquit
Single Method Testing Test Specific Method
List Available Methods
chainbench start eth_getBalance \ --users 100 \ --workers 4 \ --test-time 30m \ --target https://your-evm-node-url \ --headless \ --autoquit
Compatible Blockchains The generic EVM profiles work with any blockchain that implements the Ethereum JSON-RPC specification:
Mainnets
Ethereum
BNB Smart Chain
Polygon
Avalanche C-Chain
Fantom
Gnosis Chain
Arbitrum
Optimism
Base
Ronin
And many more…
Testnets
Sepolia
Holesky
Goerli (deprecated)
Mumbai
BSC Testnet
Arbitrum Sepolia
Optimism Sepolia
Base Sepolia
Custom Chains
Private EVM networks
Custom L2 rollups
App-specific chains
Development networks
Chain-Specific Profiles While evm.light and evm.heavy work universally, Chainbench also includes optimized profiles for specific chains:
ethereum.general - Ethereum mainnetbsc.general - BNB Smart Chainpolygon.general - Polygonavalanche.general - Avalanche C-Chainarbitrum.general - Arbitrumoptimism.general - Optimismbase.general - Basefantom.general - Fantomgnosis.general - Gnosis Chain
These chain-specific profiles use realistic method distributions based on actual usage patterns.
Advanced Usage Custom Test Data Range Specify exact block range for test data:
chainbench start --profile evm.light \ --users 50 \ --workers 2 \ --test-time 1h \ --target https://your-evm-node-url \ --start-block 5000000 \ --end-block 5001000 \ --headless \ --autoquit
Using Reference Node Fetch test data from a reference node:
chainbench start --profile evm.light \ --users 50 \ --workers 2 \ --test-time 1h \ --target https://node-under-test \ --ref-url https://reference-node \ --headless \ --autoquit
Batch Requests Test batch JSON-RPC requests:
chainbench start --profile evm.light \ --users 20 \ --workers 2 \ --test-time 30m \ --target https://your-evm-node-url \ --batch \ --batch-size 10 \ --headless \ --autoquit
Light Profile
Recommended Users : 50-500 concurrent usersSpawn Rate : 10-50 users/secondWorkers : 2-8 depending on test machineTest Data Size : S or M for most use cases
Heavy Profile
Recommended Users : 3-20 concurrent usersSpawn Rate : 1-5 users/secondWorkers : 1-2 (trace operations are CPU intensive)Test Data Size : XS or S (larger sizes require significant processing time)
Debug and trace methods are extremely resource-intensive. Start with low user counts and monitor node performance.