Cardano GovTool Budget - 12 months full active maintenance and development
220 DReps voted · 64 with a rationale · 18 changed their vote
Open a row to read the rationale.
- Yes1.7M ₳No rationale
- Yes1.6M ₳No rationale
- No1.6M ₳No rationale
- Yes1.5M ₳Rationale
GovTool is Cardano’s primary governance interface, critical for CIP-1694 and Voltaire. This would ensures accessible governance, supports DReps, users...
- No1.4M ₳No rationale
- Yes1.4M ₳No rationale
- YesRevoted1.4M ₳Rationale
I vote YES on this Info Action because GovTool is essential infrastructure for Cardano’s decentralized governance. It enables ADA holders to participate in governance actions—registering, delegating, proposing, and voting
Maintaining and improving GovTool is critical for inclusive, accessible, and decentralized governance. Supporting this proposal means investing in the foundation that makes Cardano governance work—for everyone.
Earlier votes
Yes11mo agoSuperseded
- Yes1.3M ₳No rationale
- Yes1.3M ₳No rationale
- Yes1.2M ₳No rationale
- No1.2M ₳Rationale
Rationale for voting No to Cardano GovTool Budget - 12 months full active maintenance and development
Past Performance
Govtool's past performance does not justify renewed funding. While the team has responded to community feedback, the changes are not clear or proportionate to the size of the request.Insufficient Cost Transparency
The requested budget, particularly for node and indexer operations, seems high without a clear and detailed breakdown. More financial clarity is needed to assess value for money.Unclear Funding Channels
As a platform developed under Intersect, GovTool should be financed through Intersect’s Treasury budget, not a seperate Treasury Withdrawal.Low Adoption and Preference
GovTool is not the voting interface for many in the community. Funding should follow demonstrated usage and demand—not precede it. Other options replacing govtool look attractive.
- No1.2M ₳No rationale
- Yes1.1M ₳No rationale
- No1.1M ₳Rationale
From a strategic governance perspective, this proposal to continue funding GovTool’s active development and maintenance raises significant concerns regarding the fragmentation and duplication of governance infrastructure within the Cardano ecosystem. While GovTool undeniably plays a critical role as an open-source, community-owned interface facilitating on-chain governance participation, the coexistence and overlap with other platforms—most notably tempo.vote—cannot be ignored. This parallelism risks diluting user engagement, confusing stakeholders, and ultimately weakening the unified governance experience that Cardano must strive to deliver.
The proposal’s emphasis on GovTool’s modularity, open APIs, and broad ecosystem integration is commendable; however, it insufficiently addresses the strategic imperative of consolidation. The Treasury resources allocated here—up to ₳1.15M annually—represent a substantial investment that must be justified by demonstrable efficiency gains and a clear roadmap toward interoperability or unification with other governance tools. The absence of explicit plans to harmonize GovTool with tempo.vote or to rationalize overlapping functionalities leaves the community vulnerable to redundant expenditures and operational inefficiencies.
Cardano’s governance strength lies not only in decentralization but in coherence and scalability. Supporting multiple competing governance frontends fragments the community’s attention and complicates the user journey, undermining the inclusivity and accessibility that Voltaire envisions. It is imperative that the Governance Tools Working Group and the GovTool Consortium prioritize strategic alignment with existing platforms, fostering interoperability standards or even converging development efforts to create a singular, robust, and user-friendly governance interface.
Moreover, from a business-minded stewardship standpoint, we must scrutinize the proposal’s tiered funding structure and ensure that every tranche of expenditure directly contributes to sustainable and scalable governance outcomes. While the modular approach and community feedback integration are positive steps, they do not substitute for a comprehensive strategic framework that safeguards the Treasury and maximizes long-term value for Ada holders.
In advancing Cardano’s governance infrastructure, we must reject proliferation in favor of strategic consolidation. The future stability of the protocol and the vitality of its community participation depend on decisive, coordinated action to unify governance tools. Therefore, I support funding GovTool only on the condition that the proposal includes a binding, transparent roadmap for integration or harmonization with tempo.vote and other governance platforms. This is non-negotiable if we are to preserve Treasury resources, enhance user experience, and uphold Cardano’s scientific and decentralized governance ethos.
I firmly believe that governance tools must empower and unify, not divide, our community. It is time for us, as stewards of Cardano’s future, to make strategic choices that protect our treasury and build a truly scalable, coherent governance ecosystem—one platform, one vision, one Cardano.
- Yes1M ₳No rationale
- Yes971.5K ₳No rationale
- Yes964.1K ₳No rationale
- Yes949.1K ₳No rationale
- Yes948.9K ₳No rationale
- Yes931.8K ₳No rationale
- Yes881.2K ₳No rationale
- Yes861.5K ₳No rationale
- Yes825.2K ₳Rationale
This proposal has our full support. GovTool is an indispensable public good for the Cardano ecosystem, crucial for fostering accessible and fair governance for every participant. Unlike commercial ventures, GovTool is an open-source, community-built platform, designed to be reused and expanded upon by the community. While this collaborative development demands more time and coordination, it is unequivocally the right approach for a decentralized ecosystem like Cardano.
The proposal provides a meticulous breakdown of costs for 12 months of work across all environments (Dev, QA, Preview, PreProd, Mainnet), clearly explaining fund allocation and offering historical cost data for complete transparency. This funding is vital to ensure GovTool remains a stable, community-owned hub for participation. Furthermore, the commitment to return any unused funds to the treasury demonstrates exceptional fiscal responsibility. For these compelling reasons, we consider this a fair and absolutely necessary proposal that significantly strengthens Cardano's ability to govern itself.
- Yes820.1K ₳No rationale
- Yes798.6K ₳Rationale
While there are other tools out there, this is an investment in continued innovation for governance infrastructure. Supporting diverse approaches strengthens the whole ecosystem.
- Yes798.4K ₳No rationale
- Yes763.4K ₳No rationale
- Yes763.4K ₳No rationale
- No756.5K ₳No rationale
- No731.5K ₳No rationale
- Yes717.5K ₳No rationale
- Yes707.1K ₳Rationale
We, the Dutch DRep, vote YES on the Govtool budget proposal by the Govtool consortium.
Transparency Disclosure: One of our Dutch DReps represents Dquadrant, a Govtool consortium member, in community forums. While this relationship informs our understanding, we believe the proposal stands on its own merits and advances Cardano’s governance goals.
The Govtool consortium—coordinated through Intersect and backed by trusted community teams—has a proven track record of delivering accessible, constitutionally sound governance tools since CIP‑1694. Their proposal is transparent, well‑structured, and firmly rooted in Cardano’s principles of accountability and community‑driven decision‑making.
Govtool’s planned enhancements will:
Guarantee open access for all ADA holders, lowering barriers to participation.
Foster community ownership through open‑source code and public APIs, enabling developers to build complementary governance solutions.
Support a distributed development model by funding multiple teams and encouraging community contributions.
Ensure the roadmap remains responsive to ADA holders’ needs via transparent, community‑driven prioritization.
Together, these improvements will strengthen Cardano’s decentralized governance, boost transparency and efficiency, and align with our long‑term vision of inclusivity and innovation.
- Yes705.1K ₳No rationale
- Yes655.6K ₳No rationale
- Yes652.3K ₳No rationale
- Yes625.9K ₳No rationale
- Yes605.7K ₳No rationale
- Yes598.3K ₳No rationale
- Yes590.5K ₳No rationale
- Yes589.7K ₳No rationale
- No587.6K ₳No rationale
- Yes559.2K ₳No rationale
- Yes478.3K ₳No rationale
- Yes466.2K ₳No rationale
- No450.2K ₳Rationale
GovTool is essential for DRep onboarding and CIP-1694, but its request, 1.5 M ADA for a single year of maintenance and incremental UX work, far exceeds what I consider reasonable at this stage.
After already approving ~280 M ADA of this year’s 300 M ADA NCL, I believe tighter fiscal discipline is critical. To signal the need for a leaner, better-justified budget, I will vote NO on this proposal and encourage a scaled-down resubmission.
- Yes431.7K ₳No rationale
- Yes409.7K ₳No rationale
- Yes390K ₳No rationale
- No385.2K ₳No rationale
- Yes383K ₳No rationale