Skip to content
Edit this page

Supported Methods＃

Wormhole Queries provides on-demand access to Guardian-attested on-chain data through a simple REST endpoint. It offers a faster, gasless alternative to traditional transaction-based data retrieval, removing the need for gas fees and transaction finality delays. Requests are handled off-chain and processed by the Guardians, delivering verified data efficiently and cost-effectively.

This page describes Wormhole Queries, their functionality, and available methods, aiming to assist new developers in utilizing the service.

Supported Query Types＃

Wormhole currently supports five distinct query types, each designed for specific data retrieval tasks across various chains.

Note

For a more comprehensive technical description and further specifics on each query type, please consult the white paper.

eth_call＃

The eth_call query type allows you to perform read-only calls to a smart contract on a specific block, identified by its number or hash. Some of eth_call's configurations include:

  • Batching - group multiple calls, even to different contracts, into a single query targeting the same block, which is processed as one batch RPC call to simplify on-chain verification
  • Capacity - batch up to 255 individual in a single eth_call query
  • Result data - provides the specified block's number, hash, timestamp, and the output from the contract call

eth_call_by_timestamp＃

The eth_call_by_timestamp query is similar to a standard eth_call but targets a specific timestamp instead of a block ID. This is useful for retrieving on-chain data based on a precise point in time, especially for correlating information across different chains.

The query returns your target timestamp and the latest block details at or before your specified target_time immediately preceding the subsequent block.

eth_call_with_finality＃

The eth_call_with_finality query type functions like a standard eth_call, but with an added critical assurance: it will only return the query results once the specified block has reached a designated level of finality on its chain.

You can specify one of two finality levels for your query:

  • Finalized - indicates the highest level of assurance that a block is permanent and will not be altered or removed from the chain
  • Safe - refers to a block considered highly unlikely to be reorganized, offering a substantial degree of confidence, though the network's consensus may not fully finalize it

Note

If the target blockchain does not natively support or recognize the safe finality tag, requesting safe finality will be treated as a request for finalized finality instead.

sol_account＃

The sol_account query reads on-chain data for one or more specified accounts on the Solana blockchain. This functionality is similar to using Solana's native getMultipleAccounts RPC method, enabling you to retrieve information for multiple accounts simultaneously

sol_pda＃

The sol_pda query reads data for one or more Solana Program Derived Addresses. It streamlines the standard process of deriving a PDA and fetching its account data.

This is particularly useful for accessing multiple PDAs owned by a specific program or for verifying Solana PDA derivations on another blockchain, such as how associated token accounts are all derived from the Associated Token Account Program.