We’re pleased to work with Base to bring SubQuery’s flexible, fast, open, and decentralised data indexing solution that provides blockchain developers with the tools needed to easily organise and query on-chain data for their protocol and applications. Abstracting the backend, SubQuery provides a custom API and lets developers focus on product development and user experience rather than building their own indexing solutions.
“We set out to make Base the most developer-friendly way to build on-chain, that means providing developer tooling and services to make it easy to build, deploy, iterate, and scale your applications on Base. We’re happy to see another multi-chain indexer join our ecosystem, and pleased that developers will be able to utilise SubQuery to build next-gen applications onBase.”— Rowan Stone, Head of BD, Base, and Head of Onchain BD, Coinbase
“We are excited to offer SubQuery’s flexible, fast, open, and decentralised data indexing solution to the Base community. By abstracting backend intricacies, we empower developers to focus on what matters most: product development and user experience. We are confident that our support of Base will help encourage web3 builders to create the next wave of exciting decentralised applications.”— Sam Zou, Founder and CEO of SubQuery
SubQuery is currently focused on decentralising and tokenizing the protocol to build the SubQuery Network. The SubQuery Network will index and service data from projects to the global community in an incentivized and verifiable way and support indexing Base projects, and those from any other supported network from the outset.
Why Use SubQuery?
SubQuery is 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.
SubQuery is designed to be fast, 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.
And finally, in a few months you’ll be able to completely decentralise your SubQuery infrastructure with the SubQuery Network, the future of Web3 infrastructure. The SubQuery Network will index and service your projects data to the global community in an incentivised and verifiable way. It is designed to support any SubQuery project from any supported network including Base, so you can take advantage of the scale of the unified SubQuery Network from launch.
Getting Started with SubQuery and Base
With SubQuery’s Base integration, there are three types of mapping handlers:
- BlockHandler: All blocks and their hash and height
- TransactionHandler: All transactions and their hash, height, and timestamp
- LogHandler: On each and every log that matches optional filter criteria, access various data from the Base logs
SubQuery’s Support for Base
- Advanced Indexing of blocks, transactions, and logs
- A quick start tutorial to see how to index the total faucets dripped to users from the USDC Faucet contract on Base’s Goerli Testnet
- Full support for Base in our free enterprise level managed service
- Example projects for both Base’s Mainnet and Goerli testnet.
- Discord community (including technical support)
About Base
About SubQuery