Cardano Blockchain Ecosystem Budget: Amaru Node Development 2025
228 DReps voted · 62 with a rationale · 7 re-voted unchanged
Open a row to read the rationale.
- Yes8.9M ₳Rationale
I am voting **Yes **on the Cardano Blockchain Ecosystem Budget proposal for Amaru Node Development 2025. I believe this initiative represents a strategically important step toward strengthening Cardano’s decentralization and network resilience. Introducing a second block-producing node written in Rust addresses a critical concern around single-node dependency and improves system redundancy, interoperability and overall security. The project’s emphasis on modular architecture and industry-standard observability will also support a better operational experience for SPOs and infrastructure contributors.
I have confidence in the team behind this proposal. The members of PRAGMA, including TxPipe, Sundae Labs, Blink Labs, and others, have demonstrated a consistent commitment to Cardano’s growth and have delivered meaningfully on past initiatives. Their leadership in developing Amaru is reassuring and lends credibility to the projected outcomes.
The budget request of ₳1.5M, which covers the second half of 2025, appears reasonable and well justified. At approximately ₳750K USD equivalent for 6 FTEs, the per-FTE cost falls well within industry norms. I also appreciate the transparency in breaking out previously Catalyst-funded components, ensuring there is no overlap in funding.
That said, my support is not without caveats. First, the smart contract framework proposed for fund administration is still incomplete. While I recognize the intention to finalize and audit it before the first disbursement, its current state introduces execution risk. Second, I believe the project would benefit from clearer, quantifiable KPIs or milestones that allow the community to objectively assess progress. Finally, as one of the first budget-oriented Info Actions under Voltaire, this proposal sets an important and excellent precedent. Future actions should ensure even greater transparency, early community input, and enhanced reporting frameworks.
Despite these reservations, I find the proposal’s alignment with Cardano’s constitutional values and its potential long-term impact compelling. I am casting a Yes vote and will monitor future developments closely, particularly the implementation of the smart contract and progress reporting. I look forward to seeing this project contribute meaningfully to the robustness and decentralization of the Cardano network.
- Abstain8.1M ₳No rationale
- Yes7.7M ₳No rationale
- YesChanged7.6M ₳Rationale
The provided rationale for a second node implementation is technically strong and strategically aligned with decentralization principles. Reducing reliance on the Haskell node is sound from both a security and governance standpoint. Of course this argument would not apply ad infinitum, as adding too many nodes may lead to wasted efforts. There’s a thin line between strategic redundancy and fragmentation. However, so far Cardano has put all eggs in the Haskell basket. The Rust node will add resilience through implementation diversity and represent a new pathway to approach Cardano for dev teams.
Is seems to be fairly priced by Web3 standards for a 6-month effort with a senior team.
The proposal takes governance seriously, with credible disbursement and reporting mechanisms.
I further appreciate the direct submission and the avoidance of going through a much more convoluted process with many other proposals that need to be "packaged together" in one info action. This direct submission allows DReps to vote directly on this proposal and its own merits.
Last but not least, the implementing team is quite capable and well-known for their quality contributions to the ecosystem through a myriad of different projects.Earlier votes
No1y agoSuperseded
The provided rationale for a second node implementation is technically strong and strategically aligned with decentralization principles. Reducing reliance on the Haskell node is sound from both a security and governance standpoint. Of course this argument would not apply ad infinitum, as adding too many nodes may lead to wasted efforts. There’s a thin line between strategic redundancy and fragmentation. However, so far Cardano has put all eggs in the Haskell basket. The Rust node will add resilience through implementation diversity and represent a new pathway to approach Cardano for dev teams.
Is seems to be fairly priced by Web3 standards for a 6-month effort with a senior team.
The proposal takes governance seriously, with credible disbursement and reporting mechanisms.
I further appreciate the direct submission and the avoidance of going through a much more convoluted process with many other proposals that need to be "packaged together" in one info action. This direct submission allows DReps to vote directly on this proposal and its own merits.
Last but not least, the implementing team is quite capable and well-known for their quality contributions to the ecosystem through a myriad of different projects.Yes1y agoSuperseded
The provided rationale for a second node implementation is technically strong and strategically aligned with decentralization principles. Reducing reliance on the Haskell node is sound from both a security and governance standpoint. Of course this argument would not apply ad infinitum, as adding too many nodes may lead to wasted efforts. There’s a thin line between strategic redundancy and fragmentation. However, so far Cardano has put all eggs in the Haskell basket. The Rust node will add resilience through implementation diversity and represent a new pathway to approach Cardano for dev teams.
Is seems to be fairly priced by Web3 standards for a 6-month effort with a senior team.
The proposal takes governance seriously, with credible disbursement and reporting mechanisms.
I further appreciate the direct submission and the avoidance of going through a much more convoluted process with many other proposals that need to be "packaged together" in one info action. This direct submission allows DReps to vote directly on this proposal and its own merits.
Last but not least, the implementing team is quite capable and well-known for their quality contributions to the ecosystem through a myriad of different projects. - Yes7.3M ₳No rationale
- Yes6.7M ₳No rationale
- Yes6.5M ₳No rationale
- Yes5.7M ₳No rationale
- Yes5.7M ₳No rationale
- Yes5.5M ₳No rationale
- Yes5.5M ₳No rationale
- Yes5.1M ₳No rationale
- Yes4.9M ₳No rationale
- Yes4.8M ₳No rationale
- Yes4.6M ₳No rationale
- Yes4.5M ₳No rationale
- Yes4.2M ₳Rationale
[Portuguese]
Optamos por votar "Sim" nesta ação de governança (gov_action1h4y...w9kxxz), pois um software de nó alternativo ao oficial contribui para a saúde e resiliência da blockchain Cardano. Além disso, foram apresentadas métricas de controle de qualidade e execução do projeto, de modo a garantir o acompanhamento pela comunidade.
[English]
We chose to vote "Yes" on this governance action (gov_action1h4y...w9kxxz) because an alternative node software to the official one contributes to the health and resilience of the Cardano blockchain. Additionally, quality control and project execution metrics were presented to ensure proper community oversight. - Yes4M ₳No rationale
- No3.9M ₳No rationale
- YesRevoted3.9M ₳History
Earlier votes
Yes1y agoSuperseded
- Yes3.6M ₳Rationale
Node diversity has been a long time coming. An easy yes from me.
- Yes3.5M ₳No rationale
- Yes3.5M ₳No rationale
- Yes3.1M ₳No rationale
- Yes3M ₳Rationale
It is essential for us to have node diversity for Cardano - this is a critical piece needed for the continued decentralization of Cardano. The Amaru team is trusted and completely capable of executing this project, so I believe this is good use of ADA holder treasury funds and I support it.
- Abstain2.8M ₳No rationale
- Yes2.7M ₳No rationale
- Yes2.7M ₳No rationale
- Yes2.7M ₳No rationale
- Yes2.7M ₳No rationale
- Yes2.7M ₳Rationale
Cardanoネットワークの将来において、ノード実装の多様性はセキュリティ・レジリエンス・開発の自由度に直結する重要な基盤であると考えます。
その観点から、今回の「Amaru Node開発提案」は、単なる新規ノード実装の提案にとどまらず、Cardanoの持続可能性を支える構造的な進化であると評価しています。AmaruはRustで構築されており、低リソース・高効率・高安全性を実現しつつ、WebAssembly（WASM）やRISC-Vといった次世代基盤との親和性も高く、軽量ノードやエッジ環境への展開が将来的に期待されます。これは、Cardanoのノードがデータセンターやクラウドに限定されず、地域端末やIoT、教育現場などにまで広がる未来を支える基盤となります。
また、開発を主導するPRAGMAは、Cardano FoundationやdcSpark、TxPipeなどの中核組織によって構成されており、中立性・技術力・運用経験のバランスが取れた構成です。
スマートコントラクトによる予算管理、定期レポート・デモなどの透明性のある運用体制も整備されており、本提案は「進歩」と「ガバナンス強化」を両立する良質な例と受け止めています。
本提案にYES票を投じます。
Diversity in node implementation is a critical foundation for the security, resilience, and development freedom of the Cardano ecosystem.
From this perspective, the "Amaru Node Development" proposal is not merely a technical project but a structural evolution supporting Cardano’s long-term sustainability.Amaru is implemented in Rust, aiming for efficiency, security, and low resource usage, and is also highly compatible with emerging platforms such as WebAssembly (WASM) and RISC-V. These technologies pave the way for future lightweight nodes and edge deployment, enabling Cardano nodes to expand beyond data centers into local devices, IoT systems, and educational environments—a key for true global decentralization.
The project is led by PRAGMA, a non-profit consortium composed of trusted ecosystem members including the Cardano Foundation, dcSpark, and TxPipe, providing a well-balanced mix of neutrality, technical depth, and operational reliability.
With a smart contract-based budget system, regular demos, and quarterly reports, this proposal exemplifies a mature fusion of innovation and transparent governance.
I cast a YES vote on this proposal.
- No2.6M ₳No rationale
- Yes2.5M ₳No rationale
- Yes2.5M ₳Rationale
I think this is a well detailed proposal and the cost is reasonable for the value.
- Yes2.4M ₳No rationale
- Yes2.3M ₳No rationale
- No2.3M ₳No rationale
- Yes2.2M ₳No rationale
- Yes2.2M ₳No rationale
- Yes2M ₳No rationale
- Yes1.9M ₳No rationale
- YesRevoted1.7M ₳Rationale
As a DRep and a software architect with a lot of experience, I’m all in for the Amaru proposal to build a Rust-based Cardano node. Rust is great for performance and memory safety, which means the node will be more efficient and reliable—good news for both stake pool operators and developers. Plus, having an alternative node makes the whole network more decentralized and resilient. Amaru’s approach with better monitoring and a modular setup just makes sense and fits Cardano’s goals, so I’m definitely voting yes.
Earlier votes
Yes1y agoSuperseded
- Yes1.7M ₳No rationale
- Yes1.6M ₳No rationale
- Yes1.6M ₳No rationale
- Abstain1.6M ₳No rationale
- Yes1.6M ₳No rationale
- Yes1.6M ₳Rationale
My votes for the currently active budget governance actions are as follows:
- ✅ YES on the 275M Intersect Budget
- ✅ YES on the Amaru Node Development Budget
- ❌ NO on the 7.5M Community Builders Budget
The Intersect budget includes a broad set of proposals that are generally positive for the Cardano ecosystem. While I may have reservations about some individual proposals, approving the budget doesn't automatically release funds. I can re-evaluate specific items later when the associated treasury withdrawal actions are submitted on chain. I strongly recommend avoiding overly grouped treasury withdrawals, bundling too many proposals together can result in good initiatives being blocked due to a few contentious ones.
As for the Amaru Node Development Budget, if it had been included in the recent Ekklesia vote, it likely would have passed, and I would have supported it then as well. That's why I will support it now too. For better clarity, I recommend including the requested budget amount in the governance action title next time.
I would've preferred to vote on the Community Builders Budget after seeing the outcome of the Intersect budget. If that last one were to fail, I might have considered supporting the community one, but since it was submitted beforehand, that option is off the table now. More importantly, this budget doesn't include the proposals from founding entities and there are no separate gov actions for those. It doesn't make sense to fund only this subset of proposals in isolation imho. So for now I can only assume the Intersect one will pass, which renders this budget unnecessary. Additionally, this budget appoints Intersect as the administrator, yet includes the Starstream proposal, which will not use Intersect as an administrator. For these reasons, I cannot support the Community Builders Budget at this time.
I'm aware that some of my reasons for voting NO on the community budget could also apply, to some extent, to the Amaru budget. However, the Amaru budget doesn't overlap with another Budget.
- Yes1.4M ₳No rationale
- Yes1.4M ₳No rationale