Withdraw ₳243,478 for MLabs Core Tool Maintenance & Enhancement: Plutarch
This treasury withdrawal funds **MLabs** **Core Tool Maintenance & Enhancement: Plutarch** which will provide the following services: This proposal seeks funding for the ongoing annual maintenance and feature enhancement of Plutarch, a production-grade eDSL in Haskell for creating Cardano smart contracts. As a core tool widely adopted within the ecosystem, Plutarch requires consistent upkeep. Funding covers maintenance (bug fixes, compatibility updates for hardforks) and new feature implementation based on community needs (e.g., via GitHub issues). This ensures Plutarch remains resilient, powerful, and up-to-date, supporting developers and the ecosystem. This Treasury Withdrawal is submitted by Intersect on behalf of the vendor. The following sections; Abstract, Motivation, Rationale and Vendor Profile have been sourced from the approved proposal submitted by the Vendor as part of the Intersect budget process. This treasury withdrawal funds one of 39 proposals to give effect to the approved budget info action for ₳275,269,340, administered by Intersect via gov_action1u9x73kwufaxa70lfy59g4ynwyrcsaxdcd0gxzzmh67s9fxq4j8hqqk2phgh. The information provided herein is intended to fulfill the spirit of the constitutional requirement for a treasury withdrawal info action by also providing the details of the proposed solution, alignment to the budget, and amount to be withdrawn from the Cardano Treasury.
Reasoning
Written after the vote was cast
What this asks for, and from whom
243,478 ADA for MLabs core tool maintenance and enhancement.
What would have to be true for this to be a good use of treasury funds
Plutarch and the surrounding tooling are used by dozens of teams building production smart contracts. Tooling that must track protocol evolution is exactly what maintenance funding is for.
What specifically concerns me
This was part of the 2025 Intersect budget slate, which I voted as a slate. I am saying that plainly rather than pretending each line got its own week of deliberation. The slate came through a community budget process with a support threshold before it ever reached the chain, and my judgment was that the process outcome deserved backing in Cardano's first real treasury cycle. Nothing specific. I have voted yes on MLabs maintenance repeatedly across cycles because the dependency is real and the asks stay proportionate.
What I am asking of the proposer if this passes
It was enacted. Keep publishing the benchmarks and the dependent team count. Those two numbers make every renewal a short conversation.