Treasury
Scopes
Amaru's treasury for 2025 is divided in 4 treasury buckets, each covering a different scope of work. Each scope has a dedicated owner whose role is to oversee the expenditure of the budget in that work area.
Consensus
Covers implementation of the Ouroboros family of blockchain consensus protocols, as well as work done around deterministic simulations thereof.
Ledger
Transition rules and state management pertaining to Cardano, including the execution of smart contracts (i.e. Plutus Virtual Machine).
Mercenaries
Adhoc missions and short workstream necessary to the support of Amaru's core activities.
Marketing
Promotions, socials and coordinating events related to Amaru, such as the Node Diversity workshops.
An additional special sub-treasury is reserved for contingency, and is collectively overseen by all scopes owners.
Off-chain, a series of agreements provides a legal framework to remunerate contributors according to agreed-upon missions and deliveries. These Remunerated Contributor Agreements are tied together by PRAGMA's Maintainer Committee Framework.
On-chain Process
The Amaru maintainer committee ensures direct administration of its budget, assisted with an on-chain smart contract.
The smart contract's role is to ensure that the expenditure of funds is done in accordance with the scope defined in this budget and authorized by the relevant scope owners. We recognize the following capabilities of this contract:
Standard withdrawal
A scope owner initiates money withdrawal from their treasury, with another scope owner approval.
Contingency withdrawal
A scope owner asks all other scope owners to withdraw an amount from the contingency funds.
Scope reconciliation
A scope owner asks other scope owners for a change of ownership (or a reallocation of budget).
Contingency refund/closing/failsafe
Any leftovers from scopes or from the contingency budget can be sent back to the Cardano treasury after an ageed-upon delay.
Credential rotation
In case of lost credentials or the departure of a scope owner, a mechanism allows the rotation of credentials to a new scope owner upon approval by all (5 out of 5) PRAGMA members.