We recently announced our commitment to expanding the SubQuery Network to decentralise and supercharge RPCs and address a much broader centralisation issue throughout Web3 infrastructure. The SubQuery network will see thousands of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases.
Previously the focus of the SubQuery network was to index and service data to the global community in an incentivised and verifiable way. While this mission remains, it will also do so much more. Today, we will review the participants in the SubQuery network, how they have changed with the SubQuery evolution, and how you can get involved.
Original Participants (The Old Vision)
Previously there were three main types of participants in the SubQuery Network:
Consumers: Consumers ask the SubQuery Network for specific data for their dApps or tools, and pay an advertised amount of SQT for each request.
Indexers: Indexers run and maintain high-quality SubQuery projects in their own infrastructure, running both the indexer and query service, and are rewarded in SQT for the requests that they serve.
Delegators: Delegators participate in the Network by supporting their favourite Indexers to earn rewards based on the work those indexers do.
In the evolved SubQuery Network, Consumers and Delegators remain largely unchanged - there are simply more opportunities. Consumers can purchase more types of services and Delegators will be able to earn more rewards from delegating their tokens to more service providers.
The Indexer role will also remain (now more clearly labelled ‘Data Indexers’) and are our backbone of the network alongside the newest participant, ‘RPC Providers’.
Read on to find out more!
New Participants (The New Mission)
- What’s New: On top of paying the SubQuery Network for specific data via Data Indexers for their dApps or tools, Consumers will also be able to call upon RPC Providers to serve requests in a fast and decentralised manner.
- Requirements: There are no requirements as such to become a SubQuery Consumer. However, Consumers will need to understand how to obtain SQT, how to advertise their data or RPC requirements and how to consume the information returned.
- Is this you: If you're building a decentralised application, blockchain network or analytics project, then you will benefit as a Consumer in the SubQuery Network!
- Where to start: Consumers need to head to the SubQuery Network, obtain SQT tokens to advertise their requirements and then wait for service providers to accept your offering.
- What’s New: The Delegator experience will stay largely the same. However, there are now more Node Operators to choose from in the network and there is potential for higher rewards. Many of our experienced Node Operators have experience running RPC infrastructure so they will likely serve as both Data Indexers and RPC Providers in the network. If your tokens are delegated on a dual-provider, you're likely to earn even more SQT.
- Requirements: One of the best things about being a Delegator is that you don’t need any DevOps, coding, or technical experience. A basic understanding of the SubQuery Network is all that is required to become a Delegator.
- Is this you: If you want an easy way to get involved in the SubQuery Network, then the Delegator role is for you!
- Where to start: Delegators only need to acquire SQT tokens and then learn the process of delegating the tokens to their preferred Data Indexer(s) and/or RPC Provider(s).
- What’s New: The biggest change here is the name, Indexers become ‘Data Indexers’ - this one shouldn’t be too hard to wrap your head around! Data Indexers will still run and maintain high-quality SubQuery indexing projects in their own infrastructure, turning computational and networking power into profits.
- Requirements: To become a Data Indexer on the SubQuery Network, the Data Indexer must possess the necessary hardware, run the required SubQuery services, have a publicly accessible network via a static IP or a domain name, and register as a Data Indexer.
- Is this you: If you’re familiar with running indexing infrastructure, or you’re a keen learner and technically savvy then you might be a Data Indexer!
- Where to start: Follow our step-by-step guide on how to become a Data Indexer.
- What’s New: Everything! As our newest participant in the SubQuery Network, RPC Providers run the optimised SubQuery Data Node and are rewarded in SQT for providing reliable, scalable, and affordable RPC services to the network.
- Requirements: To become an RPC Provider on the SubQuery Network, you must possess the necessary hardware to run a high-performance RPC node, have a publicly accessible network via a static IP or a domain name, and register as an RPC Provider.
- Is this you: If you’re skilled at running and resolving issues with production infrastructure or you’re technically proficient and keen to get involved in web3 infra, then an RPC Provider is a great place to start! If you’ve historically acted as a validator or an RPC provider, you’ll find this very familiar and you’re basically ready to join the SubQuery Network
- Where to start: Stay tuned for step-by-step documentation on how to become an RPC Provider in the SubQuery Network as we roll out the first phase of the evolution.
There’s a role for everyone in the network, from highly technical developers to blockchain beginners. Learn more in our docs or join our Discord and speak to members who are already actively involved in our pre-mainnet. By taking part you can actively or passively earn rewards, help enact change, and power the next generation of the internet.
SubQuery Network is innovating web3 infrastructure with tools that empower builders to decentralise the future. Our fast, flexible, and open data indexer supercharges dApps on over 115 networks, enabling a user-focused web3 world. Soon, our Data Node will provide breakthroughs in the RPC industry, and deliver decentralisation without compromise. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company - we’re a movement driving an inclusive and decentralised web3 era.