Withdraw ₳45,217 for MLabs Core Tool Maintenance & Enhancement: Cardano.nix
214 DReps voted · 61 with a rationale · 18 changed their vote
Open a row to read the rationale.
- Yes298.9K ₳Rationale
I'm defaulting to voting yes because there is some degree of consensus already achieved on each of these. So unless I have a significant issue with one of these proposals I will be voting yes on it.
- Yes271.8K ₳No rationale
- Yes270.1K ₳Rationale
I voted YES on the Treasury Withdrawal titled "MLabs Core Tool Maintenance & Enhancement: Cardano.nix" (₳45,217) after reviewing all submitted materials.
The Administrator is clearly named and this proposal is governed by a milestone-based off-chain contract with Cardano Development Holdings, including independent milestone review, 3rd-party assurance, and transparent delivery schedules. Disbursements are executed through a thoroughly audited smart contract system that prevents unilateral control and ensures community oversight.
The proposal itself delivers critical maintenance for the Cardano.nix deployment framework, a widely-used open-source tool for reproducible infrastructure builds across the Cardano ecosystem. Cardano.nix underpins deployment pipelines used by both community and IOG/Daedalus node operators, and this funding ensures consistent upgrades, bug fixes, and developer experience improvements.
MLabs is an experienced and trusted vendor with a proven track record. The requested amount is proportional to the scope and essential to maintaining infrastructure readiness in Cardano’s growth and governance phase.
For these reasons, I support this Treasury Withdrawal and recommend affirmative votes from all DReps committed to Cardano’s stability, open tooling, and infrastructure maturity.
- Yes262.6K ₳No rationale
- AbstainChanged261K ₳Rationale
🗳 Governance Action Review
Proposal: Withdraw ₳45,217 for MLabs Core Tool Maintenance & Enhancement: Cardano.nix
Vendor: MLabs LTD (administered by Intersect)
Governance Action ID: gov_action18nefry4qacd80xzs2srjahxm2e4vz3c8wvrr03rrtk8mdqfuknysq66459t
Submitted: 16 July 2025
Expires: 17 August 2025
Type: Treasury Withdrawal
Budget Requested: ₳45,217
📋 Evaluation Checklist
1️⃣ Ecosystem Essentiality → ✅ Yes
“Cardano.nix provides foundational toolsets for building and deploying Cardano infrastructure reproducibly using Nix.”
“Known adopters include: Input Output Global (IOG), Daedalus Wallet (IOHK), Kwarxs.”Analysis:
Cardano.nix is already in use by key ecosystem teams. Its role as a reproducible deployment framework directly supports infrastructure reliability, onboarding, and maintenance. This is a foundational, not peripheral, component.
2️⃣ Budget Structure and Detail → 🟡 Partial
“Estimated 260 hours total effort over 12 months. Developer Effort (Maintenance – 160 hrs): approx. $19.2k; Developer Effort (Enhancements – 100 hrs): approx. $12k; Project Management / QA Overhead: 10% or $3.1k.”Analysis:
The budget provides a breakdown by work category and estimates a total of 260 hours. However, the effective hourly rate is $120/hour, which is on the high end even for senior-level technical contractors in open-source maintenance.There is no justification provided for this rate, nor clarification on whether it includes embedded costs such as tooling, testing infrastructure, or indirect expenses. While the effort estimation appears internally consistent, the lack of transparency in rate composition weakens budget accountability.
In future proposals, a breakdown of cost components — e.g., developer base rate, overhead assumptions, or included indirect costs — would support better evaluation of reasonableness and comparability.
3️⃣ KPIs or Impact Identifiers → ❌ No
📌 “Please list any key dependencies (if any) for this proposal?”
📌 “What tangible milestones or outcomes are to be delivered and what will the community ultimately receive?”Analysis:
The proposal outlines deliverables such as updates, bug fixes, and minor enhancements, but does not define any quantitative KPIs, success metrics, or impact benchmarks. No targets for frequency of updates, turnaround time, adoption, usage, or efficiency gains are presented.
This is a missed opportunity, especially for a tool with wide ecosystem usage. Even minimal indicators — such as number of node versions supported, update response time, or integration reach — would enhance transparency.
4️⃣ Milestones and Deliverables → ❌ No
📌 “Duration Estimate: 12 months”
📌 “Maintenance Deliverables: Regular updates ensuring compatibility… DoD: Updates merged and tested…”
📌 “Enhancement Deliverables: … within the scope of 100 hours… DoD: Enhancement code merged, tested, documented…”
📌 “All milestones, acceptance criteria, payment amounts and expected delivery dates will be agreed between the Vendor and Intersect... within the Legal Contract.”Analysis:
Although some technical deliverables are mentioned, there is no publicly verifiable project timeline, no milestone schedule, and no disclosure of acceptance checkpoints. The reliance on private legal contracting with Intersect to define key aspects of delivery significantly limits transparency and public accountability.
5️⃣ Internal Consistency → ✅ Yes
ADA request: ₳45,217
USD equivalent: $31,200 @ ₳0.69
All fields align.Analysis:
No metadata or budget mismatches were identified.
6️⃣ Team Visibility & Track Record → ✅ Yes
“MLabs LTD is the primary developer and maintainer of Cardano.nix... with deep expertise in Nix, Cardano infra deployment... used by IOG, Daedalus.”
Social handle: @MLabs10Analysis:
The vendor is publicly known, experienced, and trusted. Their contributions to Cardano.nix are well-established and widely adopted across the ecosystem.In addition, MLabs has a strong delivery history within Project Catalyst, having completed 36 proposals and currently managing 8 active projects, with no significant delays reported. This reinforces their credibility and operational reliability across both infrastructure and community-funded domains.
7️⃣ Conflict of Interest → ✅ No Conflict Identified
No material conflicts identified. No financial, employment, or formal affiliation between the evaluator and the vendor.
🧾 Critical Summary
This Governance Action requests ₳45,217 to fund ongoing maintenance of Cardano.nix—a critical infrastructure tool for reproducible builds in the Cardano ecosystem. MLabs is a respected and qualified team, the budget is reasonable and clearly structured, and the technical scope is valid.
However, the proposal suffers from two major transparency gaps:
- It includes no measurable KPIs or performance metrics;
- It presents no public timeline or milestone schedule, relying entirely on private contracting.
- SOme budget items should be better detailed.
These omissions are not minor oversights — they are structural weaknesses that reflect a conscious decision to internalize accountability. As such, the proposal cannot be meaningfully audited or tracked by the community, even though it operates with public funds.
🟨 Voting Recommendation: ABSTAIN
🎯 Rationale:
While the technical significance and vendor credibility support a positive outlook, the lack of ex-ante accountability mechanisms — specifically KPIs, budget breakdown and public delivery timelines — makes this proposal unfit for approval without reservations.
ABSTAIN reflects the recognition of the project’s relevance while upholding a minimum standard of transparency and trackability for public funding.
Earlier votes
Yes11mo agoSuperseded
🗳 Governance Action Review
Proposal: Withdraw ₳45,217 for MLabs Core Tool Maintenance & Enhancement: Cardano.nix
Vendor: MLabs LTD (administered by Intersect)
Governance Action ID: gov_action18nefry4qacd80xzs2srjahxm2e4vz3c8wvrr03rrtk8mdqfuknysq66459t
Submitted: 16 July 2025
Expires: 17 August 2025
Type: Treasury Withdrawal
Budget Requested: ₳45,217
📋 Evaluation Checklist
1️⃣ Ecosystem Essentiality → ✅ Yes
“Cardano.nix provides foundational toolsets for building and deploying Cardano infrastructure reproducibly using Nix.”
“Known adopters include: Input Output Global (IOG), Daedalus Wallet (IOHK), Kwarxs.”Analysis:
Cardano.nix is already in use by key ecosystem teams. Its role as a reproducible deployment framework directly supports infrastructure reliability, onboarding, and maintenance. This is a foundational, not peripheral, component.
2️⃣ Budget Structure and Detail → 🟡 Partial
“Estimated 260 hours total effort over 12 months. Developer Effort (Maintenance – 160 hrs): approx. $19.2k; Developer Effort (Enhancements – 100 hrs): approx. $12k; Project Management / QA Overhead: 10% or $3.1k.”Analysis:
The budget provides a breakdown by work category and estimates a total of 260 hours. However, the effective hourly rate is $120/hour, which is on the high end even for senior-level technical contractors in open-source maintenance.There is no justification provided for this rate, nor clarification on whether it includes embedded costs such as tooling, testing infrastructure, or indirect expenses. While the effort estimation appears internally consistent, the lack of transparency in rate composition weakens budget accountability.
In future proposals, a breakdown of cost components — e.g., developer base rate, overhead assumptions, or included indirect costs — would support better evaluation of reasonableness and comparability.
3️⃣ KPIs or Impact Identifiers → ❌ No
📌 “Please list any key dependencies (if any) for this proposal?”
📌 “What tangible milestones or outcomes are to be delivered and what will the community ultimately receive?”Analysis:
The proposal outlines deliverables such as updates, bug fixes, and minor enhancements, but does not define any quantitative KPIs, success metrics, or impact benchmarks. No targets for frequency of updates, turnaround time, adoption, usage, or efficiency gains are presented.
This is a missed opportunity, especially for a tool with wide ecosystem usage. Even minimal indicators — such as number of node versions supported, update response time, or integration reach — would enhance transparency.
4️⃣ Milestones and Deliverables → ❌ No
📌 “Duration Estimate: 12 months”
📌 “Maintenance Deliverables: Regular updates ensuring compatibility… DoD: Updates merged and tested…”
📌 “Enhancement Deliverables: … within the scope of 100 hours… DoD: Enhancement code merged, tested, documented…”
📌 “All milestones, acceptance criteria, payment amounts and expected delivery dates will be agreed between the Vendor and Intersect... within the Legal Contract.”Analysis:
Although some technical deliverables are mentioned, there is no publicly verifiable project timeline, no milestone schedule, and no disclosure of acceptance checkpoints. The reliance on private legal contracting with Intersect to define key aspects of delivery significantly limits transparency and public accountability.
5️⃣ Internal Consistency → ✅ Yes
ADA request: ₳45,217
USD equivalent: $31,200 @ ₳0.69
All fields align.Analysis:
No metadata or budget mismatches were identified.
6️⃣ Team Visibility & Track Record → ✅ Yes
“MLabs LTD is the primary developer and maintainer of Cardano.nix... with deep expertise in Nix, Cardano infra deployment... used by IOG, Daedalus.”
Social handle: @MLabs10Analysis:
The vendor is publicly known, experienced, and trusted. Their contributions to Cardano.nix are well-established and widely adopted across the ecosystem.In addition, MLabs has a strong delivery history within Project Catalyst, having completed 36 proposals and currently managing 8 active projects, with no significant delays reported. This reinforces their credibility and operational reliability across both infrastructure and community-funded domains.
7️⃣ Conflict of Interest → ✅ No Conflict Identified
No material conflicts identified. No financial, employment, or formal affiliation between the evaluator and the vendor.
🧾 Critical Summary
This Governance Action requests ₳45,217 to fund ongoing maintenance of Cardano.nix—a critical infrastructure tool for reproducible builds in the Cardano ecosystem. MLabs is a respected and qualified team, the budget is reasonable and clearly structured, and the technical scope is valid.
However, the proposal suffers from two major transparency gaps:
- It includes no measurable KPIs or performance metrics;
- It presents no public timeline or milestone schedule, relying entirely on private contracting.
- SOme budget items should be better detailed.
These omissions are not minor oversights — they are structural weaknesses that reflect a conscious decision to internalize accountability. As such, the proposal cannot be meaningfully audited or tracked by the community, even though it operates with public funds.
🟨 Voting Recommendation: ABSTAIN
🎯 Rationale:
While the technical significance and vendor credibility support a positive outlook, the lack of ex-ante accountability mechanisms — specifically KPIs, budget breakdown and public delivery timelines — makes this proposal unfit for approval without reservations.
ABSTAIN reflects the recognition of the project’s relevance while upholding a minimum standard of transparency and trackability for public funding.
Abstain11mo agoSuperseded
- Yes252.9K ₳No rationale
- NoRevoted245.5K ₳History
Earlier votes
No1y agoSuperseded
This should be funded by the Intersect budget and OSC rather than directly from the treasury.
- Yes238.8K ₳Rationale
I plan to vote Yay on the Cardano.nix treasury withdrawal proposal for ₳45,217 because it supports a tool critical for maintaining reliable infrastructure used by key ecosystem components, including the Daedalus Wallet, which I personally rely on. The modest funding amount is reasonable for ensuring compatibility with Cardano node updates, fixing bugs, and enhancing usability for stake pool operators (SPOs), developers, and enterprises like IOG. This aligns with Cardano’s goal of robust infrastructure, as emphasized in the Cardano Foundation’s 2023 Financial Insights Report. However, I have caveats: the proposal lacks clear data on Cardano.nix’s user base or adoption beyond niche users like IOG and Daedalus, making it hard to gauge its broader ecosystem impact. Additionally, Nix’s specialized nature may limit its appeal, and the proposal could benefit from metrics demonstrating its necessity. Despite these concerns, the low cost and direct benefit to tools I use justify my support, though I encourage more transparency on usage in future proposals.
- Yes238.6K ₳No rationale
- Yes233.2K ₳No rationale
- Abstain208.3K ₳No rationale
- Yes191.1K ₳No rationale
- Yes187.4K ₳No rationale
- Yes185.6K ₳Rationale
I am voting yes on all 39 Intersect Governance actions. The community has thoroughly reviewed the many proposals presented in the Intersect Budget Process for the 2025 budget. I was deeply involved in the entire process as an SME for the Budget Committee, and then as the Secretary for the Budget Committee.
The proposals presented represent an incredible amount of development for our ecosystem for the next year. The teams all received at least 50% on Ekklesia polling. The teams will face milestones in order to continue to receive funding. If a team fails to deliver, the process will stop them from enriching themselves without returning value.
If anything, we are spending too little on our community. We need to spend more to further develop our governance and our organized events. This is a liquid democracy. If you believe that all of these proposals deserve a chance to deliver, you can shift your delegation to my DRep ID.
- Yes178.9K ₳No rationale
- Yes174.5K ₳No rationale
- Yes166.4K ₳No rationale
- No147.5K ₳No rationale
- Yes138.4K ₳No rationale
- Yes137.4K ₳No rationale
- Yes133.7K ₳No rationale
- Yes110.9K ₳No rationale
- Yes108.3K ₳Rationale
I am voting in favor of approving the treasury withdrawal for all 39 withdrawal actions that are part of the approved ecosystem budget administered by Intersect. I am voting this way for several reasons, as I will outline here. This rationale will be included in all 39 withdrawal votes.
First and foremost, I believe that we would be making a mistake in underfunding our community with our available treasury funds. The budget system as it currently stands has some flaws, as should be expected from a first version of any system. Of the current proposals, I voted to include several in the budget when it was being formed; however, I also did not vote in favor of several others. This is, of course, the case for most DReps. If I were to vote only for the proposals I initially favoured, and all other DReps did the same, we would likely approve only 2 or 3 proposals out of 39 due to the vote split. In my view, this is not an acceptable outcome for the community, and this is why I was also opposed to the idea of having 39 separate treasury withdrawal actions. I have reviewed all 39 requests, and they all have merit. Are they exactly in line with the priorities I wanted as part of the initial budget? No. Is that reason enough to vote no on several of these and end up approving only 2 or 3 proposals in the end? I certainly don't believe so.
In addition to this, the total amount of the intersect budget is roughly 10% higher than what I voted for, and I find that to be within an acceptable margin to approve all the withdrawals.
The individual proposals also all received at least 50% community approval to be included and will be subject to reviews and milestones to receive funds.
For these reasons, I am casting my vote to approve and am wishing the best of luck to all the teams waiting for funding through this process. - Yes103.1K ₳No rationale
- Yes92.6K ₳No rationale
- Yes71.3K ₳Rationale
As a DRep, I vote Yes. Cardano.nix simplifies node deployment with Nix, ensuring reproducible setups and fewer errors for SPOs and developers. Already used by IOG and Daedalus, it’s a proven tool. Led by the experienced MLabs team, this focused proposal promises high impact.
- No69.4K ₳No rationale
- Yes68.8K ₳Rationale
- Yes65.7K ₳No rationale
- Yes58.6K ₳Rationale
MLabs has a mature track record, while the budget is a small maintenance request and the community impact is modest but necessary for developer infrastructure.
Also --> previous continuation of funding shows consistency.
- No55.9K ₳No rationale
- NoChanged50.5K ₳History
Earlier votes
Yes11mo agoSuperseded
- Yes49.6K ₳No rationale
- Yes48.6K ₳No rationale
- Yes46.5K ₳Rationale
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 still stand by those decisions.
For proposals with large budgets (>500k ADA), 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.
- No45.2K ₳No rationale
- Yes36.3K ₳No rationale
- Yes36.3K ₳Rationale
🗳️ Vote: Yes on gov_action18nefry4qacd80xzs2srjahxm2e4vz3c8wvrr03rrtk8mdqfuknysq66459t
Proposal: Fund MLabs to maintain and enhance Cardano.nix – foundational Nix-based tooling for Cardano infrastructure
Amount: ₳45,217⸻
✅ Reason for Support:
As a DRep focused on long-term ecosystem sustainability, I voted Yes because Cardano.nix is critical infrastructure. It enables reproducible, secure node deployments using the Nix build system — something I rely on directly in my own bare-metal setup.
Without ongoing maintenance:
• It risks falling behind Cardano node, Haskell, and Nix updates
• Node operators, developers, and wallet teams would face higher friction and inconsistent builds
• The community would lose a reliable, standardized tool for onboarding and deploymentThis proposal ensures continued support for a tool that benefits SPOs, wallet teams, and devs alike. MLabs has the track record to deliver, and Intersect’s funding process adds accountability through legal contracts, milestone tracking, and 3rd party assurance.
- Yes29.3K ₳No rationale
- No29K ₳No rationale
- Yes26.7K ₳Rationale
MLabs has closed out and completed more proposals since my last criticism of them. Many very useful projects have been completed by them. They can have some funding. https://projectcatalyst.io/proposers/lpmaho
- Yes25.7K ₳No rationale
- Yes15.2K ₳No rationale
- No14.3K ₳No rationale
- Yes13.3K ₳No rationale
- Yes10.6K ₳Rationale
I vote for this proposal
- Yes8.3K ₳No rationale
- Yes7.7K ₳No rationale
- Yes7K ₳No rationale
- Yes6.7K ₳No rationale