Subsquid Indexing Comes to Boba Network
We are excited today to announce support for Boba Network, a Layer-2 scaling solution and Hybrid Compute platform that offers lightning fast transactions and fees up to 100x lower than Layer-1s. Boba currently runs networks ‘on-top’ of four EVM chains: Ethereum, Moonbeam, BNB Chain, and Avalanche. To kickstart our support for the ecosystem, we have launched Archives for boba-eth and boba-moonbeam.
Why build with Subsquid on Boba?
> Web3’s fastest indexer: Up to and beyond 50,000 blocks per second
> Familiar TypeScript-based configuration
> GraphQL API ‘out-of-the-box’
> Custom data targets (ie. Google BigQuery, external databases, CSV files)
> Free hosted service (while in beta)
> 100% open-sourceHow to get started with Subsquid on Boba
The best place to get familiar with Subsquid is the official documentation. After getting familiar with the basic architecture of the toolkit, it is recommended to work through the quickstart guide, which shows how to auto-generate a basic GraphQL API from an EVM smart contract ABI. Instructions for further configurations of the squid processor can be found in the EVM indexing article of the docs.
To visit the correct configuration for your preferred Boba chain, access the archive-registry as shown:
const processor = new EvmBatchProcessor()
.setDataSource({
archive: lookupArchive(‘boba-eth’),
})Free hosted service
Web3 developers are often frustrated with the task of maintaining the infrastructure that hosts their indexers. Subsquid’s managed service, which we call ‘the Aquarium,’ has been created to address this issue, and allows builders to deploy their squid indexers as easily as a single command in the terminal.
We are proud to announce that this managed service now fully supports the Boba ecosystem, and is currently available free of charge. It’s worth noting that the launch of Subsquid’s decentralized network will not impact the continued operation of this service. You can leave your squid in the Aquarium for as long as you need it to be there!
Migrate to Subsquid
We have created a step-by-step tutorial for developers who are already using or are more comfortable with the Graph, and want to migrate from Subgraphs to Squid SDK. Even if Subsquid’s programming model does differ from that of the Graph (it maximizes for performance through batch indexing of EVM logs and transaction data), migration does not typically take long, while for ‘heavy’ projects it is frequently a necessity. Many concepts such as code generation from the schema file are the same for both Subsquid and the Graph, and in most cases the schema file can be imported to a squid with any changes.
Why migrate to Subsquid from the Graph?
> 50–100x faster indexing.
> Support for ‘heavy’ factory contracts.
> Full control over the target database, including custom migrations and ad-hoc queries in the handler.
> Extension of the GraphQL API with arbitrary SQL
> Custom data targets and formats (ie. BigQuery, CSV)
> Ability to integrate with external APIs and 3rd part RPC endpoints
> API versioning and aliasing.
> API caching
> GraphQL subscriptionsAbout Subsquid
Subsquid is the team behind squids, a new standard for Web3 data extraction and transformation. Squids already power hundreds of applications across dozens of EVM, Substrate, and WASM-based chains. With modular architecture and a host of advanced features, Subsquid offers the most resource-efficient and developer-friendly way to build, test, and deploy customized GraphQL APIs and ETLs for dApps and blockchain analytics.
