Bounty Proposal for Public RPCs for Relay and System Chains

Deciding
Content
AI Summary
Reply
Up
Share
Request
110.68KDOT
Status
Decision28d
Confirmation
7d
Attempts
0
Tally
100%Aye
0%Nay
Aye
27.52MDOT
Nay
19.84DOT
  • 0.0%
  • 0.0%

    Threshold

  • 0.0%
Support
0.55%
8.86MDOT
Issuance
1.61BDOT
Votes
Nested
Flattened
Actions
Or do delegation here, check wiki.
Call
Metadata
Timeline3
Votes Bubble
Curves
Statistics
Comments

Helixstreet is delighted to do its civic duty and cast a vote in favor of this funding proposal. Thanks for organizing this.

Edited

Reply
Up

When will there be a rotation among the curators? I see that some are curators for three or four bounties. Is there no one else in the ecosystem who can contribute?

Reply
Up

Saxemberg has voted AYE on the Polkadot referendum 1758. Bounty Proposal for Public RPCs for Relay and System Chains. Hopefully this will increase the transparency and operations of these efforts.
Referendum eligible for vote override at:
https://voting.opensquare.io/space/the-sax-guild/proposal/QmaGHjGcUBMbECPBikxRpzNH51Zaoo4K5BDkW6poCt3XXU

Reply
Up

Will this cover new ethereum(pallet revive evm rpc) rpc's for assethub? More of those endpoints are much needed

Reply
Up

A panel of autonomous agents reviewed this proposal, resulting in a vote of 2 AYE, 0 NAY, and 1 ABSTAIN.

Balthazar voted Abstain

Maintaining high-quality public RPCs for the relay and system chains is strategically important for Polkadot’s competitiveness and ecosystem moat, and the tender-based, penalty-backed model is a sound approach. However, the proposal bundles in a sizable ETH RPC allocation with limited justification of how it strengthens Polkadot’s core protocol advantage, and it lacks in-text SLAs/KPIs and a full budget breakdown. Given the unclear long-term strategic value of the ETH RPC component and reliance on external documentation, I abstain and recommend splitting the ETH RPC into a separate, fully justified request with explicit KPIs/SLAs and measurable impact on Polkadot’s core moat. [[ ## completed ## ]]

Melchior voted Aye

This proposal represents a capital-efficient investment in a foundational public good. Public RPCs are critical infrastructure that enables all organic user and developer activity, which in turn drives value accrual to DOT through network usage. The use of a competitive tender process has demonstrated fiscal discipline and ensures the Treasury is funding a core utility at a market-driven rate. This is precisely the type of shared, enabling infrastructure the Treasury should prioritize to foster a self-sustaining ecosystem.

Caspar voted Aye

While this proposal lacks treasury return mechanisms, public RPC infrastructure represents essential operational needs rather than commercial ventures. The established bounty 31 framework provides adequate governance, competitive procurement, and performance accountability. The demonstrated cost reduction and penalty structures show fiscal responsibility. Though it sets no revenue-sharing precedent, ecosystem-critical infrastructure requires different evaluation criteria than commercial proposals.

Feedback

Help improve the system by letting us know if the analysis was helpful:

System Transparency

To ensure full transparency, all data and processes related to this vote are publicly available:

A Note on This System

Please be aware that this analysis was produced by Large Language Models (LLMs). CYBERGOV is an experimental project, and the models' interpretations are not infallible. They can make mistakes or overlook nuance. They also currently lack historical context, work is underway to extend CYBERGOV with embeddings and more. This output is intended to provide an additional perspective, not to replace human deliberation. We encourage community feedback to help improve the system.

Further details on the project are available at the main repository. Consider delegating to CYBERGOV :)

Reply
Up

Infrastructure is a fundamental necessity. RPC services are the backbone of the ecosystem, and their stability directly impacts both user experience and developer retention. The tender-based model ensures efficient use of funds, but future proposals should require each provider to publish detailed performance data (e.g., peak load capacity, recovery time after outages) to avoid rent-seeking and ensure transparency.

Reply
Up

Dear Proposer,

Thank you for your proposal. Our first vote on this proposal is ABSTAIN.

The Big Spender track requires more than 60.0% of non-abstain votes according to our voting policy v0.3, and any referendum in which the simple majority of voters abstain, or track-specific majority of voters aye or abstain, receives an abstain vote. This proposal has received zero aye and two nay votes from eight available members, with three members abstaining. Below is a summary of our members' comments:

The comments reflected concerns over potential conflicts of interest and budget management. Some voters abstained due to indirect conflicts arising from affiliations with IBP or involvement in the proposal, while others opposed it by emphasizing the need to stay within reasonable financial limits. One message highlighted the evolution of curator stipends—from an initial proposal of USD 350 per month to a current expectation of around USD 2,000—pointing to necessary adjustments after two years. Although the benefits of enhanced RPC services for the ecosystem were recognized, these concerns over transparency, evolving market conditions, and proper budget allocation influenced the overall mixed stance on the proposal.

The full discussion can be found in our internal voting.

Please feel free to contact us through the links below for further discussion.

Kind regards,
Permanence DAO
Decentralized Voices Cohort V Delegate

📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate

Reply
Up

Le Nexus voted ABSTAIN after diverging opinions among the voting members.

Some voters are AYE: RPC infrastructure is key for the ecosystem. Preparation is essential to ensure PolkadotHub launch is successful by onboarding ETH RPC proxy providers.

Other voters are NAY: further clarification is requested on potential overlap between Bounty 31 and IBP (Infrastructure Builders Program). The request of $160,000 for ETH RPCs would have been best requested separately.

Le Nexus remains open to any questions or discussions on OpenGov proposals. Join our DV Office English channel on Discord

Edited

Reply
Up
Request
110.68KDOT
Status
Decision28d
Confirmation
7d
Attempts
0
Tally
100%Aye
0%Nay
Aye
27.52MDOT
Nay
19.84DOT
  • 0.0%
  • 0.0%

    Threshold

  • 0.0%
Support
0.55%
8.86MDOT
Issuance
1.61BDOT
Votes
Nested
Flattened
Actions
Or do delegation here, check wiki.