How it works
Firehose streams full blocks over gRPC, including transactions, receipts and logs, with cursors so a consumer can resume exactly where it stopped after a restart or a reorg. The same stream serves both historical and live blocks, so one integration covers backfill and tail. Celo blocks are served at Firehose’s base detail level: call traces, internal transfers and storage changes are not included. Those extended fields are produced by an instrumented node, which Pinax does not currently run for Celo. The Graph’s networks registry records the same for Celo —"evmExtendedModel": false and "blockFeatures": ["base"].
Substreams runs on top of Firehose. You write modules in Rust, package them as an .spkg file, and run them on Pinax servers to turn raw blocks into the shape your application needs. Output can go to PostgreSQL or ClickHouse, stream to a consumer, or feed a Graph Node as a subgraph data source.
Pinax RPC serves standard Ethereum JSON-RPC 2.0 from archive nodes, so historical state is queryable at any block.
Endpoints
pinax.network/chain/celo is the canonical list of Pinax’s Celo endpoints. The tables below are examples, and that page is the one to trust if they ever disagree.Celo mainnet
Celo Sepolia
Firehose and Substreams are available on Celo mainnet only. Celo Sepolia is served over RPC.
Calling RPC without an API key
The RPC endpoints also answer unauthenticated requests, so aneth_chainId call with no key returns 0xa4ec on mainnet and 0xaa044c on Sepolia. Those requests take a rate-limited anonymous path, served only from Pinax’s own nodes with no fallback capacity behind them. Send an API key for the full routing and for per-key rate limits — see the RPC documentation.
Resources
Related
- Indexers overview - other indexing options on Celo, and when each one fits.
- The Graph - subgraphs, which can use Substreams as a data source.