Withdraw 1,162,746 ada for MLabs Core Tool Maintenance & Enhancement: Plutarc...
143 DReps voted · 48 with a rationale · 3 changed their vote
Open a row to read the rationale.
- Yes8.1M ₳No rationale
- Abstain7.4M ₳Rationale
ABSTAIN
I am not fully convinced this is absolutely necessary, so I will abstain from voting.
- Yes7.2M ₳No rationale
- Yes5.9M ₳Rationale
Consistent with my 2026 Intersect budget process votes, I am voting YES. This is part of the bulk proposals submitted by Intersect from that process.
Hydra Evidence IPFS: https://bafybeie6yykngvn5xsq6va6nwz3sdeadgxd45yhsoeqpuiyxh4tky5tuzi.ipfs.inbrowser.link/
X-Post: https://x.com/mr_cata/status/2063660464450527709?s=20 - Yes5.4M ₳No rationale
- Yes5.4M ₳No rationale
- Yes4.8M ₳No rationale
- Yes4.6M ₳No rationale
- Yes4.4M ₳No rationale
- Yes4.1M ₳Rationale
[Portuguese]
Optamos por votar "SIM" nesta ação de governança "Withdraw 1,162,746 ADA for MLabs Core Tool Maintenance & Enhancement: Plutarch and Ply" (gov_action1k02...fsvefn), pois entendemos que a proposta financia a continuidade e a evolução de ferramentas essenciais para o desenvolvimento de contratos inteligentes na Cardano. A manutenção do Plutarch e do Ply contribui para reduzir riscos de incompatibilidade, evitar falhas decorrentes da evolução do protocolo e minimizar custos de migração para equipes e projetos que já dependem dessas soluções. O valor solicitado, de ₳1.162.746, nos parece proporcional ao escopo das atividades previstas e apresenta uma boa relação custo-benefício diante da importância dessas ferramentas para desenvolvedores e para o ecossistema como um todo. Ao garantir a manutenção contínua e a evolução dessas bibliotecas, a proposta fortalece a infraestrutura de desenvolvimento da Cardano e contribui para a criação de aplicações mais seguras e eficientes. Também avaliamos positivamente os mecanismos de governança, controle e transparência previstos na proposta, incluindo desembolsos condicionados ao cumprimento de marcos, obrigações periódicas de prestação de contas, supervisão independente e acompanhamento público da execução por meio de contratos inteligentes e painel on-chain. Esses mecanismos aumentam a rastreabilidade da utilização dos recursos da Tesouraria e permitem que a comunidade acompanhe a evolução das entregas de forma transparente.
[English]
We chose to vote "YES" on this governance action "Withdraw 1,162,746 ADA for MLabs Core Tool Maintenance & Enhancement: Plutarch and Ply" (gov_action1k02...fsvefn), because we believe the proposal funds the continued maintenance and enhancement of essential tools for smart contract development on Cardano. Ongoing support for Plutarch and Ply helps reduce compatibility risks, prevent issues arising from protocol evolution, and minimize costly migrations for development teams and projects that already rely on these technologies. The requested ₳1,162,746 appears proportionate to the proposed scope of work and represents good value considering the importance of these tools to developers and the broader Cardano ecosystem. By ensuring their continued maintenance and improvement, the proposal strengthens Cardano’s development infrastructure and supports the creation of more secure and efficient decentralized applications. We also view the proposal’s governance, oversight, and transparency mechanisms positively. These include milestone-based disbursements, regular accountability reporting, independent supervision, and public on-chain monitoring through smart contracts and a public dashboard. Together, these measures improve transparency, strengthen accountability, and enable the community to verify how Treasury resources are being used throughout the project. - Yes4M ₳No rationale
- Yes3.8M ₳Rationale
I see this as a administrative vote which is to process a withdrawal that DRep's have previously approved. I do not believe in throwing monkey-wrenches into approved and planned for processes, and thus I vote yes so as not to obstruct progress and momentum, and to not undermine previous decisions.
- Yes3.6M ₳No rationale
- Yes2.9M ₳No rationale
- Yes2.8M ₳No rationale
- Yes2.8M ₳No rationale
- Yes2.7M ₳No rationale
- Yes2.6M ₳No rationale
- Yes2.6M ₳Rationale
私は本Treasury Withdrawalに 賛成します。
理由は、Plutarch / PlyがCardanoのスマートコントラクト開発者向けの重要なOSS toolingであり、既存dAppや開発チームの保守・互換性・安全性に直接関わるからです。CIP-57 blueprint対応やUPLC効率性は、on-chain/off-chain境界の信頼性、開発者体験、監査容易性にもつながります。
また、Intersect管理、TRSC/PSSC、oversight committee、dashboardを用いたSmart Contract Disbursement設計がある点は、Treasury資金管理として評価できます。--
I support this Treasury Withdrawal.
Plutarch and Ply are important open-source tools for Cardano smart contract developers. They directly support the maintenance, compatibility, and safety of existing dApps and development teams.
Their support for CIP-57 blueprints and efficient UPLC generation also improves the reliability of the on-chain/off-chain boundary, developer experience, and auditability.
I also value the funding management design, including Intersect administration, TRSC/PSSC smart contracts, oversight committee involvement, and a public dashboard. These elements make this proposal stronger from a Treasury fund management perspective.
- Abstain2.5M ₳No rationale
- Yes2.5M ₳Rationale
Due to rationales becoming stressful and the bear market vibes - I will not be providing rationale. I voted the way that I did bc we need a 'no stress' environment more than ever.
- Yes2.3M ₳No rationale
- Yes2.2M ₳No rationale
- Yes2.1M ₳Rationale
If there were full descriptions instead of excerpts only here, the treasury governace process would be less cumbersome.
Plutarch and Ply are mature, open-source development tools with demonstrated adoption, so "Yes".
- Yes2.1M ₳No rationale
- Yes2.1M ₳Rationale
I am voting YES on the MLabs Core Tool Maintenance & Enhancement: Plutarch and Ply proposal.
Plutarch and Ply are important developer tools for Cardano smart contract development. They help teams write, compile, serialize, test and maintain production on-chain applications, with Plutarch supporting efficient smart contract development through compilation to UPLC, and Ply helping bridge scripts into blueprint-style artifacts.
In the current NCL environment, I believe DReps need to be selective. My priority is to support proposals that maintain essential public goods, developer infrastructure, security-critical tooling and the core rails that allow Cardano builders to keep building.
This proposal fits that framework.
It is not a broad speculative growth proposal. It is a focused maintenance and enhancement request for tooling already used by Cardano builders. The work prioritises critical breakages, serious vulnerabilities, protocol-era and hard-fork compatibility, bug fixes, correctness improvements, optimisations, documentation and developer-experience improvements.
I also view it positively that the proposal discloses prior treasury funding, sets out a clear budget, includes Intersect administration, provides for oversight and milestone-based disbursement controls, and is structured through the 2026 treasury management smart contract framework.
The requested amount is material, but proportionate when compared with larger and more speculative treasury asks currently competing for limited NCL capacity. Cardano needs to preserve and maintain the tooling that production teams rely on, especially as Plutus, UPLC and ledger-era changes continue to evolve.
For these reasons, I consider this a responsible use of treasury funds and a good example of the type of developer infrastructure maintenance the treasury should support.
I vote YES.
- Yes1.9M ₳No rationale
- Yes1.8M ₳Rationale
Plutarch and Ply are used by Cardano builders, it is important to maintain them.
- Yes1.8M ₳No rationale
- Yes1.7M ₳No rationale
- Yes1.6M ₳No rationale
- No1.5M ₳No rationale
- Yes1.3M ₳No rationale
- No1.2M ₳No rationale
- Yes1.2M ₳Rationale
I vote YES on "MLabs Core Tool Maintenance & Enhancement: Plutarch and Ply" because Cardano needs well-maintained tools for people building smart contracts. Plutarch and Ply are not user-facing apps, but if tools like these fall behind, builders can face broken code, extra migration work, or higher costs when Cardano changes. I also want Cardano to keep supporting several serious smart-contract toolchains, including Aiken, so developers have strong options instead of a single path. My support is not a blank cheque: future requests should explain usage, deliverables, costs, and the 15-team versus 26-team adoption claim more clearly.
- No1.2M ₳No rationale
- Abstain1.1M ₳No rationale
- Yes1.1M ₳No rationale
- No1.1M ₳Rationale
₳1.2M for maintaining Plutarch and Ply is a hefty amount to request without clear KPIs to back it up. Just saying “15 teams use these tools” doesn’t cut it.
I need solid data showing how this usage translates into real value for Cardano, like revenue growth, increased user adoption, or meaningful expansion of the ecosystem. From my experience, maintenance alone rarely justifies this level of funding unless it clearly prevents major setbacks or drives significant growth. What’s the trend in adoption? Are these tools becoming more relevant, or are they just sitting still or even declining? Without clear metrics and proof that these investments provide value to the treasury, it feels more like costly upkeep instead of a strategic move. The proposal needs to demonstrate that this spending not only keeps Cardano going but also enhances its network effects and developer engagement. Without that, I can’t support such a big request solely for maintenance.
- Yes1M ₳No rationale
- Yes988.7K ₳Rationale
We vote YES on this proposal because maintaining proven developer tooling is important for the long-term health of the Cardano application ecosystem. Plutarch and Ply are not speculative new tools. They are existing open-source components used by Cardano builders to write, compile, serialize and maintain efficient smart contracts. If tools like these fall behind protocol upgrades, Plutus changes, or future hard forks, teams building production applications may face avoidable friction, migration costs, or technical risk.
We also appreciate the focused scope of this proposal. The funding is directed toward maintenance, compatibility, bug fixes, optimizations, documentation and developer-experience improvements rather than a broad or unclear new initiative. While the tooling is more specialized than some other ecosystem infrastructure, it supports real builders and contributes to Cardano’s smart contract reliability. For that reason, we believe this is a reasonable investment into the developer layer of the ecosystem.
- Yes988.4K ₳No rationale
- Yes964.5K ₳No rationale
- Yes924.2K ₳No rationale
- Yes881.9K ₳No rationale
- Yes870.4K ₳No rationale
- Yes830.3K ₳Rationale
We support Intersect's budget process. This proposal is part of it.
- Yes799.1K ₳No rationale
- Yes795K ₳No rationale
- Yes626K ₳Rationale
Voting YES. Plutarch and Ply are open-source Cardano smart contract tools in active use by 26+ teams. MLabs is a proven maintainer with transparent prior funding. ₳1.16M for annual maintenance is proportionate. Transparency gaps are real but not blocking.
A PDF version of this rationale is also made available.
This proposal funds maintenance of Plutarch (Haskell eDSL for efficient Cardano smart contracts) and Ply (serialization library for Plutarch scripts with CIP-57 blueprint support). These are established, open-source developer tools used by at least 26 teams building on Cardano.
The ask is modest at ₳1.16M for annual maintenance, from a proven maintainer with transparent prior funding history. The value proposition is clear: without ongoing compatibility work, teams building on Plutarch face expensive migrations, rewrites, and friction as Cardano's ledger and Plutus/UPLC evolve.
I have the same transparency concerns I flag in every Intersect-administered proposal: thin budget detail, no ADA volatility policy, and milestones not visible in the public metadata. But at this scale, roughly $290K but, those concerns are proportionate, not blocking. This is exactly the kind of open-source tooling maintenance the Treasury should fund.
Plutarch and Ply are real, open-source tools with proven adoption across the Cardano ecosystem. MLabs has maintained them through multiple protocol eras with transparent prior funding and demonstrated delivery. The ask ₳1.16M for annual maintenance is proportionate to the value at stake.
The transparency gaps I note (budget detail, ADA volatility policy, milestone visibility) are real but manageable at this scale. They are patterns across Intersect-administered proposals, not flaws unique to this one. I will continue to flag them, but I will not let them block well-justified, modest asks from proven maintainers.
This is the kind of proposal the Treasury should fund: established public infrastructure, proven team, clear additionality, and a reasonable price.