Amaru Treasury Withdrawal 2026
6 of 7 committee members voted
- Ace Alliance71aa5b3a…8f04YesActive · term ends epoch 726Rationale
Ace Alliance finds the proposed “Amaru Treasury Withdrawal 2026” Governance Action Constitutional. Rationales are archived at https://github.com/ace-alliance/ace-voting/
A PDF version of this rationale is also made available.
This Treasury Withdrawal Governance Action (TWGA) seeks ₳10,142,000 to support Amaru’s 2026 work towards an interoperable, block-producing Cardano node implementation, with milestones extending from January through December 2026. The proposal’s central aim is to bring Amaru to production readiness by achieving feature parity with the Haskell node, beginning with a relay-capable node able to follow chain selection, diffuse transactions and blocks, and fully validate ledger compliance. It also proposes continued hardening of the system through work on the mempool, performance, observability, and, ultimately, safe block-production capability, while maintaining interoperability and usability on lower-resource hardware.
Article II.6 requires governance actions to be submitted in a standardized and legible format, supported by immutable off-chain documentation, and accompanied by sufficient rationale, including a title, abstract, justification, and supporting materials. On its face, this proposal satisfies those requirements. It was submitted in a standardized format, provides both a URL and hash for immutable off-chain content, and includes the required abstract, rationale, and supporting materials.
Article II.7 imposes additional requirements specific to TWGAs, and the proposal addresses each of them. It identifies the purpose of the withdrawal, specifies the 2026 delivery period, describes the cost structure and refund conditions, and discloses prior treasury funding received within the last 24 months It also provides for periodic independent audits and oversight metrics, designates administrators known to the community who are working through a smart contract, and states that treasury funds will be held in five separate script-controlled accounts that are auditable by the community and delegated only to the predefined abstain governance option rather than to a DRep or SPO. We apply Article II.7.3, requiring “A Net Change Limit must be set” and “Treasury Withdrawals actions must not exceed the Net Change Limit for that period,” concluding this is not a barrier to this action’s constitutionality. See Precedent Discussion, below.
Ace Alliance finds the proposed “Amaru Treasury Withdrawal 2026” Governance Action constitutional, so long as the requisite CC affirmation threshold is met at the conclusion of voting.
- Cardano Curia84feba94…6bd5YesActive · term ends epoch 799Rationale
The Constitutional Committee finds the Amaru 2026 Treasury Withdrawal constitutional, subject to final submission meeting immutability and auditability requirements.
What is being proposed
This governance action proposes a Treasury Withdrawal to fund Amaru’s 2026 work program (January–December 2026), including development toward a relay-capable node (Q1), block-producing capability (by end of Q2), protocol R&D prototypes, and ecosystem integrations, administered through a smart-contract-controlled treasury with PRAGMA maintainer committee oversight.
Constitutional and guardrails consistency (v2.4)
A Treasury Withdrawal is constitutional when it is properly specified, auditable, and consistent with guardrails on format, denomination, and oversight. The proposal describes:
- a defined purpose and delivery period (2026);
- scoped costs (FTE-based + fixed costs) and a volatility buffer policy with unused funds intended to be returned;
- governance/administration via segregated script accounts and multi-scope approvals;
- auditability measures (public journal, independent audit provisions).
Determination (with conditions)
YES on constitutionality, contingent on final submission including immutable URLs and hashes for the canonical 2026 proposal plus annexes (2025 retrospective, prior withdrawal evidence, and TxPipe audit), with translations clearly marked as translations, and with retroactive work mapped to dated deliverables and invoices for auditability.
For the reasons above, the Constitutional Committee finds the action constitutional under Constitution v2.4 provided the final submission includes immutable URLs + hashes for the canonical proposal and annexes, translations are clearly marked as translations referencing the canonical hash, and any retroactive work is mapped to dated deliverables and invoices for auditability.
- Cardano Japan Council725d4d44…7b31YesExpired · term ends epoch 653Rationale
We consider this governance action to be constitutional.
This proposal satisfies the formal requirements for governance actions set forth in Article II, Section 6 (Governance Action Standards) of the Cardano Constitution, and is presented via an immutable off-chain document (IPFS). Furthermore, the proposal is submitted under Article II, Section 7 (Treasury Withdrawal Action Standards) and specifies the purpose of the funds, the implementation period, the breakdown of costs, and the conditions for returning unused funds. Based on these points, no clear conflict with the Constitution has been identified. Accordingly, this proposal is considered constitutional. However, the proposal includes a contingency allocation to account for potential price fluctuations. Appropriate transparency in its implementation and reporting will therefore be important.
For the reasons stated above, we determine that it is constitutional.
- Phil_uplc68bb0b42…8746YesActive · term ends epoch 799Rationale
- Tingvard646d1b3a…be43YesActive · term ends epoch 726Rationale
Tingvard judges this governance action constitutional.
This governance action is a treasury withdrawal under the Cardano Constitution and must therefore satisfy the requirements of Article II, § 6 and Article II, § 7, in addition to the applicable Treasury Guardrails in Appendix I.
Under Article II, § 6, governance actions must be presented in a standardized, legible format, include a title and abstract, and reference supporting materials in a manner that ensures clarity and immutability. This proposal includes a clear title, abstract, motivation, and detailed rationale. Supporting documents are referenced using content-addressed ipfs:// URIs, satisfying the constitutional expectation that referenced off-chain materials be immutable and verifiable. The submission is therefore compliant with Article II, § 6.
Article II, § 7.1 requires treasury withdrawals to specify:
(a) a clear withdrawal purpose;
(b) a defined delivery period;
(c) relevant costs and expenses; and
(d) circumstances under which funds may be refunded to the treasury.
The proposal clearly defines its purpose: funding development, testing, integrations, security audits, and operational support for the Amaru node implementation throughout calendar year 2026. It specifies a 12-month delivery period (January–December 2026), includes a detailed cost breakdown (FTE allocations, fixed costs, and contingency), and describes mechanisms for returning unspent funds to the treasury at the conclusion of the budget period. These elements satisfy Article II, § 7.1.
Article II, § 7.2 requires disclosure of prior withdrawals within the preceding 24 months. The proposal explicitly acknowledges a prior treasury withdrawal in 2025 and references it. This satisfies the disclosure requirement.
Article II, § 7.3 requires compliance with the applicable Net Change Limit (NCL). The currently active NCL for Epochs 613–713 has been set at 350 million Ada and the limit has not been met. The requested ₳10,142,000 remains well within that ceiling. Therefore, this proposal does not violate the NCL requirement under Article II, § 7.3 and the Guardrail TREASURY-02a.
Article II, § 7.4 requires provision for periodic independent audits where applicable. The proposal includes budgeting for security audits and commits to external financial auditing, with publication of reports. This satisfies the constitutional audit requirement.
Article II, § 7.5 requires that a treasury withdrawal specify an administrator and describe the administration process. The proposal designates a maintainer committee operating under a defined legal framework and supported by an on-chain treasury smart contract. It describes multi-party authorization procedures, scope ownership, contingency controls, credential rotation, and refund mechanisms. This satisfies the administration requirement.
Article II, § 7.6 requires treasury oversight and traceability. The proposal commits to on-chain management via script-controlled accounts and to maintaining a public expenditure journal, thereby ensuring visibility and auditability. These measures align with the oversight requirement.
The proposal also complies with Guardrail TREASURY-03a by denominating the request in Ada.
Finally, the proposal aligns with Article I, § 1 (Tenets), particularly those requiring sustainability, responsible stewardship of resources, and preservation of decentralization and resilience. Funding an alternative node implementation, security testing, and node diversity initiatives is consistent with strengthening the long-term robustness of the Cardano blockchain.Tingvard judges this governance action constitutional. The proposal satisfies Article II, § 6 and Article II, § 7 of the Cardano Constitution, complies with the applicable Treasury Guardrails in Appendix I, remains within the active Net Change Limit for Epochs 613–713, and aligns with the Tenets set forth in Article I, § 1.
- KtorZ64f97568…3a49AbstainExpired · term ends epoch 653Rationale
Conflict of interest: I am one of the proposers.
Abstaining due to an apparent conflict of interest: I am one of the proposers.
- Eastern Cardano Council4a822702…3d76Not votedActive · term ends epoch 726No rationale