The Ledger
Mina Sets Out a 55 Million MINA Treasury Rollout With Aragon
Mina Foundation plans to introduce an onchain treasury in three deployments, starting with 1 million MINA and aiming to make about 55 million available. Aragon will operate the treasury application for 24 months, while MINA holders vote on funding proposals under staged safeguards.

“The DT will be introduced progressively. An initial allocation will be deployed with defined governance and security safeguards.”
Aragon, MinaResearch
Mina Foundation plans to place its decentralized treasury under onchain governance through a staged rollout totaling approximately 55 million MINA. In a post published October 23, Aragon set out the proposed deployment sizes, voting process and temporary controls, and said it would provide operational stewardship during the treasury’s initial period.
The plan begins with 1 million MINA in a Test Phase, followed by a Scale Up Phase targeting 20 million and a Final Deployment of up to 34 million MINA. Mina Foundation and Aragon say deployment will follow remaining readiness work; the post does not give a launch date. Parameters for each phase, including participation settings, will be confirmed before that deployment goes live.
Three deployments, with larger voting requirements
The staged funding is intended to limit exposure at launch and give the project time to observe proposal activity and voter participation before making more MINA available. The transition out of the Test Phase can happen when its treasury is spent, two consecutive proposals pass or two months have elapsed since launch. The Scale Up Phase can transition when its funds are spent, three consecutive proposals pass or three months pass from its start.
Requests will face participation and approval thresholds that rise with their size relative to the treasury in that deployment. The framework sets default participation requirements from 20% for smaller requests to 50% for a request equal to the treasury, before a deployment-specific modifier; approval requirements rise from 51% to 70%. Abstentions count toward participation but not toward the yes-versus-no approval calculation.
The post gives an example for a request equal to 10% of its deployment’s treasury: 40.68% participation and 60.99% approval, before the modifier. The actual settings for each deployment remain to be confirmed. Mina’s voting power is concentrated, the post says, with the top 10 validators accounting for approximately 32.95%.
Aragon’s key and the temporary veto
During the Test Phase, Aragon will deploy the Mina-native zkApp and hold its deployment key, called the Steward Key. With written approval from Mina Foundation, that key can return treasury funds to the Foundation in an emergency, allowing redeployment if parameter errors or other failure modes arise. The same emergency-return safeguard remains during the Scale Up Phase.
A separate “Break Glass” mechanism can veto proposals on defined grounds, including serious legal violations, failed recipient screening, credible threats to treasury funds, compromised voting and technical errors that could cause unintended execution. Three of five signers must approve an intervention; the initial seats are divided three for Mina Foundation and two for Aragon. The post describes the default as non-intervention and says each action must be publicly justified and documented.
In the final deployment, the plan says treasury funds will move only through passed proposals, with no emergency return. The Break Glass safeguard will remain at first. Once approved removal conditions are met, its signer keys will be sent to a burn address and Aragon’s Steward Key will be destroyed.
Four-week proposal cycle, offchain identity checks
Each proposal moves through submission, community exploration, voting and cooldown, with each stage lasting one Mina epoch. After the Mesa mainnet hardfork, an epoch is approximately one week, making a full proposal cycle about four weeks. Voting is open to validators and individual MINA holders with self-delegation, and votes must appear in at least five different slots for a proposal to be tallied.
Recipients must complete identity and sanctions screening before funds are paid out. Verification is handled by a Foundation-approved independent provider; identity and corporate records stay offchain and are not shared with Aragon or treasury participants, according to the post. For the Test Phase, proposers also provide a bond equal to 1% of the request: it is paid out with the approved amount when that proposal executes, but stays in the treasury if the proposal fails, misses participation requirements or is vetoed.
A 24-month operating role, with terms still subject to change
Aragon says it will operate the treasury application and the infrastructure that keeps it synchronized with Mina chain state for an initial 24 months under its agreement with Mina Foundation. The post also says the application has undergone audits and testing across mainnet, devnet and purpose-built datasets. It describes the current plan as a progress update, not a final deployment specification: terms and parameters, including the bond, may change before launch.
The design therefore puts two kinds of control side by side: MINA holders decide whether funding proposals pass, while temporary signers retain narrow intervention powers during the staged rollout. Those safeguards are scheduled to recede only after the final deployment meets the conditions for removing them; the post says the specific settings for each deployment will be confirmed before it goes live.
Sources
- Original source MinaResearch forums.minaprotocol.com