SubQuery Developer Update: November
As summer arrives down in the southern hemisphere, the team at SubQuery have continued to deliver new features and support new chains that our customers want. In our latest Developer Update we highlight new features and technical improvements to make your indexing even smoother & faster!
- Index data across chain with our new multi-chain indexing
- Avoid chain type issues or stalled networks with the ability to skip a selection or range of blocs
- Indexing speed improvements by optimising our dictionary queries and block queues
- New Chain Support
- Shout outs
- A big thanks to MOZGIII for support for adding settings to GraphQL playground
- Thanks also to kumar8317 to help us identify and fix a bug with our Avalanche indexer
SubQuery is a fast & flexible blockchain indexing toolkit that powers hundreds of teams on Polkadot, Avalanche, Algorand, Flare and Cosmos. We help developers focus on their core product, rather than waste time and money building their own indexing solution.
Multi Chain indexing
Multi-chain indexing allows you to index data from across different networks into the same database. This allows you to combine and aggregate data from different chains, or see the full picture when indexing XCM or IBC cross chain messages. Once indexed, you can query the data for all supported networks via a single GraphQL endpoint.
You can use the same SubQuery project, which includes the same GraphQL schema and mapping files to achieve this. It means that SubQuery is truly a write once, run anywhere multi-chain indexer.
For example, you could capture XCM transaction data from all Polkadot parachains or monitor IBC messages across Cosmos Zones in a single project, with a single database, and a single query endpoint.
The ability to skip problematic blocks
Bypass Blocks allows you to skip a number of blocks on a chain when indexing. On some chains, new chain type updates can make some older blocks impossible to decode. On other chains like Juno, some blocks were intentionally skipped after a runtime upgrade.
This feature accepts both a range or single integer entry into an array, and since it’s in the project manifest, it will ensure that proof of indexing can still be verified for an indexer working on this project.
Improvements to dictionary queries to speed up projects
A dictionary is a must have when indexing blockchain data. It records metadata of events, transactions, extrinsics, and types in a SubQuery project in a way that allows your own project to know exactly where to look when indexing. We’ve completed a number of under the hood improvements that make dictionary queries faster from your project, speeding up the indexing performance in the process and decreasing load on our dictionaries so we can scale as more customers connect to them.
New Chain Support
SubQuery is proud to announce its data indexing support for the Flare network. Flare supports EVM-based smart contracts, and has data and interoperability infrastructure built natively into the blockchain, providing dApps with highly decentralized price feeds and secure state acquisition from other blockchains.
Flare Network developers can now benefit from the full SubQuery experience, including the open-source SDK, tools, documentation, developer support, and other benefits developers receive from the SubQuery ecosystem. Additionally, Flare Network is accommodated by SubQuery’s managed service, which provides enterprise-level infrastructure hosting and handles over 400 million requests each day.
SubQuery is proud to announce it has extended its data indexing support within the Cosmos ecosystem with its latest partnership with Cronos, the blockchain supported by the Crypto.com exchange. As a result of the integration, SubQuery now supports the Ethermint blockchain unlocking further opportunities for web3 developers building on top of it.
After its rapid expansion into the Cosmos ecosystem with integrations with Juno, Fetch.ai, Stargaze and Cosmos Hub in the last few months, SubQuery received support from the Cronos Ecosystem Grants programme to develop the first indexing solution specifically for builders in Cronos.
OKC (OKX chain)
SubQuery’s goal has always been to provide fast and efficient indexing to the widest variety of chains possible. This month we started supporting another Cosmos chain: OKC (OKX Chain)! OKC (OKX Chain) is an EVM-compatible L1 built on Cosmos with a focus on true interoperability (IBC) and maximized performance.
OKC will benefit from the full SubQuery experience, including the open-source SDK, tools, documentation, developer support, and other benefits developers receive from the SubQuery ecosystem. Additionally, OKC is accommodated by SubQuery’s managed service, which provides enterprise-level infrastructure hosting and handles over 400 million requests each day.
- A big thanks to MOZGIII for contribution to our codebase supporting the adding of settings to GraphQL playground Github
- Thanks also to kumar8317 to help us identify and fix a bug with our Avalanche indexer Github
- View the releases page for more information
- Developer documentation
- Discord community (including technical support)
SubQuery is a blockchain developer toolkit facilitating the construction of Web3 applications of the future. A SubQuery project is a complete API to organise and query data from Layer-1 chains. Currently servicing Polkadot, Avalanche, Algorand, Cosmos and Flare projects, this data-as-a-service allows developers to focus on their core use case and front-end without wasting time building a custom backend for data processing activities. In the future, the SubQuery Network intends to replicate this scalable and reliable solution in a completely decentralised manner.
Linktree | Website | Discord | Telegram | Twitter | Matrix | LinkedIn | YouTube