Withdraw ₳243,478 for MLabs Core Tool Maintenance & Enhancement: Plutarch
164 DReps voted · 52 with a rationale · 2 changed their vote
Open a row to read the rationale.
- Yes46.5K ₳Rationale
- with the condition, Mlabs should not resubmit redundancy at the Catalyst
I voted YES on all 39 Governance Actions — 39 times, 39 votes.
Since I supported these during Ekklesia and saw no major changes or conflicts of interest, I stand by those decisions now. For proposals with large budgets, I paid extra attention to the justification and scope. Voting isn’t just a click — it’s a responsibility. I own mine, for myself and for our CASIA community.
- Yes45.2K ₳No rationale
- Yes36.3K ₳No rationale
- Yes36.3K ₳Rationale
✅ Voted YES on: MLabs – Plutarch Maintenance & Enhancements
Summary:
Plutarch is a production-grade Haskell eDSL used to write smart contracts on Cardano. It’s critical tooling that underpins many ecosystem projects and requires active maintenance to remain compatible with future hardforks and user needs.Why I voted YES:
• 🧰 Core infrastructure: Widely adopted by Cardano developers for smart contract development
• 🔧 Maintains developer productivity: Bug fixes, upgrades, and new features improve ecosystem health
• ⚙️ Future-proofing: Ensures compatibility with upcoming protocol changes
• 🧠 Led by MLabs: A trusted contributor with deep Cardano experience and a track record of deliveryReliable tooling like Plutarch is essential for long-term innovation in Cardano’s smart contract ecosystem.
🗳️ DRep: DeepStatecraft
🔗 View Proposal - Yes26.7K ₳Rationale
MLabs has proven to use their funds responsibly and they have been closing out their Catalyst proposals. https://projectcatalyst.io/proposers/lpmaho
- No14.3K ₳No rationale
- Yes6.7K ₳No rationale
- Yes4.8K ₳No rationale
- Yes335.3 ₳No rationale
- Yes13.5 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale