Tempo
Tempo is a purpose-built, layer 1 blockchain for payments, developed in partnership with leading fintechs and Fortune 500s. With support for all major stablecoins, Tempo enables high-throughput, low-cost global transactions for any business use case.
Goldsky powers the web3 products you use
How to index Tempo data with Goldsky
Turbo Pipelines
Stream Tempo data with the latest blockchain data streaming engine. Vectorized processing, instant deployment, and live data inspection without needing an enterprise team.
Ideal for:
- Instant deployment – pipelines spin up in seconds; index Tempo instantly
- Live data previews – inspect what every part of your pipelines produce in real-time
- TypeScript transforms – execute custom logic with WebAssembly
- Dynamic tables – unlimted filtering on addresses & contracts without redeploying
- Local debugging – iterate on Tempo data on your machine
Mirror
Stream Tempo data directly into your own database for maximum control. Designed for scaling ambitious projects and unlocking full ownership of your data.
Ideal for:
- Teams building on Tempo who need full control over data storage, infrastructure, and processing
- Combining on-chain Tempo data with off-chain data
- Ultra-low latency for the most demanding apps
- Multi-chain projects expanding into Tempo or building cross-chain functionality
- High traffic and throughput scenarios
Subgraphs
Query Tempo data with an instant GraphQL API. Perfect for familiarity, fast setups, on-chain data queries, and getting to market quickly.
Ideal for:
- Teams building on Tempo who want quick setup & minimal infrastructure overhead
- Production-ready Tempo API endpoints
- Moderate traffic and throughput scenarios
- Predefined data models and standard query patterns
- On-chain data from EVM-compatible chains
Get a Tempo RPC endpoint
Edge RPC
Create an instant Tempo RPC endpoint with global edge distribution. Built for apps that demand reliable, low latency access without running your own node infrastructure.
Key benefits:
- <10ms latency from tip-of-the-chain CDN
- <50ms latency from 8+ global edge regions
- 99.9% uptime with automatic failover
- Data integrity mechanisms & cross-validation
- Optimized for indexing
- Built-in observability
- Compatible with your existing RPC endpoints
Deploy your Tempo data stack by --:--
Creating an account is free. No credit card needed.
Tempo data: frequently asked questions
What is Tempo?
Tempo is a blockchain network supported by Goldsky for real-time data indexing and streaming. Goldsky makes it easy to access Tempo data through subgraphs, data pipelines, and RPC endpoints, so your team spends less time on infrastructure and more time building your product.
How do I start indexing Tempo data with Goldsky?
Sign up for a free Goldsky account, then deploy a subgraph or pipeline against Tempo in minutes. Goldsky handles node infrastructure, reorg detection, and data freshness automatically.
Can I run a subgraph on Tempo?
Yes. Goldsky Subgraphs run on Tempo and are fully compatible with The Graph protocol, so you can migrate existing subgraphs with a single CLI command. Queries are served via a standard GraphQL API with sub-second indexing latency.
How do I stream Tempo data to my database or data warehouse?
Goldsky Mirror streams Tempo blockchain data in real time to destinations like PostgreSQL, BigQuery, S3, Kafka, and more. You define a pipeline in a YAML config and Goldsky handles delivery, reorgs, and schema management. No custom ETL code required.
Does Goldsky offer a Tempo RPC endpoint?
Yes. Goldsky Edge provides a low-latency Tempo RPC endpoint with global edge distribution, high availability, and automatic failover. It is a drop-in replacement for any standard EVM JSON-RPC provider.
How much does it cost to index Tempo data with Goldsky?
Goldsky offers a free plan with generous limits so you can start building right away. Paid plans scale with usage. Creating an account is free and no credit card is required to get started.
How fresh is the Tempo data available through Goldsky?
Goldsky indexes Tempo blocks as they land on-chain, typically delivering data with sub-second latency after confirmation. Reorgs are handled automatically, so your application always reflects the current canonical chain state.
155 more chains available
All yours to access, with more being continuously added