+0
日增长
18,714
stars
398
forks
88
watchers
2,196
prs
737
issues
1,054
releases
README
Welcome to SubQuery! Flexible, reliable, and decentralised APIs for your web3 project SubQuery is an Open, Flexible, Fast and Universal data indexing framework for web3. Our mission is to help developers create the decentralised products of the future. SubQuery allows teams across multiple blockchain architectures to process and query their data. The project is inspired by the growth of data protocols serving the application layer and its aim is to help web3 projects build better dApps by allowing anyone to reliably find and consume data faster. Today, anyone can query and extract blockchain data from various supported networks in only minutes and at no cost. The future is multi-chain - SubQuery is no different. SubQuery is well on our way to support all leading blockchain networks with support for the following: - Polkadot (and all Substrate networks) - Ethereum (and all EVM-compatible networks) - Cosmos (and all CosmWasm and Ethermint networks) - Algorand - NEAR - Stellar (including Soroban) - Solana (Beta) - Starknet - Concordium You can also use SubQuery to index data from multiple networks in any combination of the above SDKs. See our Multi-Chain Indexing Quickstart for more details. Get Started Create a SubQuery project You can follow our Quick Start Guide to learn how to create, initialize, build, and publish a new SubQuery Project using the @subql/cli tool. Learn and improve with our comprehensive documentation Dig into every term, usecases, and best-practices that help you build a dApp which your users love. Take a look at our detailed technical documentation. Publish your SubQuery Project to the SubQuery Network Take advantage of the decentralized SubQuery Network to host your project without managing any infrastructure. By publishing to the SubQuery Network, you'll benefit from a reliable, scalable, cost-optimised, and censorship-resistant indexing service. Follow our comprehensive publishing guide to learn how to upload your project to the network and start leveraging its distributed infrastructure today. Publish to managed hosting providers If you prefer a managed hosting option for your indexer deployment, contact our managed hosting partners. Learn more. Run your own Indexer and Query Service Follow our guide to run your own SubQuery local node that you can use to debug, test, and run you own GraphQL server. You're going to need to a Postgres database, a node to extract chain data, and a moderately powerful computer to run the indexer in the background. You'll also use our custom-built GraphQL query service @subql/query to interact with your SubQuery project. MCP (Beta) You can also create, build and deploy SubQuery projects using MCP (Model Context Protocol). Our MCP integration provides all the same functionality as the CLI but works well with LLMs and AI IDEs such as Cursor. Manual configuration For adding SubQuery MCP into other tools, the following command needs be run by the client. bash npx
Top issues
#2863Can't create basic Injective project9 comments · 2025-07-23#2899Using solana-dex-parser with mappings7 comments · 2025-08-29#1887[Reward Cancelled] Allow query historical data by block range5 comments · 2023-07-17#2591Expose more of the schema in gql subscriptions4 comments · 2024-11-13#2747Cannot build using latest subql package versions3 comments · 2025-04-17#2599Big Block Issue Optimization3 comments · 2024-11-22#2590GraphQL subscriptions `mutation_type` is always UPDATE3 comments · 2024-11-13#1911Update docker compose with more flags3 comments · 2023-07-30
Discussions
#3049Silent data loss at the chain tip: 61 fills missing across 5 blocks while lag reported 0 — how does SubQuery defend this?1 comments · 2026-10-22#2636For Hiring web3 developer3 comments · 2024-12-23#2313Codegen and Substrate types0 comments · 2024-03-20#2223graph-node subgraph0 comments · 2024-01-18#1533subql publish command error0 comments · 2023-03-01#1299how allow cors * in node?4 comments · 2022-09-15#1275Schema Migrations1 comments · 2022-08-30#1260FrontierEvm issue: atob is not defined0 comments · 2022-08-23
Latest release
[6.5.0] @subql/node node/6.5.0 2026-10-29[6.5.0] - 2026-10-29 Changed - Update @subql/node-core to 19.4.0 - The spec version dictionary query uses DictionaryV1.query(), and @apollo/client is no longer a dependency (3048)