Fundation Rapid dApp Creation Lvl One: Let the Fun Begin

Rejected
Content
AI Summary
Reply
Up
Share
Request
15,000USDC
7,653DOT
Status
Decision28d
Confirmation
2d
Attempts
0
Tally
2.9%Aye
50.0%Threshold
97.1%Nay
Aye
766KDOT
Nay
25.57MDOT
  • 0.0%
  • 0.0%

    Threshold

  • 0.0%
Support
0.02%
257.42KDOT
Issuance
1.6BDOT
Votes
Nested
Flattened
Actions
Check how referenda works here.
Call
Metadata
Timeline4
Votes Bubble
Curves
Statistics
Comments

Saxemberg has ABSTAINED on the Polkadot referendum 1716 Fundation Rapid dApp Creation Lvl One: Let the Fun Begin. Scaffolds and tooling are some of the things developers require. Unfortunately, this ref didn't pass the approval threshold.

Reply
Up

Dear Proposer,

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

The Small Spender track requires 50% participation and simple majority of non-abstain votes according to our voting policy v0.2, and any referendum in which the majority of members vote abstain receives an abstain vote. This proposal has received zero aye and four nay votes from eight available members. Below is a summary of our members' comments:

The voters expressed concerns about the proposal’s lack of detail and clarity, noting that it failed to provide sufficient information about the proposer, a concrete roadmap, or even a basic working prototype. They observed that while the idea of a tool to simplify dApp creation held potential, the submission did not adhere to a standard proposal template and omitted key aspects needed to assess its feasibility. The submissions were deemed vague in presentation and delivery, with critics suggesting that more comprehensive details and evidence of prior experience should have accompanied the request for funding.

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 IV Delegate

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

Reply
Up

Although I’m voting NAY, I appreciate the focus on making it easier for Web2 devs to build on Polkadot. A lot of this overlaps with work already underway in the UX Bounty (UXB-7), where we’re creating a shared component library with chain-aware UI (address inputs, tx buttons, etc.) and standardizing best practices.

I recommend checking out the UXB work outlined here. You can also see a preview of the new Polkadot UI library at https://polkadot-ui.com/.

It might make more sense to contribute there rather than starting a separate framework. The more we align and pool efforts, the stronger and more sustainable the tooling will be for the ecosystem.

Reply
Up

Sorry for the delay in my rationale. While the idea shows potential, the proposal is premature for Treasury funding at this stage, as it lacks adoption, validation, and concrete evidence of demand within the Polkadot ecosystem. If the team first focuses on building, testing, and demonstrating the real necessity and usefulness of the framework, and then resubmits the request, I could consider supporting it.

Reply
Up

@swenthebuilder We respect your vision and the passion you bring to building tools for Polkadot. Making the ecosystem more accessible for Web2 developers is a goal we fully share.

Our vote is not against your idea, but against funding it at this stage without stronger proof of adoption and continuity. At this point, without developer traction or clear validation, it is too early for us to justify spending public funds.

We encourage you to keep building, gather feedback from other developers, and connect with ongoing UX efforts. With a working proof of concept and community validation, we believe a future proposal could gain much stronger support.

A friendly word of advice:

OpenGov also has its own “codes” To maximize your chances, it’s important to work in three phases:

  • Before going on-chain: share your idea on the forum, discuss it on Discord/Telegram and reach out to DV for early feedback.
  • During the proposal: defend it publicly with clear threads and summaries, answer questions on Subsquare/Polkassembly, re-engage with the DVs and seek visibility through AAG.
  • After the vote: publish a post-mortem, whether you win or lose, this shows commitment and builds credibility for future proposals.

This is not a no to your vision, but a not yet. We’ve seen many solo-dev proposals struggle at this stage, so taking the time to build allies and early validation will make all the difference next time.

Le Nexus invites you to join our DV Office English channel on Discord to engage in conversation about OpenGov proposals.

Reply
Up

MJ here representing PBA Alumni Voting DAO.

Our voters chose NAY, as we believe it would be beneficial for the project to first pursue a W3F grant. This path provides valuable guidance and support which can help strengthen the proposal and team's credibility before approaching the treasury.

For further enquiries, please reply here or contact alumni@polkadot.academy.

Reply
Up
Request
15,000USDC
7,653DOT
Status
Decision28d
Confirmation
2d
Attempts
0
Tally
2.9%Aye
50.0%Threshold
97.1%Nay
Aye
766KDOT
Nay
25.57MDOT
  • 0.0%
  • 0.0%

    Threshold

  • 0.0%
Support
0.02%
257.42KDOT
Issuance
1.6BDOT
Votes
Nested
Flattened
Actions
Check how referenda works here.