Withdraw ₳220,914 for Pallas: Sustaining Critical Rust Tooling for Cardano
191 DReps voted · 59 with a rationale · 1 changed their vote · 4 re-voted unchanged
Open a row to read the rationale.
Changed votes: 1 to yes, together voting with 9.4M ₳ of voting power.
- Yes161K ₳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.
- Yes157.8K ₳No rationale
- No149.8K ₳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.
- Yes138.6K ₳No rationale
- Yes126.4K ₳No rationale
- Yes124.6K ₳No rationale
- Yes102.5K ₳No rationale
- Abstain90.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.
- Yes83.9K ₳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. - No77.2K ₳No rationale
- Yes74.5K ₳Rationale
As a DRep and a developer, I vote Yes because Pallas is a core open-source library essential for Rust development on Cardano. It has been and continues to be widely used in several prominent projects such as Aiken, Lucid, Amaru, and Mithril.
- Yes65.9K ₳No rationale
- Yes63.1K ₳No rationale
- Yes58.7K ₳No rationale
- Yes56.4K ₳No rationale
- Yes56.1K ₳No rationale
- Yes51.8K ₳Rationale
With the growth of Amaru node, this is crucial for more RUST compatible on Cardano toolings
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.
- Yes48.7K ₳No rationale
- Yes48K ₳No rationale
- No45.3K ₳No rationale
- Yes36.9K ₳No rationale
- Yes36.4K ₳Rationale
✅ Pallas Rust Tooling – ₳220,914
Why I voted YES:
Pallas is a foundational Rust toolkit for Cardano, powering essential infrastructure like Aiken, Mithril, Lucid, and Amaru. With 591 commits and 39 contributors, it’s one of the most active and widely used open-source libraries in the ecosystem. Continued funding ensures protocol compatibility, performance, and security as Cardano evolves.Key benefits:
• 🧱 Provides core blockchain primitives for Rust development
• 🔧 Enables rapid dApp/tooling creation without reinventing the wheel
• 🚀 Actively used by major projects across the ecosystem
• 🧑💻 Maintains open-source transparency and collaboration
• 🔄 Keeps up with protocol changes and critical bug fixesSustaining Pallas means supporting the foundation that many Cardano-native tools are built on. It’s a small but vital investment in ecosystem health and developer experience.
- Yes28.8K ₳No rationale
- No26.7K ₳Rationale
No, TxPipe has way too many projects still open on Catalyst that are not completed.
- Yes15.3K ₳No rationale
- No14.3K ₳No rationale
- Yes10.7K ₳Rationale
I vote for this proposal
- YesRevoted8.4K ₳History
Earlier votes
Yes1y agoSuperseded
- Yes6.8K ₳No rationale
- Yes5.7K ₳No rationale
- No3.6K ₳No rationale
- Yes1.6K ₳No rationale
- Yes675.6 ₳No rationale
- Yes335.9 ₳No rationale
- Yes52.8 ₳No rationale
- Yes13.5 ₳No rationale
- Yes6.3 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale
- YesRevoted0 ₳History
Earlier votes
Yes1y agoSuperseded