Hello SubQuery Node Operators,
We announcing a significant change in how we distribute requests from the SubQuery Gateway (primarily RPC requests but also dictionary requests for data indexing projects) to our network’s Node Operators. This update aims to enhance the performance and reliability of our network while allowing market dynamics to play a greater role in request distribution.
Previous Distribution Criteria:
Until today, we have been distributing requests based on three primary factors:
- Your indexer’s health.
- Low latency of your node.
- A flex plan price below a certain minimum.
New Distribution Criteria:
Starting today, we are introducing a more nuanced approach that considers several additional factors. This change aims to ensure that our network can meet the increasing demand for low latency and high reliability from enterprise RPC consumers. Here are the new factors that will influence the distribution of requests (in decreasing order of importance):
-
Block Height Proximity:
- Your block height should always be within 3 blocks of the chain head. If you fall more than 3 blocks behind, the number of requests you receive may drop exponentially. With the rising demand for low block latency, it’s crucial to ensure your RPC is adequately resourced to stay up to date.
-
Pricing:
- We are increasing the maximum accepted price to the numbers in the table below. We hope the market will dictate pricing, but it’s important to note that lower-priced node operators will receive proportionally more requests compared to higher-priced ones.
- Soon you will also have more visible pricing details available, including being able to clearly see the current flex plan pricing of all node operators at a glance
- New Pricing Caps:
- Data Indexing Projects: Increased price cap 10x to 10 SQT per 1,000 requests
- RPC Projects: Increased price cap 5x to 5 SQT per 1,000 requests
-
Up to Date Service Versions:
- Running the most recent two minor versions of the SubQuery proxy and coordinator service will also impact the number of requests you receive. Keeping your software up to date is crucial for optimal performance and security.
-
HTTP2 Enablement:
- Nodes with HTTP2 enabled will be preferred, as it offers better performance and efficiency.
-
SSL Enablement:
- Security is paramount, so having SSL enabled on your nodes will positively impact your request distribution.
-
Social Proof (ENS Domain):
- Nodes with social proof enabled, such as an ENS domain, will be favored. This helps establish trust and reliability within the network.
In the future as we run more gateways, we will also start to incorporate request latency as an indicator here. This will allow us to better route requests faster to closer nodes. However it’s important first, that we don’t allow this to encourage centralisation around our gateways.
Why are we making this change
By adhering to these new criteria and striving for performance, high-quality node operators can expect to receive significantly more requests, which in turn will increase their income from the network. This change is designed to reward those who invest in maintaining high standards and contribute to the overall improvement of the network.
Improving the quality of service provided by our node operators directly translates to a higher overall network service quality. This enables us to attract and support more enterprise customers who demand top-tier performance and reliability.
Action Items for Node Operators:
- Ensure your block height is consistently within 3 blocks of the chain head.
- Consider adjusting your pricing strategy to remain competitive but sustainable.
- Upgrade to the latest two minor versions of the SubQuery proxy and coordinator service.
- Enable HTTP2 and SSL on your nodes.
- Set up social proof, such as an ENS domain, to boost your credibility.
We are confident that these changes will help create a more dynamic and efficient network, benefiting both node operators and RPC consumers. Your cooperation and adherence to these new guidelines are greatly appreciated.
Thank you for your continued support and commitment to the SubQuery network.