Simulation

Simulation executes a transaction against the latest block state without sending it to the network, so you can check whether it succeeds, how assets change, and how much gas it uses before signing. With eth_simulateV1, you can run multiple calls sequentially with accumulated state, or run them under assumed state such as balances and storage. You can check asset changes in the execution result logs of eth_simulateV1. When you enable traceTransfers, native token movements are also returned as Transfer logs.

If you broadcast a transaction that is going to fail, no assets move but gas fees are still consumed, and operations teams spend time identifying the cause and reprocessing. When you apply Simulation before the signing request, you can filter out transactions that would fail due to insufficient balance or contract conditions. For institutional wallets, this works as a verification step before withdrawal approval.

Use Cases

• Withdrawal OpsBlock failing withdrawals before signing

  Filter out withdrawals that would fail because of balance, allowance, or contract conditions before signing. This reduces gas costs and the operational effort of reprocessing.

• Risk & ComplianceValidate approval policies based on asset changes

  Compare the assets and amounts that the execution result would move against internal limits and allowed-token policies. Only transactions that pass the policy are forwarded as signing requests.

• Withdrawal OpsPre-check bulk withdrawal batches

  Execute the entire batch cumulatively to separate the transactions that would fail. This prevents failed transactions from breaking the nonce order.

Available APIs

You can check gas limit estimation (eth_estimateGas) and access list creation (eth_createAccessList) together with fee calculation in Preflight.