Skip to main content
POST
eth_getProof
Fantom API method that returns a Merkle proof for a specific account, contract storage, or both for a given block. Merkle proofs enable users to verify the existence and authenticity of data within a Merkle trie, a data structure that helps optimize and secure data retrieval in blockchains.
When called against a block older than the latest ~128 blocks, this method is treated as an archive request (2 RUs instead of 1 RU). See request units.
No longer supportedThe Sonic node client no longer supports eth_getProof for the Fantom chain. See GitHub Issue.
eth_getProof is not available on Fantom Global Nodes — the call returns -32000 method handler crashed. See Fantom methods for the methods that are available.
Get your own node endpoint todayStart 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

  • address — Ethereum address of the account for which the proof is requested.
  • array — the array of 32-byte storage keys that need to be proven and included. See eth_getStorageAt.
  • quantity or tag — the integer of a block encoded as hexadecimal or the string with:
    • latest — the most recent block in the blockchain and the current state of the blockchain at the most recent block.
    • safe and finalized — not supported on Fantom; the request fails with an invalid argument error. Fantom blocks are final as soon as they’re produced, so use latest.
    • earliest — the earliest available or genesis block.
    • pending — the pending state and transactions block. The current state of transactions that have been broadcast to the network but have not yet been included in a block.

Response

  • balance — represents the account balance. Refer to eth_getBalance.
  • codeHash — indicates the code hash associated with the account. For a simple account without any code, the value will be 0xc5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470.
  • nonce — refers to the account’s nonce. See eth_getTransactionCount.
  • storageHash — represents the SHA3 hash of the StorageRoot. All storage data will provide a Merkle proof that starts with this rootHash. This hash serves as the starting point for obtaining a Merkle proof for all storage entries linked to the account.
  • accountProof — an array of RLP-serialized Merkle trie nodes, starting with the stateRoot node and following the path of the SHA3 (address) as the key, which can be used to verify the existence and authenticity of data within the trie.
  • storageProof — contains the requested storage entries in an array, with each entry being an object that includes the following properties:
    • key — the requested storage key
    • value— the value associated with the storage key
    • proof — an array of RLP-serialized Merkle trie nodes, starting with the storageHash node and following the path of the SHA3 (key), which can be used to verify the existence and authenticity of data within the trie.

eth_getProof code examples

The following examples retrieve the Merkle proof for the USDC contract.
Read Deep dive into Merkle proofs and eth_getProof to learn more about the Merkle trie and how to use eth_getProof.

Use case

A use case for the eth_getProof method can be when a decentralized application (DApp) interacts with a smart contract on the Fantom blockchain. The DApp needs to verify the state of the contract’s storage variables without downloading the entire blockchain data. By using eth_getProof, the DApp can request Merkle proof for specific storage slots in the contract. This proof can then be used to cryptographically verify the authenticity and accuracy of the storage data, ensuring the DApp is working with the correct contract state.

Body

application/json
method
string
default:eth_getProof
params
string · string[] · string[]

The address of the account to query.

id
integer
default:1
jsonrpc
string
default:2.0

Response

200 - application/json

The account state proof.

jsonrpc
string
id
integer
result
object
Last modified on November 13, 2026