Amaru Treasury Withdrawal 2026
155 DReps voted · 51 with a rationale
Open a row to read the rationale.
- Yes 6.2M ₳ No rationale
- Yes 6M ₳ Rationale
Clear deliveries and fund management have been demonstrated historically by Amaru. While cost demands are still meaningfully high, I can easily get behind a project that can continue to build and send back what's left from prior years withdrawels before asking for additional funds. We already know from prior proposals what is being delivered here is for the overall safety and security of the chain, so it's an important endeavor that some teams need to work on. I will continue to support Amaru on this project as a DRep.
- Yes 5.5M ₳ Rationale
Amaru represents a structural security investment for Cardano.
- Yes 5.3M ₳ Rationale
Amaru's proposal stands out for its transparency and integrity – they even returned over 920k ADA from the last round.
The November 2025 incident proved it: relying on a single Haskell node is a massive single point of failure. Node diversity is now a critical security need for Cardano, and Amaru looks like our strongest realistic path to get it soon.
The ask is high, and multiple clients will complicate upgrades – but resilience beats convenience when the network's future is at stake.Solid, detailed proposal with a great retrospective, and those Amaru Pi nodes at the Summit were a brilliant, tangible showcase of treasury impact.This is the standard we should expect.
Easy yes from me.Great work, team – keep it up.
- Yes 4.8M ₳ No rationale
- Yes 4.8M ₳ No rationale
- Yes 4.5M ₳ No rationale
- Yes 4.4M ₳ No rationale
- Yes 4.2M ₳ Rationale
[Portuguese]
Optamos por votar "SIM" nesta ação de governança "Amaru Treasury Withdrawal 2026" (gov_action19uhuy5uame2s60yrh6n8cyds8ps5q7tkh05dqlzmpcfy429p9w4qq5ll3g0), pois o projeto Amaru apresenta uma contribuição concreta e estratégica para a descentralização, a resiliência e a sustentabilidade de longo prazo da rede Cardano. O desenvolvimento de um nó produtor de blocos alternativo, interoperável e com baixos requisitos de hardware fortalece diretamente a diversidade de clientes, reduz a dependência de uma única implementação e amplia a robustez operacional do ecossistema. Além disso, a proposta demonstra maturidade técnica e institucional ao apresentar entregas claras para 2026, cronograma definido, métricas de desempenho, foco em segurança, auditoria externa e integração com componentes relevantes do ecossistema, como Mithril, Kupo e Dolos. Também consideramos a proposta bem fundamentada do ponto de vista de governança e responsabilidade no uso dos recursos do tesouro. O texto descreve mecanismos concretos de transparência e controle, com administração por contrato inteligente, prestação de contas pública, auditoria financeira, devolução de saldos remanescentes ao tesouro e uso restrito da contingência apenas para mitigação de volatilidade de mercado. Soma-se a isso o retrospecto positivo de 2025, que evidencia capacidade de execução, aprendizado institucional e evolução de processos. Embora o orçamento seja expressivo, ele vem acompanhado de justificativa técnica compatível com a complexidade e criticidade do trabalho proposto, o que torna o investimento proporcional ao impacto esperado para o futuro da Cardano.
[English]
We chose to vote "YES" on this governance action "Amaru Treasury Withdrawal 2026" (gov_action19uhuy5uame2s60yrh6n8cyds8ps5q7tkh05dqlzmpcfy429p9w4qq5ll3g0), because the Amaru project represents a concrete and strategic contribution to the decentralization, resilience, and long-term sustainability of the Cardano network. The development of an alternative block-producing node, interoperable and with low hardware requirements, directly strengthens client diversity, reduces reliance on a single implementation, and increases the operational robustness of the ecosystem. Furthermore, the proposal demonstrates technical and institutional maturity by presenting clear deliverables for 2026, a defined roadmap, performance metrics, a strong focus on security, external auditing, and integration with relevant ecosystem components such as Mithril, Kupo, and Dolos. We also consider the proposal well grounded from a governance and treasury responsibility perspective. It outlines concrete mechanisms for transparency and accountability, including smart-contract-based fund administration, public reporting, financial auditing, the return of unused funds to the treasury, and restricted use of contingency reserves solely for mitigating market volatility. Additionally, the positive track record from 2025 demonstrates execution capability, institutional learning, and process improvement. While the requested budget is significant, it is accompanied by a technical justification consistent with the complexity and critical nature of the proposed work, making the investment proportional to the expected long-term impact on Cardano’s future. - Yes 4.2M ₳ No rationale
- Yes 3.8M ₳ Rationale
I see this withdrawal as a continuation of a decision made by the community to prioritize this node over other options made previously. It is not a decision of this project vs. others, as that was already made previously, the decision is if this proposal is aligned with previous promises, and strategy.
I will use the same template that I used for rejecting the Dingo node which I see as a competitive and comparable proposal.
- Does this proposal require comparison with alternative approaches?
- Yes.
Node implementations are among the most complex and mission-critical components of the Cardano protocol.
Cardano’s existing node—developed in Haskell—already follows rigorous engineering and review processes designed to maximize resilience and correctness. Even so, experts acknowledge that distributed systems at this scale are never completely risk-free.
Introducing additional node implementations increases the complexity of maintaining consensus across the network. Any divergence between clients could have severe consequences.
Because of this, alternative node implementations should not be evaluated in isolation. They must be assessed comparatively alongside other potential approaches, considering architecture, operational risk, and long-term maintenance implications.
This proposal therefore requires deep technical evaluation relative to competing designs, not a standalone yes/no vote.
However, that was done last year, and at this point, we are facing an ongoing project. Teams need continuity and from governance side, Cardano must complete projects and intentions baring some significant reason to change course. I do not see that at this point. Cardano would benefit from additional nodes and this project should continue forward and not be derailed.
- Does this proposal require expert prioritization and trade-off analysis?
- Yes.
Proposals affecting protocol infrastructure involve trade-offs across multiple dimensions:
• network security
• engineering complexity
• ecosystem coordination
• long-term maintenance cost
• opportunity cost versus other protocol workThese decisions are best made through structured evaluation by domain experts who can compare alternatives and determine sequencing and priorities.
A global governance vote works well for many ecosystem initiatives, but core infrastructure decisions require coordinated technical review before they reach the treasury voting stage.
For Amaru, I see that as already completed previously. I see many of the team-members as best in the ecosystem, and the founding entities and steering committees have prioritized and highlighted the project over others.
- Is it clear this team represents the strongest available option?
- I have no reservations on the quality and ethics of the team.
When funding protocol-level infrastructure, the burden of proof should be high. It passed my high-bar.
- Should node development be funded as an isolated treasury withdrawal?
- No. However, I see it as previously approved.
Client diversity is not a standalone feature—it is a strategic infrastructure decision.
Multiple node implementations affect:
• protocol governance
• long-term maintenance obligations
• upgrade coordination
• security response processesFor these reasons, node development should emerge from a coordinated platform strategy, ideally guided by technical leadership evaluating multiple competing approaches.
Treasury funding may ultimately support such work—but only after a structured process determines which solution should be prioritized.
With Amaru, I see the ecosystem as having been previously completed this analysis, approved the project we are well along this path, so the rational choice is to complete it. It has passed those hurdles previously.
Conclusion: For these reasons, I support this proposal.
- Yes 3.7M ₳ Rationale
I support the Amaru project, as node diversity is essential for maintaining a resilient and robust ecosystem.
- Yes 3.7M ₳ No rationale
- Yes 3M ₳ No rationale
- Yes 2.8M ₳ Rationale
The Amaru team has successfully proven their capabilities to deliver with effective contingency planning in place. They were able to avoid using their contingency fund from last year and returned the leftover ADA from their previous funding to the treasury. This proves the Amaru team's honesty and credibility, and they deserve full support to continue to build critical infrastructure that Cardano needs. Thank you Amaru team, I'm happy to vote yes on your proposal!
- Yes 2.7M ₳ No rationale
- Abstain 2.6M ₳ No rationale
- Yes 2.5M ₳ No rationale
- Yes 2.5M ₳ Rationale
LFG already!
- Yes 2.5M ₳ Rationale
本提案は、Cardanoにおけるブロック生成ノードの多様性を高める戦略的投資と評価します。AmaruはRustベースの新たなノード実装であり、低ハードウェア要件や開発者層の拡大を通じて、ネットワークの分散性と耐障害性の向上が期待されます。単一実装依存のリスク低減は中長期的に重要です。一方で本件は比較的大型案件であり、費用対効果の観点からは明確なKPI設定が不可欠です。SPOによる採用数、実際のブロック生成割合、今後のプロトコル進化への適応計画などの具体的指標の明示と継続的な進捗開示を求めます。以上を踏まえ、戦略的意義を重視し賛成します。
This proposal represents a strategic investment in client diversity for Cardano. Amaru is a Rust-based block-producing node that aims to improve accessibility and broaden the developer base, potentially strengthening network resilience and decentralization over the long term. Reducing reliance on a single implementation is important for the ecosystem’s sustainability.
However, this is a relatively large funding request. Clear and measurable KPIs are necessary to ensure responsible treasury use. In particular, I expect transparency regarding SPO adoption, actual block production share, and compatibility with future protocol upgrades.
Considering its strategic value, I vote in favor while emphasizing the need for clear performance metrics and ongoing accountability. - Yes 2.5M ₳ No rationale
- Yes 2.4M ₳ No rationale
- Abstain 2.4M ₳ No rationale
- Yes 2.1M ₳ No rationale
- Yes 1.9M ₳ No rationale
- Yes 1.8M ₳ No rationale
- Yes 1.7M ₳ No rationale
- Yes 1.7M ₳ No rationale
- Yes 1.7M ₳ No rationale
- Yes 1.5M ₳ No rationale
- Yes 1.4M ₳ No rationale
- Yes 1.4M ₳ No rationale
- No 1.4M ₳ No rationale
- Yes 1.2M ₳ Rationale
I vote YES on this treasury withdrawal because the proposal addresses a core infrastructure need: stronger node diversity and resilience for Cardano, with a defined 2026 scope. My decision is based on governance discipline as much as technical value, so funding must remain tied to milestone-based payouts, objective acceptance criteria, and transparent public reporting of delivery and spending. The requested amount is significant, which makes strict accountability essential throughout execution. If these safeguards are not upheld, future support should be reconsidered.
- Yes 1.2M ₳ No rationale
- Yes 1.2M ₳ Rationale
First had some questions about what would happen with remaining funds in the case of ada price appreciation, but answers from the team made it clear that those would be paid back to the treasury.
As for the budget itself, seems reasonable, hence voting ✅ YES. - Abstain 1.1M ₳ No rationale
- Yes 1.1M ₳ No rationale
- Yes 1M ₳ Rationale
Amaru is not a discretionary application-layer bet. It is load-bearing infrastructure work directed at eliminating Cardano's most dangerous and least discussed systemic risk: the absence of a viable alternative node implementation.
The budget is competitive by market standards, the contingency structure is transparent and return-obligated, the 2025 governance track record is credible. Some concerns around contingency calculations and certain budget items though.
However, the 2025 execution delays are a legitimate concern that must be monitored closely, and the contingency scale deserves continued DRep attention in subsequent withdrawal rounds. But **withholding this vote means accepting a permanent single-client risk for the entire Cardano network. And that risk is not theoretical, is not trivial, and is not compatible with the Constitution's demands on security and decentralization. **This is precisely the kind of compounding investment that makes sure the pyramid we have build does not crumble at the core. Furthermore, it separates strategic treasury stewardship from short-sighted treasury management.
The vote is Yes, with a clear expectation that Q1 and Q2 2026 milestones are delivered on time, and with the firm message to the Amaru team: the relay node must be production-ready this quarter! The community's patience is not infinite, and neither is the treasury's appetite for carrying forward deferred commitments.
- Yes 985.7K ₳ No rationale
- Yes 955.2K ₳ No rationale
- No 935.4K ₳ No rationale
- No 922.9K ₳ No rationale
- Yes 920K ₳ No rationale
- Yes 881.3K ₳ No rationale
- Yes 860.4K ₳ No rationale
- Yes 818K ₳ Rationale
We continue to support Amaru's initiative due to the professionalism, clarity and execution proven.
- Yes 785.2K ₳ No rationale
- Yes 762.8K ₳ No rationale
- No 749K ₳ Rationale
DRep Rationale: Why I am voting "NO" on Amaru 2026
While I value the technical expertise of the Amaru team and the importance of node diversity, I am voting NO on this withdrawal for the following reasons:
Inefficient Treasury Allocation: The 4M ADA "market contingency" buffer is excessive. It locks up significant community capital that could be used for other initiatives. I prefer a model where projects request additional funds if market conditions shift, rather than over-budgeting by 40%.
Performance vs. Cost: The 2025 retrospective shows that key deliverables like Block Production and Mempool implementation are behind schedule. I cannot support a 10.1M ADA expansion until the primary goals of the previous funding round are fully realized and stable.
High Overhead: The fixed costs (Audit and Testing) and high FTE rates set a high-cost precedent for Cardano development. I am looking for proposals that demonstrate more aggressive cost-optimization for the benefit of the ADA holders.
I encourage the Amaru team to return with a more focused, milestone-driven proposal that addresses the current delays without the heavy contingency padding.