Cardano Blockchain Ecosystem Budget: Amaru Node Development 2025

System1y ago1 post

228 DReps voted · 60 with a rationale · 7 changed their vote

Open a row to read the rationale.

  • Abstain13.9M ₳Rationale

    I am voting to abstain on the Amaru Node Development budget info action with hash bd488931f792651fefa9c6fda185a2c6cec83245b51d994e33090ce36e29cc26#0.

    I am abstaining because of a potential conflict of interest. I am one of the scope owners on this project, and Sundae Labs will be one of the development teams employed to help deliver on the goals of the project, and so I cannot in good conscience vote on this proposal. That being said, I believe very very strongly in the need for Node Diversity. Beyond just the added robustness to the network, reimplementing the Cardano protocol in another language is a forcing function: all of the design decisions, implementation details, and protocol trivia must be opened and re-examined in order to build a node. As we do so, we are making sure to document these things clearly, making them accessible to any who want to build on Cardano, from nodes. The beneficiaries of this effort extend far beyond those building alternative nodes, but to those building tooling, dApps, and interconnectivity solutions. Building an alternate node will help decentralize not just the network, but the brain trust of the entire protocol.

    Additionally, while some hold reservations about how it may impact delivery timelines of other projects, I'm actually quite optimistic. I believe that having a fresh, lower risk code base to experiment in may ultimately accelerate some of these roadmap items like Leios or Starstream.

    So, while I am abstaining on a matter of principle, if you are looking for guidance on how I would have voted absent that conflict, it would be a resounding yes.

  • Yes13.3M ₳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.

  • Yes12.1M ₳Rationale

    As Wada DRep, we represent a decentralized and globally connected network of Cardano community builders, innovators, and voters; many based across Africa and the diaspora. Our role in constitutional governance is to act in the best interests of the ecosystem while reflecting the priorities of our community and honoring our internal deliberative frameworks.

    After careful review and deliberation, we have voted YES on the Amaru Node Development proposal, which requests ₳1.5 million in Treasury funding to support the project’s second phase in 2025. The Amaru project represents more than a technical milestone; it is a foundational step toward realizing the full vision of a resilient, multi-client, and decentralized Cardano. It embodies constitutional alignment, budgetary discipline, and strategic foresight, and its success or failure will significantly shape the ecosystem’s credibility and progress.

    Cardano currently operates with a single block-producing node, i.e.,the Haskell node maintained by IOG. While it has served the network well, relying on one implementation creates systemic risk:
    *

    A single point of failure, with no fallback in case of critical bugs.
    *

    Limited validation of protocol conformance and specs.
    *

    Bottlenecks in innovation, observability, and integration across environments.

    Amaru addresses these by introducing a fully interoperable, modular node in Rust, which brings improved performance, memory efficiency, and cross-platform capabilities (e.g., WebAssembly, RISC-V). A second node implementation increases network resilience, fosters protocol transparency, and accelerates feature experimentation without compromising safety.

    The Amaru proposal is a textbook example of what Voltaire-era BIA should look like:
    *

    It complies fully with Articles IV.1 through IV.4 of the Cardano Constitution.
    *

    It proposes a multi-signature smart contract system to manage disbursements.
    *

    Each scope of work has a clearly defined owner and budget.
    *

    Safeguards include milestone-gated releases, pause-payment mechanisms, refund capabilities, and credential rotation.

    Amaru is governed by PRAGMA, a nonprofit association formed by core ecosystem teams: Blink Labs, dcSpark, Sundae Labs, TxPipe, and the Cardano Foundation. This collaboration brings together some of the most experienced contributors to Cardano’s open-source tooling and node infrastructure. Moreover, the team has committed to:
    *

    Quarterly progress reports, made public via GitHub.
    *

    Working demos every 4–6 weeks, showcasing real deliverables.
    *

    Ongoing community visibility and documentation of all development efforts.

    These commitments far exceed the transparency baseline expected of Treasury-funded initiatives.

    The proposal seeks ₳1.5 million to fund 6 full-time contributors over six months. This includes a 25% contingency for complexity and overhead, based on a $0.50/ADA conversion rate. The networking scope, already funded via Catalyst, is excluded from this ask.

    In relative terms, this is a small investment for a high-impact project, especially considering that community-signaled proposals totaling over ₳275 million is also up for vote.

    Rejecting the Amaru Node proposal would have negative ripple effects:
    *

    It would delay node diversity, exposing Cardano to prolonged infrastructure fragility.
    *

    It would discourage developers from engaging in critical protocol-level work.
    *

    It would undermine the credibility of the on-chain governance and treasury processes we are working to legitimize.
    *

    It could stifle future-forward innovation, such as light clients, WASM support, and modular architecture.

    The message it would send is that even the most constitutionally aligned, community-driven, technically sound proposals are not safe from political or procedural paralysis.

  • Yes10.9M ₳No rationale
  • No10.8M ₳No rationale
  • Abstain9.6M ₳No rationale
  • Yes8.8M ₳Rationale

    本提案に賛成票を投じます。\n\nRustによる新たなノード実装は、Haskellノードへの依存を減らし、多様性を高めるものです。信頼ある5団体がPRAGMAの枠組みで推進しており、モジュール性の高い設計、シームレスな操作性、低いハードウェア要件はSPOや開発者の参加しやすさを高めることを意図しています。Cardanoの回復力と分散性を強化する取り組みとして、本提案を支持します。\n\nI vote YES on this proposal.\n\nThis proposal improves node diversity by implementing a new Rust-based node, reducing reliance on the existing Haskell implementation. Led by five trusted entities under a clear governance framework (PRAGMA), it emphasizes a modular design, seamless user experience, and low hardware requirements - which are intended to improve accessibility for SPOs and developers. I support this effort to strengthen Cardano’s resilience and decentralization.

  • Yes8.1M ₳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.6M ₳No rationale
  • Yes6.4M ₳No rationale
  • Yes5.9M ₳Rationale

    I'm fully supportive of node diversity on Cardano. This is something we can work on while doing other developments in the ecosystem that are just as important. I'd prefer to see a completed smart contract to reference for future treasury withdrawals, however the roadmap on how it's going to be laid out and the team working on it is sufficient for now.

  • Yes5.8M ₳No rationale
  • Yes5.4M ₳No rationale
  • Yes4.8M ₳No rationale
  • Yes4.7M ₳No rationale
  • Yes4.6M ₳No rationale
  • Yes4.6M ₳No rationale
  • Yes4.4M ₳No rationale
  • No4.2M ₳No rationale
  • Yes4.1M ₳No rationale
  • Yes4.1M ₳Rationale

    [Portuguese]
    Optamos por votar "Sim" nesta ação de governança (gov_action1h4ygjv0hjfj3lmafcm76rpdzcm8vsvj9k5wejn3npyxwxm3fesnqqw9kxxz), 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_action1h4ygjv0hjfj3lmafcm76rpdzcm8vsvj9k5wejn3npyxwxm3fesnqqw9kxxz) 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
  • YesRevoted3.8M ₳History

    Earlier votes

    Yes1y agoSuperseded

  • Yes3.7M ₳Rationale

    Node diversity has been a long time coming. An easy yes from me.

  • Yes3.4M ₳No rationale
  • Yes3.1M ₳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.

  • Yes3M ₳No rationale
  • Yes2.8M ₳No rationale
  • Yes2.8M ₳No rationale
  • Yes2.7M ₳No rationale
  • Yes2.7M ₳No rationale
  • No2.6M ₳No rationale
  • Yes2.6M ₳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.

  • 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.3M ₳No rationale
  • Abstain2.1M ₳No rationale
  • Yes2.1M ₳No rationale
  • Yes2M ₳No rationale
  • Yes1.9M ₳No rationale
  • Yes1.9M ₳No rationale
  • Yes1.8M ₳No rationale
  • Abstain1.7M ₳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.7M ₳No rationale