zkLink Nova
zkLink Nova is a Layer 3 zkEVM rollup that aggregates liquidity across Ethereum L2s. It enables seamless DeFi and dApp deployment with zk-proof security, fast finality, and cross-chain asset support.
Goldsky powers the web3 products you use
How to index zkLink Nova data with Goldsky
Subgraphs
Query zkLink Nova 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 zkLink Nova who want quick setup & minimal infrastructure overhead
- Production-ready zkLink Nova API endpoints
- Moderate traffic and throughput scenarios
- Predefined data models and standard query patterns
- On-chain data from EVM-compatible chains
Get zkLink Nova data indexing by --:--
Creating an account is free. No credit card needed.
zkLink Nova data: frequently asked questions
What is zkLink Nova?
zkLink Nova is a blockchain network supported by Goldsky for real-time data indexing and streaming. Goldsky makes it easy to access zkLink Nova 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 zkLink Nova data with Goldsky?
Sign up for a free Goldsky account, then deploy a subgraph or pipeline against zkLink Nova in minutes. Goldsky handles node infrastructure, reorg detection, and data freshness automatically.
Can I run a subgraph on zkLink Nova?
Yes. Goldsky Subgraphs run on zkLink Nova 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 much does it cost to index zkLink Nova 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 zkLink Nova data available through Goldsky?
Goldsky indexes zkLink Nova 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.
156 more chains available
All yours to access, with more being continuously added