Build your RPC knowledge

An RPC request is a JSON-RPC call from your app to a blockchain node. See how a call travels from our edge to a node and back.

How it works

Your app sends a request such as eth_call to an endpoint. An Envoy edge gateway receives it, and a Rust router checks the key, classifies the method and picks a healthy backend by head lag, error rate and latency.

Before reaching a node, the request checks a cache keyed by block hash. Immutable data can be served from it. Anything else goes to a per-chain node pool, and history or trace_ calls go to the Reth archive tier.

Why Reorgs Matter

A reorg happens when a chain replaces recent blocks with a different version. Data you read from the latest block may later change. Ethereum finalises after about 13 minutes, and rollups settle after that.

That is why we key the cache by block hash and never cache latest or pending beyond one block time. Data tied to a block hash cannot change, so it is safe to reuse.

Who is this for?

Protocols and DeFi Teams

Read logs and state reliably, and understand which results can still change after a reorg.

Learn More

Exchanges and Custodians

Know how finality, head lag and caching affect the balances and transactions you display, and which calls to wait on.

Learn More

Enterprise and fintech

Wallets and apps can use standard JSON-RPC and WebSocket subscriptions on six EVM chains at launch.

Learn More

Enterprise and Fintech

Understand what an SLA measures and how availability is probed independently from three regions.

Foundations and Ecosystems

Plan capacity for your ecosystem with dedicated nodes and named solutions engineers.

Data Teams

Use decoded events and traces through SQL and GraphQL instead of running your own pipeline.

Tessellate Supports Six EVM Chains at Launch

Ethereum
ETH
Linea
LINEA
Scroll
SCR
Unichain
UNI
Polygon
POL
Arbitrum One
Arbitrum One
Avalanche
Avax
Gnosis
GNO
Base
BASE
Optimism
Optimism

RPC with Tessellate

Explore insights from our engineers