RFQ/RFC: 100 Operators Program treasury proposal
3 years ago
I'm requesting for comments / questions on the stake plus treasury proposal for creation of the 100 operators program. This program was designed to decentralize various aspects of the polkadot infrastructure. I'm making the working copy draft version available for review in the link below. This draft proposal is still missing a few elements including justification of expenditures on hardware and supporting references for the problem statement. However, the form, idea and goals are fully
documented.
Comments (3)
Hey, thank you for publishing this proposal. All in all, I think the idea is noble, but there is some information missing, along with some more proposal requirements I would like to see when using treasury funds.
In general, I agree with this statement: "There are several problems with existing infrastructure and trends that infrastructure growth is taking will only exacerbate these issues. These are rooted in an infrastructure provider’s desire to provide high quality services at the lowest price which results in an inevitable decision to use public cloud providers." - the use of public clouds should be gradually avoided and higher cost location included in the set to accomplish better geographic decentralisation.
A few comments and questions that come to my mind when reading the proposal:
Regarding the W3F, there would need to be an entity that registers the IPv4 subnets we will use for anycast deployment. The registration would need to be done with one of the regional registries (ARIN, LACNIC, RIPE, AFRINIC, APNIC). If one of the members registers the subnets they would be owned by the member not the network which could pose a risk in the future. Alternatively, we would/could create a new foundation for this purpose. I will get back to you on the other points.
Thanks for the proposal Tom.
We at Dwellir are one of the infrastructure providers who run our own hardware in co-locations sites.
We see the same challenge as you regarding the centralization around Public Cloud providers. A quick look at the validator distribution on which network they run on, we see how they cluster within the Clouds.
The ecosystem should continue to support different initiatives for decentralization.
If your proposal could be modified so that there will be, as rtti5220 wrote, "skin in the game" for the operators that will be great.
Let the operators of the ecosystem buy the hardware, and then the program can pay a monthly fee to the operators. We want to avoid free-riders, but at the same time help out newcomers get going. Setting the entry barrier right is the challenge.
/Gustav
Dwellir
Would Dwellir be interested in joining? It seemed like you're one of the few existing RPC providers that is operating on owned hardware. I saw on your stats page that your endpoints recently had a surge in RPC queries and that reduced your response time for queries. My benchmark script wasn't even able to make contact with wss on occasion (I'm benchmarking getheader requests). If interested, Ping me on element (@stakeplus:matrix.org) I'll send you an invite to the room where we're discussing program requirements and working together to build this out.