Withdraw ₳220,914 for Pallas: Sustaining Critical Rust Tooling for Cardano
191 DReps voted · 51 with a rationale
Open a row to read the rationale.
- Yes 1.2M ₳ No rationale
- Yes 1.2M ₳ Rationale
I decided to vote ✅ YES on 37 treasury withdrawals, ➖ ABSTAIN on none, and ❌ NO on 2 treasury withdrawals from the Intersect 2025 budget.
It’s obvious I consider all proposals I approved in the budget vote on Ekklesia beneficial for Cardano, so those all receive a ✅ YES vote.
I also vote ✅ YES for most proposals I initially abstained from or voted against in the Ekklesia vote. There are a few reasons for this:
- Some proposals gained strong community support after all, so I don’t want to be the one standing in the way, especially when the requested amount is negligible in the bigger picture.
- Some proposals I actually liked, but I found them more suitable for Catalyst. However, with all the delays, it now makes more sense to fund them as soon as possible.
- Some didn’t get my initial support because I thought the requested amount was too high. But I now believe it’s better for the ecosystem to fund them, despite the larger budget, than not fund them at all.
- I needed to vote for budget proposals with my own NCL in mind. Not all those I approved made it, however, so that leaves some room for other ones.
I won’t approve the treasury withdrawal for two proposals:
❌ Withdraw ₳3,000,000 for High-yield RWA Asset for Cardano: Tokenized Real Estate
This proposal won’t bring much value to our ecosystem, imho.❌ Withdraw ₳1,500,000 for Complement Catalyst: Extended Quadratic Funding---Zero Operational Costs
While the proposal includes some interesting ideas for a fairer voting mechanism, I now support Catalyst and don’t see the need for an additional funding system at this moment, especially considering total spending. The requested amount also seems too small to meaningfully fund multiple projects. While the model relies on donations, it’s unclear what the donor incentive is. Since voting power is tied to donation size, why wouldn’t donors just support specific fundraisers run directly by the projects they care about? That way, they can ensure their contribution goes straight to their preferred initiative without needing it to win a vote first.
I do appreciate the idea of a hybrid funding model where the treasury covers part of a project, but ideally, the remaining portion should come from investors rather than donations, imho.
Lastly, I don’t appreciate that the proposal’s title refers to Catalyst, even though it has no relationship to it. This seems intended to mislead people into thinking Catalyst would benefit from this proposal, which it doesn’t...I acknowledge there’s a metadata issue in the proposal “Withdraw ₳45,217 for MLabs Core Tool Maintenance & Enhancement: Cardano.nix”, but I approved it nonetheless, as the problem is minor and not worth obstructing the process.
- Yes 1.1M ₳ No rationale
- No 1.1M ₳ No rationale
- Yes 1M ₳ Rationale
I vote Yes to fund Pallas because it is a critical Rust-native toolkit underpinning key Cardano projects and essential for ecosystem stability. However, the proposal lacks clear KPIs and a strong innovation roadmap aligned with Cardano’s long-term vision. Continued funding should be contingent on rigorous milestone tracking and demonstrable impact beyond maintenance. Supporting Pallas now is pragmatic—but we must insist on sharper accountability going forward.
- Yes 1M ₳ No rationale
- Yes 1M ₳ No rationale
- Yes 955.2K ₳ No rationale
- Yes 947.9K ₳ No rationale
- Yes 922.9K ₳ No rationale
- Abstain 860.4K ₳ No rationale
- Yes 819K ₳ No rationale
- Yes 818K ₳ No rationale
- Yes 810K ₳ No rationale
- Yes 793K ₳ No rationale
- Yes 785.2K ₳ No rationale
- Yes 765.1K ₳ No rationale
- Yes 733.1K ₳ No rationale
- Yes 717.1K ₳ No rationale
- Yes 716.6K ₳ Rationale
We, The Dutch Drep, vote Yes on this withdrawal governance action for 2025 Input Output Engineering Core Development Proposal, administered by Intersect. DISCLAIMER: Dutch Drep members may be contracted to perfom work for this proposal and as such benefit from its passing. Our affirmative vote is based on IO and IOE representing significant capability needed for Cardano to progress to the next stage. Although IO's proposal can be argued to be somewhat lacking in detail, this must be weighed together with the undeniable track record of IO and broader mission focus. The size of this proposal is substancial however we expect that the positive externalities to far outweigh the costs to the Cardano Ecosystem given IO's open source and collaborative DNA. Additionally we see no other party being able to coordinate with the relevant parties needed to deliver the scope of work as described at this time. These were major factors in our decision to support this proposal.
- Yes 655K ₳ No rationale
- Yes 654.5K ₳ No rationale
- Yes 624.8K ₳ Rationale
I have voted in favor of this action to demonstrates my intention to execute without delays and move the treasury expenditure process forward. I also want to note that I will not seriously consider individual requests from the treasury for less that 1,500,000 ADA moving forward. I reserve the right this round because I feel the process was not properly explained to proposers and DRep and it would be unfair to implement this personal guardrail at this time. Requests below that threshold are better suited for Catalyst funding or bundled together in MBO, DAO, or conglomerate entities. TWA (Treasury Withdrawal Actions) need be comprehensive and not ad hoc as that makes oversight more costly and inefficient.
A budget and all included line items has already been approved, and now is the time to disperse funding and enable further development of the Cardano network. The proposal was selected through a well-defined process, and I will fully support it out of respect for the will of the broader Cardano community and a belief in respecting the consensus we achieved together under the Intersect-administered budget process. The process reflects a coordinated, strategic approach to funding Cardano’s ecosystem-critical infrastructure. The community has thoroughly reviewed the proposal. I was actively involved in the entire process and the proposal presented represents development that provides a tangible benefit to our ecosystem. It would be a mistake to underfund our ecosystem’s development when we can sustainably provide the required funding with our available treasury reserves.
Furthermore there are exceptional oversight mechanisms in place to ensure a minimum amount of wast, fraud, and abuse of treasury expenditures, such as Intersect’s smart contract framework (audited by TxPipe and MLabs), Multi-party oversight (including Cardano Foundation, Sundae Labs, NMKR, etc.), A clear milestone-driven disbursement model, and full transparency via TRSC/PSSC dashboards.
These governance and assurance systems meet the constitutional standards for accountability and risk management and provide confidence in efficiency and execution. - Yes 589.2K ₳ No rationale
- Yes 587.1K ₳ Rationale
I believe robust, low-level tooling is the invisible backbone of any thriving ecosystem — and in Cardano, Pallas is exactly that. Built in Rust and widely adopted by crucial projects like Aiken, Lucid, Mithril, and Amaru, Pallas provides the cryptographic primitives and serialization layers that allow developers to focus on innovation rather than protocol details. Its open-source nature, wide contributor base, and modular architecture make it an essential public good for enabling both interoperability and scalable dApp development across Cardano.
In my view, TxPipe has consistently proven its reliability and alignment with Cardano’s long-term goals through its public work and transparent delivery. Funding this proposal ensures that Pallas remains updated, maintained, and secure as the protocol evolves. This is not just a maintenance request — it's an investment in the developer experience, ecosystem efficiency, and technical sovereignty of Cardano. I support this proposal with a strong YES, recognizing its foundational role in sustaining decentralized innovation.
- Yes 473.6K ₳ No rationale
- Yes 466.2K ₳ No rationale
- Yes 445.1K ₳ No rationale
- Yes 443.5K ₳ No rationale
- Yes 385.6K ₳ Rationale
As Krypto Labs, a Cardano DRep deeply engaged in the 2025 budget process, I am voting YES on the ₳220,914 Pallas proposal.
This funding is crucial for sustaining Pallas, a foundational suite of Rust-native libraries that provides essential blockchain primitives like cryptographic functions and CBOR encoding.Pallas is a cornerstone for critical projects such as Aiken, Lucid, and Mithril, enabling developers to build higher level applications like explorers, smart contracts and wallets more efficiently.
This investment diversifies Cardano's tooling beyond its Haskell heavy ecosystem, attracting a broader developer base and fostering innovation.
The project's active open-source collaboration, with numerous commits, pull requests, and contributors, underscores its community value.TxPipe, the proposer, has a proven track record of over three years in open source delivery within Cardano, successfully completing multiple Project Catalyst milestones. The requested ₳220,914 for 0.625 FTEs represents a modest, high-ROI investment, ensuring ongoing maintenance, bug fixes, and feature development.
This prevents stagnation and bolsters the entire ecosystem's resilience.Furthermore, the proposal emphasizes transparent development, public milestones, and third party assurance via Intersect, mitigating risks and ensuring accountability. Approving this proposal aligns directly with our commitment to strengthening Cardano's core infrastructure, enhancing developer accessibility, and promoting long term growth for all stakeholders.
- No 382.6K ₳ No rationale
- Yes 377.3K ₳ No rationale
- Yes 371.8K ₳ No rationale
- Yes 328.9K ₳ No rationale
- Yes 321.1K ₳ No rationale
- Yes 314.4K ₳ Rationale
In alignment with my voting on the 2025 Cardano Budget Reconciliation process through Ekklesia platform, I support this withdrawal and therefore vote YES.
In alignment with my voting on the 2025 Cardano Budget Reconciliation process through Ekklesia platform, I support this withdrawal and therefore vote YES.
- Yes 313.1K ₳ Rationale
I’m voting YES to fund the Pallas Rust tooling proposal as I believe it provides essential elements that underpin critical Cardano projects including Aiken, Lucid, and Mithril, Sustains this opensource library and ensures developers can continue building reliable explorers, Smart contracts and wallets, strengthening ecosystem’s resilience and attracting a wider developer community outside of Haskell.
TxPipe team have a strong track record of delivering opensource solutions for Cardano over a few years. The requested funding is modest relative to its ecosystem impact and supports ongoing maintenance, bug fixes, and enhancements. This investment helps prevent stagnation of a foundational toolset and supports long-term innovation.
While smaller requests like this might, in future, be better suited for Catalyst or bundled under broader initiatives, this round is an opportunity to learn and refine the treasury withdrawal process. It’s important not to hold up positive votes on essential infrastructure that has already been reviewed and approved in earlier stages.
This aligns with my priorities as a DRep: sustainable infrastructure, long-term strategic thinking, support for proven open-source contributors, and enabling a healthy, diverse developer ecosystem for Cardano.
- Yes 298.6K ₳ 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.
- Yes 295.2K ₳ No rationale
- Yes 271.5K ₳ No rationale
- Yes 262.3K ₳ No rationale
- Abstain 258.6K ₳ Rationale
🧭 Evaluation Methodology and Rationale
Given the unprecedented volume and technical depth of the 39 Treasury Withdrawal Governance Actions submitted in this cycle, a comprehensive, proposal-by-proposal audit of budgets, scopes, and implementation frameworks would demand a level of time and resourcing incompatible with the available review window.
Rather than abstaining from participation, I adopted a hybrid evaluation methodology that combines AI-assisted content parsing with structured human analysis. This standardized checklist framework was designed to streamline high-volume assessment while preserving critical reasoning, contextual understanding, and value-based judgment.
All final decisions reflect deliberate human oversight — AI outputs serve to accelerate comprehension and comparison, but no vote is cast without manual review and a principled assessment of relevance, feasibility, and accountability.
📋 Checklist Criteria Explained
Each proposal is evaluated across seven standardized dimensions using a three-point scale:
✅ Yes — fully meets the criterion
🟡 Partial — partially meets the criterion
❌ No — does not meet the criterion1️⃣ Ecosystem Essentiality
Does the proposal address a critical function within Cardano, or is it peripheral or redundant?
This criterion assesses the strategic relevance of the initiative. Proposals should contribute meaningfully to Cardano’s infrastructure, decentralization, usability, or long-term resilience. Initiatives that duplicate existing efforts or lack demonstrable alignment with ecosystem priorities may score lower.2️⃣ KPIs or Impact Identifiers
Does the proposal define measurable success indicators or quantifiable outcomes?
This includes Key Performance Indicators (KPIs), numerical targets, milestones with metrics, or other tangible proxies of progress. The absence of quantifiable measures introduces uncertainty around potential impact and limits effective performance tracking.3️⃣ Milestones and Deliverables
Are there clear, time-bound milestones with verifiable deliverables and acceptance criteria?
Effective proposals define not only what will be delivered, but also when and how success will be verified. This enables staged disbursement, delivery monitoring, and community oversight. Lack of milestone clarity may indicate execution risk.4️⃣ Team Visibility & Track Record
Is the proposing team clearly identified, with relevant expertise and a verifiable delivery history?
This criterion evaluates the transparency and credibility of the individuals or organizations responsible for delivery. Established contributors with proven ecosystem involvement are preferred. Anonymous or unvetted teams may raise accountability concerns.5️⃣ Budget Structure and Detail
Is the budget transparently structured, with clear categories, amounts, and justification?
A strong proposal includes itemized costs (e.g., per workstream, staff role, tooling), explains the rationale behind budget allocations, and clarifies estimation methods. Lack of detail in budget structure reduces transparency and erodes confidence in treasury stewardship.6️⃣ Internal Consistency
Are the on-chain metadata, proposal content, and budget details aligned?
Consistency across all proposal components — including funding amounts, receiving addresses, project scope, and references — is essential. Misalignment creates confusion, undermines credibility, and may signal governance process weaknesses.7️⃣ Conflict of Interest
Does this proposal present a potential conflict of interest that could compromise the impartiality of the evaluation?
To preserve the integrity of the voting process, any proposal in which I (as evaluator) hold a significant, non-marginal conflict of interest will be automatically met with an ABSTAIN vote. Minor or indirect associations are disclosed where relevant, but only material conflicts — such as direct financial involvement, employment, or formal partnership — trigger abstention. This ensures all evaluations remain transparent, independent, and in service of the broader Cardano community.
🗳 Governance Action Evaluation – Final Review
Proposal: Withdraw ₳220,914 for Pallas – Sustaining Critical Rust Tooling for Cardano
Vendor: TxPipe (administered by Intersect)
Type: Treasury Withdrawal
Requested Amount: ₳220,914
Governance Action ID:gov_action13tfag48nf94rtjcdq7c06vhkslmxxw9h6c88sl7q5g5nnewcsvlqghuqg03
📋 Evaluation Checklist
1️⃣ Ecosystem Essentiality
✅ Yes
“Pallas has become a critical Rust-native foundation for Cardano development, providing essential blockchain primitives such as cryptographic primitives and CBOR encoding.”
“Projects like Aiken, Lucid, Mithril, and Amaru already utilize Pallas…”Pallas is a strategically essential component in Cardano’s infrastructure. It provides reusable primitives for CBOR parsing, cryptographic functions, and decoding of chain data structures. These enable modern development efforts in Rust and allow the ecosystem to expand beyond Haskell-centric tooling.
Key dependencies such as Aiken, Lucid, Mithril, and the Amaru node rely on Pallas for low-level operations. Without it, these projects would face significant maintenance overhead, code duplication, and higher risk of inconsistencies.
2️⃣ Budget Structure and Detail
✅ Yes
“0.5 FTE Blockchain Developer for 12 months = $99,412 = ₳165,686”
“0.125 FTE Tech Lead for 12 months = $33,137 = ₳55,228”The proposal provides a clear labor-based cost breakdown using daily rates and FTE percentages. The rate of $825/day for the developer and $1,100/day for the tech lead are slightly above market averages, but within reason for experienced Rust-based infrastructure work in the Web3 space.
No other cost categories (infrastructure, security, support, etc.) are included — all work is expected to be delivered via internal labor. There is no per-task hour allocation, but the transparency in rate calculations offsets this gap for a proposal of limited complexity.
3️⃣ KPIs or Impact Identifiers
🟡 Partial
“At least one major feature or optimization is implemented.”
“Pallas remains fully compatible with the latest Cardano releases.”
“With 591 commits, over 430 pull requests, and 39 contributors…”The proposal includes some functional targets under its “definition of done,” and references past performance indicators. However, it lacks measurable, forward-looking KPIs, such as usage growth, performance metrics, or defined success thresholds. The absence of outcome metrics limits external accountability and auditability.
4️⃣ Milestones and Deliverables
🟡 Partial
“All milestones, acceptance criteria, payment amounts and expected delivery dates will be agreed between the Vendor and Intersect… detailed in the Legal Contract.”
A general scope is outlined, and the team commits to maintaining compatibility, delivering one new feature, and engaging with the community. However, no public roadmap, timed milestones, or acceptance criteria are provided before ratification. While this is less problematic due to the project's maintenance nature, it still hinders transparency.
5️⃣ Internal Consistency
✅ Yes
All details (amount requested, metadata, description) are internally consistent and match the budget Info Action from which this withdrawal is sourced.
6️⃣ Team Visibility & Track Record
🟡 Partial
“TxPipe has helped develop several dApps… successfully completed several Catalyst proposals… participated in Partnerchain SDK…”
TxPipe has a strong technical reputation in Cardano. However, they are currently managing 8 active Catalyst proposals, most of which are delayed by weeks to months. This indicates possible overextension and unacknowledged bandwidth risk. The proposal does not disclose these commitments, nor does it offer any mitigation plan or delivery prioritization.
7️⃣ Conflict of Interest
✅ No Conflict
No material or financial conflict identified. I have no professional or financial ties to TxPipe or Intersect.
🧠 Critical Summary
This proposal requests ₳220,914 to sustain Pallas, a critical Rust-native toolkit used widely across the Cardano ecosystem. It plays a foundational role in enabling developer tooling beyond Haskell, especially for Aiken, Lucid, Mithril, and node alternatives like Amaru.
The labor-based budget is clearly structured, and the technical scope is well-understood. However, the lack of transparent milestones, verifiable KPIs, and public delivery planning reduces accountability, especially given that TxPipe is already behind schedule on multiple concurrent Catalyst projects.
🗳 Voting Decision: ABSTAIN
While the value of Pallas is not in question, I abstain from this vote due to the following:
- No public KPIs or success metrics
- No milestone roadmap or timing disclosures
- High delivery risk from overlapping commitments
- No declared mitigation for known execution delays
A more transparent and realistically scoped proposal — with milestones and resourcing aligned to current delivery bandwidth — would be better positioned for funding.
- Yes 257K ₳ Rationale
I voted YES on the Treasury Withdrawal titled Pallas – Sustaining Critical Rust Tooling for Cardano requesting ₳220,914.
Pallas is a critical piece of Rust-based infrastructure, used daily by protocol developers, explorers, wallet libraries, and tools like Aiken, Lucid, Mithril, and Amaru. This proposal sustains the library through dedicated engineering time and smart-contract-governed payments.
TxPipe is the original Pallas maintainer and has proven delivery capacity through Catalyst and open-source history. Their GitHub activity and engagement with the broader Cardano contributor community earn high marks on transparency and reliability.
Funding mechanisms use the TRSC smart contract framework with full moderated delivery assurance, milestone tracking, and public dashboards. All data is verified on-chain using metadata hashes and IPFS anchors.
Given Pallas’s widespread usage, developer importance, and vulnerability to protocol drift without support, I fully support this constitutional treasury withdrawal for a modest, proportionate amount. Sustaining this public good is aligned with Cardano’s roadmap and ecosystem health.
- No 252.6K ₳ No rationale
- No 245K ₳ No rationale
- Yes 238.6K ₳ No rationale
- Yes 238.2K ₳ No rationale
- No 208.6K ₳ Rationale
While the Pallas project offers Rust-native building blocks for Cardano, I believe this treasury withdrawal proposal does not merit funding at this time. My primary concerns stem from skepticism about Rust’s role in the Cardano ecosystem. Rust, despite its vocal proponents, has a relatively niche adoption rate compared to other programming languages, and its complexity may limit its appeal to a broader developer base. Pallas, while open-source and collaborative, primarily serves a subset of projects (e.g., Aiken, Lucid, Mithril), and the demand for Rust-based tooling does not yet justify the proposed allocation of resources for a 0.5 FTE blockchain developer and 0.125 FTE tech lead. Given the Cardano treasury’s finite resources, I believe funding should prioritize initiatives with wider adoption and broader ecosystem impact over specialized tools like Pallas that cater to a narrower, Rust-focused audience.
- Yes 206.4K ₳ No rationale
- Yes 190.2K ₳ No rationale