POST
/
2f6d649e68c2f861fecd5b8a9e35139e
eth_simulateV1
curl --request POST \
  --url https://ethereum-mainnet.core.chainstack.com/2f6d649e68c2f861fecd5b8a9e35139e \
  --header 'Content-Type: application/json' \
  --data '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_simulateV1",
  "params": [
    {
      "blockStateCalls": [
        {
          "blockOverrides": {
            "baseFeePerGas": "0x9"
          },
          "stateOverrides": {
            "0xc000000000000000000000000000000000000000": {
              "balance": "0x4a817c800"
            }
          },
          "calls": [
            {
              "from": "0xc000000000000000000000000000000000000000",
              "to": "0xc000000000000000000000000000000000000001",
              "maxFeePerGas": "0xf",
              "value": "0x1"
            },
            {
              "from": "0xc000000000000000000000000000000000000000",
              "to": "0xc000000000000000000000000000000000000002",
              "maxFeePerGas": "0xf",
              "value": "0x1"
            }
          ]
        }
      ],
      "validation": true,
      "traceTransfers": true
    },
    "latest"
  ]
}'
{
  "jsonrpc": "<string>",
  "id": 123,
  "result": {}
}

Ethereum API method that enables simulation of complex transactions and state changes without modifying the blockchain. This method is particularly useful for testing and debugging smart contracts, estimating gas costs, and analyzing the potential outcomes of transactions before committing them to the network.

Data from full node only

Running eth_simulateV1 will yield a full node response—i.e. only the data from the latest 128 blocks. Archive data is not supported for this call and the node will respond with missing trie node.

Get your own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • object — the simulation request object:
    • blockStateCalls — an array of block state call objects:
      • blockOverrides — (optional) an object to override block-level parameters:
        • baseFeePerGas — (optional) the base fee per gas for the block, encoded as hexadecimal.
      • stateOverrides — (optional) an object to override account states:
        • <address> — the address of the account to override:
          • balance — (optional) the balance to set for the account, encoded as hexadecimal.
      • calls — an array of transaction call objects:
        • from — the address from which the transaction is sent.
        • to — the address to which the transaction is directed.
        • maxFeePerGas — (optional) the maximum fee per gas the sender is willing to pay.
        • value — (optional) the value sent with the transaction, encoded as hexadecimal.
    • validation — (optional) a boolean indicating whether to perform validation checks.
    • traceTransfers — (optional) a boolean indicating whether to trace value transfers.
  • quantity or tag — the integer block number, or the string "latest", "earliest" or "pending".

​
Response

  • object — the simulation result:
    • blockResults — an array of block result objects:
      • blockNumber — the block number of the simulated block.
      • blockHash — the hash of the simulated block.
      • stateRoot — the state root of the simulated block.
      • receipts — an array of transaction receipt objects for each simulated transaction.
    • traces — (if traceTransfers is true) an array of transfer trace objects.

​
Use case

eth_simulateV1 is particularly useful for developers working on complex smart contracts or DApps. It allows for the simulation of intricate transaction sequences, including multiple contract interactions and state changes, without the need to deploy contracts or spend real gas. This can be invaluable for:

  • Debugging complex smart contract interactions
  • Estimating gas costs for multi-step transactions
  • Analyzing the potential outcomes of different transaction scenarios
  • Testing contract upgrades or migrations before deployment

Body

application/json

Response

200 - application/json

Successful response

The response is of type object.