How to choose the next RPC

SubQuery Mainnet New Features/Ideas
1

We have been thinking of how to get the community involved more in helping to select the next RPC for the SubQuery Network to support.

Some may recall that previously we held a vote on Snapshot which was well received with Solana being the eventual winner.

We are developing a page where anyone can suggest an RPC, and any SQT token holder can then vote. Here is a quick “wireframe” mockup.

image
image1266×815 68.7 KB

The way we see it working is that the RPC with the most amount of votes at the start of each month is the one that will get selected for development.

There is also a freeze period 7 days prior to the end of the month that prevents any more RPCs being suggested or votes being removed at the last minute.

Keen to get some feedback, and hear everyone’s thoughts.

2

It should be possible to identify a network or project that has a need for the service. If it were me I would try to get some sort of commitment from a project that they require X amount of requests per month. Any amount of requests per month lower than at least 100 million would be considered insufficient unless closed agreements were agreed on to incentivize operators. Or something like that.

I don’t think adding a RPC service in the hopes that usage will grow organically is a very good idea.

1 Like
3

Fair comment.

5

Who do you mean has the responsibility to identify the network?

I agree some sort of commitment is essential, that’s why in this process you can see we ask for locking SQT which serves as the commitment.

1 Like
6

Also, I agree that "adding a RPC service in the hopes that usage will grow organically is a very good idea:.

The thinking here is that those who are suggesting the RPC would be the main ones who are wanting to use it or have it available for their community to use. ie there is some sort of initiation motivation already.