Following our recent release of our support for BNB Chain, in this article we share a detailed developer guide for the BNB community to use to solve their data indexing needs, including how to migrate from The Graph or use our Managed Service.

SubQuery is an open data indexer that is designed to be flexible, fast and provide universal coverage. Our open indexing tool empowers developers to;

  • Build their own API that exposes on-chain data for their dApps in hours
  • Index chains incredibly quickly with the assistance of dictionaries (pre-computed indices)
  • Take advantage of multithreading and optimisation of the store to reduce costly database writes resulting in faster indexing and faster iterations.

Our experience with customers across all verticals in Ethereum, Polygon, Polkadot, Cosmos, Algorand, NEAR and Avalanche (such as wallets, networks, explorers, NFT, DeFi, scanners, etc.) has helped us build the best Indexer for Developers in web3.

Our BNB support is still in its beta, and while we’ve completed considerable testing to ensure that it’s stable, we have further improvements to massively increase the performance and features. Watch this space!

Why Use SubQuery?

SubQuery also brings some major improvements to existing decentralised indexing solutions, including users of The Graph. For one, SubQuery is far more flexible with the ability to make external API calls or import external libraries from within your mapping functions, and better controls to run your projects in your own infrastructure with automated DOS (denial of service) mitigation controls. Additionally, we have no plans to sunset our managed service.

Both SubQuery and The Graph are designed to index data fast, but analysis shows that the existing beta support from SubQuery is already 1.85x faster for common projects over The Graph (e.g the standard Ethereum Name Service project). This adds up when you’re indexing millions of blocks, and is something to consider when choosing your indexer. SubQuery achieves this by using mulit-threading and optimisation of the store to reduce costly database writes. With faster sync times, developers can iterate faster and deliver features to market quicker.