Skip to content

Willow RPC

Willow RPC is an Ethereum JSON-RPC endpoint for blocks, transactions, receipts, and logs on the chains listed below. It supports any contract and any event over any block range. Every block is verified against its block hash before any data from it is stored or served.

Account state is served on the same endpoint, on plans that include state methods. Balances, nonces, code, storage, and eth_getProof are verified against the state root of a verified block. eth_call and eth_estimateGas on Ethereum, Unichain, and Robinhood Chain are executed over verified state, and on Ethereum and Unichain the trace methods run the block again over verified state. Fees are computed from verified blocks with a published formula. Sent transactions are forwarded to a provider. See State methods.

Responses can also be verified independently, without trusting Willow. The willow_* proof methods return the proofs behind the standard methods, and @willow-network/rpc, a viem transport and ethers provider, verifies each response before the app sees it, or reports why it can’t.

On the chains marked below, any eth_getLogs result can be requested with a log proof. A log proof establishes that each returned log is included in its block, and that no log in the requested range matching the filter was omitted. Proofs can be verified independently, in a browser or from the command line. The assumptions a verifier relies on are listed in Verifying proofs.

ChainChain IDLog proofs
Ethereum1Yes
Base8453Yes
Arbitrum One42161Yes
OP Mainnet10Yes
Unichain130Yes
Ink57073Yes
Robinhood Chain4663Yes
BNB Smart Chain56No
World Chain480No
Soneium1868No
Zora7777777No
Base Sepolia84532No
Arbitrum Sepolia421614No
OP Sepolia11155420No
Unichain Sepolia1301No
Ink Sepolia763373No
Robinhood Chain Testnet46630No
Polygon137No
Monad143No
HyperEVM999No
Celo42220No
Linea59144No
Mantle5000No
Plasma9745No
Berachain80094No
opBNB204No
Katana747474No
X Layer196No
Arc5042No
ApeChain33139No
Monad Testnet10143No
Ethereum Sepolia11155111No
StellarstellarNo

Block, transaction, and receipt proofs are available on the first 17 chains in the table. On the next 15, from Polygon to Ethereum Sepolia, Willow’s servers verify each block before serving it, but no proofs are served yet, so their responses can’t be verified independently. HyperEVM’s blocks can’t be proven from public data. Stellar is served with stellar-rpc’s read methods, and its ledgers, transactions, and Soroban events can be verified against SCP, the consensus of Stellar’s validators (see Chains and URLs).

A single API key is valid on every chain. Endpoint URLs are listed in Chains and URLs.

Willow RPC is designed for indexers, analytics platforms, RPC routers, auditors, and AI agents that read large volumes of chain data, and for applications that read account state and submit transactions.

  • Verification. Every block is verified against its block hash before any data from it is stored or served. On Ethereum, the canonical chain is determined with the Helios light client. On the L2s, it is determined from the sequencer’s signature, and on BNB Smart Chain from its validators’. See How Willow verifies data.
  • Retention. All data Willow serves is retained. Ethereum is held in full from genesis. On the other chains, blocks older than those held are fetched on the first request from a paying account, verified, and retained. See History.
  • Proofs. Log proofs are generated on request and priced per block, at a flat rate per chain. Every log proof is retained, so a block proven once is available to all later requests without being proven again. The proofs of blocks, transactions, receipts, state, calls, traces, and fees are returned immediately. See Proofs.

Contact [email protected], or ask in the Willow Discord.