Firstly, SubQuery crossed a huge milestone in its development of the completion of season 2 of Frontier Testnet. It marks the close of the most critical season, and means that they can move towards final public test network. SQT token sale as we race towards the launch of the SubQuery Network.
Season 2 of the SubQuery Frontier testnet had the following goal: scale the number of indexers to help us fix process issues, find more elusive bugs, and identify scalability concerns. Enlisted more than 80 node operators and invited ambassadors as Indexers to achieve a total of 156 registered Indexers.
Furthermore, also released a few new features as part of our SubQuery Network explorer which you can see for yourself at frontier.subquery.network. This is the first version of the UI that will make it easy and intuitive for consumers to find and select plans, as well as delegators to decide where to delegate their SQT to. One of the best aspects of the testnet is that the explorer that you see retrieves data directly from a SubQuery project. It’s the ultimate test of our own tools and software, where we’ve built a complex project and run it in our own infrastructure to power our own application, just like how our customers do.
With SubQuery Ambassadors joining in this season. They had to focus on documentation to help non-technical ambassadors to get started as indexers. Running nodes and compute instances isn’t the easiest, even for experienced developers, so it’s been interesting observing where people get confused in our node setup guides. Documentation is always extremely important to us at SubQuery, this is even more so when scaling the SubQuery Network to the public testnet (season 3).
Having 156 registered indexers indexing two projects each gave an awesome opportunity to run some stress tests against testnetwork. Always designed the SubQuery to be the most performant, reliable and scalable decentralized infrastructure service out there. Used load generators to simulate real GraphQL requests to prove this. Five rounds of testing allowed to reach a peak sustained load of 2,200 requests per second. Equates to almost 200million requests. They did not see any significant increase in failure rates. As they hit the limit on load generators far before they reached the limit on the network. Can be confident that the network can handle magnitudes more traffic than this test.
The 200 million requests per day figure is what our managed service was handling over a few months ago (it’s much more since then), so we are reassured that our network is capable of handling traffic numbers to become the largest decentralised data network in web3.
In summary, season 2 gives the confidence that need to surge ahead with plans for the TGE. Season 3 (the public round), and ultimately the launch of the SubQueryNetwork. Season 3 will start in few weeks and intend to be one of the earliest test networks on Acala’s parachain.
About SubQuery Network
SubQuery is a blockchain developer toolkit enabling others to build Web3 applications of the future. A SubQuery project is a complete API to organise and query data from layer-1 chains. Currently servicing Polkadot, Substrate and Avalanche projects, this data-as-a-service allows developers to focus on their core use case and front-end. Without needing to waste time on building a custom backend for data processing. The SubQuery Network proposes to enable this same scalable and reliable solution, but in a completely decentralised way.