XDC Network
XDC Network is an enterprise-grade, EVM-compatible Layer 1 optimized for global trade, asset tokenization, and cross-border payments. It uses XDPoS consensus and supports public/private chain configurations.
Goldsky powers the web3 products you use
How to index XDC Network data with Goldsky
Subgraphs
Query XDC Network 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 XDC Network who want quick setup & minimal infrastructure overhead
- Production-ready XDC Network API endpoints
- Moderate traffic and throughput scenarios
- Predefined data models and standard query patterns
- On-chain data from EVM-compatible chains
Get XDC Network data indexing by --:--
Creating an account is free. No credit card needed.
XDC Network data: frequently asked questions
What is XDC Network?
XDC Network is a blockchain network supported by Goldsky for real-time data indexing and streaming. Goldsky makes it easy to access XDC Network 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 XDC Network data with Goldsky?
Sign up for a free Goldsky account, then deploy a subgraph or pipeline against XDC Network in minutes. Goldsky handles node infrastructure, reorg detection, and data freshness automatically.
Can I run a subgraph on XDC Network?
Yes. Goldsky Subgraphs run on XDC Network 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 XDC Network 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 XDC Network data available through Goldsky?
Goldsky indexes XDC Network 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