Polkassembly Logo

Head 1
Head 3
Head 4
Create Pencil IconCreate
TRACKS
ORIGINS
Report an issueNeed help with something?
Foot 1
Foot 2
Foot 3
Foot 4
OpenGov
View All Discussion

Funded High Performance Public Infrastructure for the entire Polkadot and Kusama Ecosystem (OnFinality)

james_bayly
2 years ago
infra
rpc
parachain
parachains

Tldr;

  • OnFinality has a proven track record providing RPC API support for 68 substrate networks
  • To help cash-starved parachains through the winter, we propose funded complete support for the entire Polkadot ecosystem - this will cover the existing 38 Polkadot parachains
  • Each parachain network will be allocated US$620 of base funding each month for this service which will be held by OnFinality to explicitly provide the service. In our experience, this is the average funding that we require to provision, run, maintain, and monitor a basic service for each small network. Unused prorated amounts will be refunded at the end.
  • Historic data has shown us that this should be sufficient to serve up to 5 million daily API responses with careful rate limiting and DDOS protection. 
  • For the few larger networks that exceed these requirements (e.g. Polkadot's RPC endpoint), those sovereign parachains will be responsible for all costs above the base $620 funding.
  • We will also start working with other ecosystem infrastructure providers to work on a more sustainable long term solution

Background and Problem Statement

As Polkadot’s largest and most cost efficient infrastructure provider, since November 2020 we've provided access to dedicated node support and free public API service for over 68 networks in the Polkadot / Kusama ecosystems. We’ve always made it our goal to provide complete support for the entire Polkadot ecosystem. For RPC API services, historically we have sought funding from the sovereign parachain teams themselves for funding the ongoing operating expenses of these services. However, as the crypto winter has hit hard, many teams are no longer able to fund core public good services like public RPC endpoints.

This has a detrimental effect on applications that serve the Polkadot ecosystem (many of which are our customers). Wallets (e.g. Talisman and Nova), explorers (e.g. Subscan and Polkaholic), account tools (e.g. Sub.ID), indexers (e.g. Subsquid and SubQuery), governance applications (e.g. Polkassembly and Subsquare), and thousands of other applications in each ecosystem struggle to find reliable, performant, and SLA supported RPC API endpoints for many smaller networks.

“If we had some public good service that helps grass root teams it would be a tremendous help for teams such as ours” - Imbue

This is causing a divide in our ecosystem between highly funded parachains that can survive the winter, and new emergent chains that are struggling to get started - we’re seeing first hand that the number of growing new parachains in Polkadot is stalling.

Proposed Solution

We’re requesting globally accessible and equitable funding from the treasury to cover a basic RPC API service (full archive and trace node support included) for all active Polkadot and Kusama parachains to provide immediate relief until we can set up a Parachain Infrastructure Bounty.

This proposal will cover US$620 of base funding each month for each parachain’s API service. To start with, we budget that there will be 38 parachains that take us up on this offer (all parachains with an active lease will be eligible). The total combined running cost for each month is estimated at USD $23,560.00 - all inclusive of capital and operating expenses, administration time from OnFinality DevOps, onboarding costs, backup costs, and all other monitoring and right-sizing by our team.

Longer term solution

“Teams need to coordinate/negotiate with all sorts of partners (block explorers, rpc node providers, wallets, other parachains). This slows down innovation for Kusama.” - Interlay

Multiple parachains have privately and publicly affirmed that one of the biggest challenges is dealing with all the tertiary providers needed to run a production parachain (RPC nodes, block explorers, indexers, governance pages, wallets integrations and more).

We propose that in the long term, we create a new “Parachain Infrastructure Bounty”, that provides basic public services for all active parachins for both ecosystems. The aim is to make the ecosystem more harmonious, unify processes and tools, speed up development progress, and will help all new teams get started.

But setting this bounty up and communicating with the large number of stakeholders will take a long time. At this stage, we expect at least 5 RPC providers, 4 wallets, 3 block explorers, 2 indexers, and 2 governance tools will want to be party to this bounty if it encompasses all “public good infrastructure”.

As a result, in order to establish precedent, and to provide quick pain relief to all parachains next week, our view is to proceed with the current immediate solution now.


Please read the full proposal here including a collection of feedback and discussion from community members here

Comments (4)

2 years ago

This proposal is a significant step in the right direction to support the ecosystem and solidify the infrastructure of the Polkadot Network. The ecosystem depends on a solid Node-RPC infrastructure to support multiple tools and services which many need and use every day:

  1. mobile and desktop wallets
  2. indexers and APIs
  3. explorers
  4. aggregators
  5. specialized UIs: bridges, staking...
  6. business metric collection from third-party teams / Parity

These are public good components that unfortunately need to rely on RPC nodes supported by Parachain teams. Many of these teams unfortunately may not have the time, bandwidth, or resources to support such demanding public goods services. And even if they were to have the time, bandwidth, and resources, it represents yet another barrier to entry and added costs for them to be in the ecosystem.

Passing this proposal at the Polkadot level will mean quite a lot for the ecosystem as a whole:

  1. RPC APIs will become more stable and affordable, thus helping the other previously mentioned components be more stable
  2. Reduce barrier to entry for new parachain teams which should lead to more builders and activity on the network
  3. Reduce overhead for existing parachain teams allowing them to focus on core protocol innovations

Because of all the above, I personally support this proposal and will vote accordingly.

Eliott - CTO @ Nodle

2 years ago

Sharing experience from parachains POV:

  • The key problem is the massive overhead for parachain teams to operate all sorts of infrastructure. This is cost for running the infra, having the people that maintain these nodes (monitoring, upgrading, backups, ...)
  • Parachain teams are essential for the success of Polkadot. Polkadot is not succeeding at the moment as it has comparatively way too little users compared to other ecosystems (like Arbitrum, Optimism, ...)
  • Parachain teams have a very long time to market. I think most projects take about 2 years from start to a parachain slot launch. That is way too much time to validate a product.
  • Instead of having the entire focus on the product and its validation, parachain teams need to coordinate/negotiate with all sorts of partners (block explorers, rpc node providers, wallets, other parachains). This slows down innovation for Polkadot.

While there are many problems, having a treasury funded rpc node provider is a good start to help parachain teams, help Polkadot, and help innovation to happen more quickly.

Dom - Co-founder Interlay

Load more comments
PleaseLogin to comment

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

A House of Commons Initiative.

Polka Labs Private Limited 2025

All rights reserved.

Terms and ConditionsTerms of Website
Privacy Policy