Skip to main content

Mina

Mina Foundation sets out how its 55M MINA on-chain treasury will launch

A framework published on 23 October 2026 describes the Mina Decentralized Treasury: a zkApp where validators and self-delegating MINA holders vote on funding proposals. It launches with a 1M MINA test phase and grows to about 55M MINA in three deployments.

Mina Foundation is preparing to deploy the Mina Decentralized Treasury (DT). This is an on-chain fund that MINA holders control by vote. On 23 October 2026, Aragon, which is running the launch for the Foundation, published the deployment framework on the Mina forum. It sets out how proposals will work, who can vote and how the treasury will be released. The framework gives no launch date. It says the values for each deployment will be confirmed before that deployment goes live.

How proposals work

The treasury runs as a Mina zkApp. It tallies votes from Mina chain state and pays out approved proposals. Each proposal goes through four stages, and each stage lasts one Mina epoch, about a week since the Mesa hard fork:

  1. Submission of the proposal and its on-chain payload.
  2. Exploration, while the community reviews it.
  3. Voting. Validators and MINA holders who delegate to themselves can vote. Votes must be recorded in at least five different slots for the proposal to be tallied.
  4. Cooldown, before an approved proposal is executed.

The whole process takes about four weeks. In the test phase, a proposer puts up a bond of 1% of the amount requested. The bond is paid out with the funds if the proposal executes and stays in the treasury if it doesn't.

Thresholds and safeguards

How many tokens must take part in a vote, and how large a yes share is needed, both rise with the size of the request. Yes, no and abstain votes all count towards participation. In a later forum reply, Aragon said that in the test phase a small request needs about 1% of supply to take part, rising to 2.5% for a request of the full 1M MINA. A request for a whole deployment needs 70% approval.

The treasury, about 55 million MINA in all, is released in three deployments:

  • Test phase: 1M MINA.
  • Scale-up phase: about 20M MINA.
  • Final deployment: up to 34M MINA.

The treasury moves to the next deployment when its funds are spent, when two (later three) proposals pass in a row, or after two (later three) months, whichever comes first.

During the first two phases, a "Break Glass" safeguard can veto proposals on published grounds. In an emergency, and with the Foundation's written approval, a key held by Aragon can return the funds to Mina Foundation. In the final deployment, funds can move only through passed proposals. The Break Glass keys are to be burned once agreed conditions are met.

What it means for validators and delegators

Validators and self-delegating holders vote with their stake. The framework notes that voting power is concentrated: the top 10 validators hold about 32.95% of it. Delegators who want a direct vote need to delegate to themselves. Otherwise their influence runs through the validator they delegate to. BitBasic's Mina dashboard and block producer list show how stake is spread.

Sources