Oasis Consensus
The Oasis Consensus Layer is the foundational, scalable, and high-throughput backbone of the Oasis Network. It is a decentralized Proof-of-Stake (PoS) blockchain that focuses on security and minimal state management, separating consensus from execution to achieve high scalability.
Goldsky powers the web3 products you use
How to index Oasis Consensus data with Goldsky
Turbo Pipelines
Stream Oasis Consensus 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 Oasis Consensus 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 Oasis Consensus data on your machine
Get Oasis Consensus data indexing by --:--
Creating an account is free. No credit card needed.
Oasis Consensus data: frequently asked questions
What is Oasis Consensus?
Oasis Consensus is a blockchain network supported by Goldsky for real-time data indexing and streaming. Goldsky makes it easy to access Oasis Consensus 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 Oasis Consensus data with Goldsky?
Sign up for a free Goldsky account, then deploy a subgraph or pipeline against Oasis Consensus in minutes. Goldsky handles node infrastructure, reorg detection, and data freshness automatically.
How much does it cost to index Oasis Consensus 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 Oasis Consensus data available through Goldsky?
Goldsky indexes Oasis Consensus 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.
154 more chains available
All yours to access, with more being continuously added