Documentation Index
Fetch the complete documentation index at: https://voltaire.tevm.sh/llms.txt
Use this file to discover all available pages before exploring further.
Contract Call Methods
Methods for executing contract calls and transaction simulations.eth_call
Execute a read-only contract call without creating a transaction.callParams: CallParams- Transaction call parametersfrom?: Address- Sender address (optional)to: Address- Contract addressdata: Hex- Encoded function callgas?: Quantity- Gas limit (optional)gasPrice?: Quantity- Gas price (optional)value?: Quantity- ETH value (optional)
blockTag: BlockTag- Block to execute against ('latest','earliest','pending', or block number/hash)
Response<Hex> - Encoded return data
Common use cases:
- Call contract view functions
- Query contract state
- Validate transaction execution before sending
- Simulate complex contract interactions
eth_estimateGas
Estimate gas required for a transaction.callParams: CallParams- Transaction parameters (same aseth_call)
Response<Quantity> - Estimated gas amount
Best practices:
- Always add a buffer (10-20%) to estimates
- Handle estimation failures gracefully
- Consider network congestion in final gas limits
- Test with realistic transaction data
Estimating with Buffer Pattern
eth_createAccessList
Generate an access list for a transaction to optimize gas costs (EIP-2930).callParams: CallParams- Transaction parametersblockTag: BlockTag- Block to execute against
Response<AccessListResult>
accessList: AccessList- Generated access listgasUsed: Quantity- Gas that would be usederror?: string- Optional error message
- Reduces gas costs for complex transactions
- Makes gas costs more predictable
- Required for some contract interactions post-EIP-2930
- Multi-contract interactions
- Transactions touching many storage slots
- Gas optimization for frequent operations
eth_simulateV1
Simulate multiple transactions in sequence (EIP-not-yet-finalized).params: SimulationParams- Simulation configurationblockStateCalls: BlockStateCall[]- Transactions to simulatevalidation: boolean- Enable validationreturnFullTransactionObjects?: boolean- Include full tx objects
Response<SimulationResult> - Simulation results for each transaction
Use cases:
- Test transaction sequences
- Validate multi-step operations
- Debug complex contract interactions
- Estimate total gas for batched transactions
Related
- State Query Methods - Query account and storage
- Transaction Methods - Send and query transactions
- Usage Patterns - Common recipes including gas estimation
- Error Handling - Handle RPC errors

