Governance ReviewNo. 33Epochs 624 to 6269 Apr 2026 to 24 Apr 2026
₳50M for the Orion Fund is paid, and the Foundation is backed to run Catalyst
The treasury paid ₳57.7M in epochs 624 to 626, ₳50M of it in one withdrawal for the first tranche of the Orion Fund, an investment vehicle that proposes to return capital to the treasury over time. Two smaller payments followed one epoch later: Dingo, a block producing node written in Go, and the Cardano Defi Liquidity Budget, the legal and technical setup of a liquidity budget. In the same window DReps backed the Cardano Foundation's proposed takeover of Project Catalyst with 83.4% of DRep power, in a vote that binds nothing on chain. Nine treasury requests asking for ₳162.1M together arrived in one transaction in epoch 626.
Orion receives its first ₳50M tranche
Cardano x Draper Dragon: Orion Fund drew ₳50M from the treasury at the start of epoch 624, the largest single withdrawal since the ₳70M paid in epoch 606. It had been ratified at the start of epoch 623, before this window, on 74.9% of DRep power, and the vote itself is in the review of epochs 621 to 623. The shares in this edition are the yes power as a share of all counted power, with abstaining power left out and power that cast no ballot counted as no.
The money is the first tranche of a multi-year investment fund. The proposal describes a vehicle managed by Draper Dragon that invests in companies built on or connected to Cardano, draws on the treasury in capped tranches, and proposes to return capital to the treasury over time. The voters who backed it wrote about that return. The Cardano Foundation called it “one of the few proposals that actively seeks to grow the Treasury”, with 90% of the money deployed into the ecosystem, about 10% for operating costs including a 1.3% management fee, and no profit share for the general partner “until Treasury contributions are recouped”. The Eternl DRep Committee wrote that Draper “is an established entity” and that the proposal “favors the Cardano treasury over its own profit”. YUTA wrote that it “was not an easy decision, but the discontinuation of Catalyst became the final push”, and that it may be time to try a different approach. The treasury balance fell by ₳46.1M between the readings at epoch 623 and epoch 624, the payment less the epoch’s inflow.
Treasury balance, epochs 604 to 626
In billions of ada
A node in Go and a liquidity budget
Dingo and Cardano Defi Liquidity Budget were ratified at the start of epoch 624 and paid at the start of epoch 625, ₳7.7M together. Dingo took ₳6.9M for a new block producing node from Blink Labs, on 70.3% of DRep power from 133 yes votes, 59 no and 13 abstain. Its document describes twelve months of engineering on a node written in Go, which it places next to Amaru as a second independent implementation, priced at thirty cents per ada and paid in one go into an escrow contract that releases money against milestones and returns what is unused to the treasury at the end of its term.
The yes votes were about cost and diversity. YUTA wrote that it had run the node on the main network, that Go is easier for pool operators to evaluate than Haskell, and that “price competition in node development is extremely important”, setting three twelve month node budgets side by side: $48.4M for the existing node, $3.04M for Amaru, $2.07M for Dingo. The Eternl DRep Committee wrote that it had revised its vote on Dingo from no to yes and would support the Haskell, Rust, Go and TypeScript implementations alike, because more than one additional node is needed for them to check each other. Sebastien Guillemot セバ voted yes and called it “a hard decision”: the team had done impressive work, but Go over Rust was “a very unfortunate choice” for interoperability with the cryptography ecosystem.
The liquidity budget took ₳800,000 on 74.1%, a second try after an untitled, smaller request from the same budget had expired in epoch 614 with six committee votes against it, which the review of epochs 612 to 614 covers. The revised request lists the circumstances under which funds return to the treasury and discloses that the recipient has received no treasury ada in the previous two years, the two omissions the committee had named, and it spends the money on a legal entity, an audit of the contract and a multisig, within six months. The committee was unanimous on both payments. The Cardano Foundation commended the staged budgeting and “strongly urge[d] the resolution of outstanding transparency, operational, and security concerns” before the ₳50M withdrawal that the budget plans next. The Eternl DRep Committee wrote that costs “are higher than previously, but they need to start somewhere”. Across the three epochs the treasury paid ₳57.7M in all, and by epoch 626 four withdrawals had drawn ₳67.8M of the ₳350M ceiling for the spending period that began at epoch 613.
The Foundation is backed to run Catalyst
Approve Cardano Foundation as New Managing Entity of Project Catalyst closed at the start of epoch 626 with 83.4% of DRep power behind it, on 186 yes votes, 11 no and 4 abstain. Six committee members voted yes and one abstained. The stored pool tally holds 22 yes ballots and 2 no, with the yes side at 5.5% of stake, and only one of those pool ballots was cast inside this window, in epoch 625.
What it asks is whether the Cardano Foundation should take over the running of Project Catalyst, the community grants programme, from Input Output Group, which had run it and backs the handover. The point of asking now is continuity: teams funded in rounds ten to fourteen still need milestone reviews and payments, and those do not pause while an organisation changes. The proposal puts a date on it, saying that without approval by the end of May the operations would likely pause and disbursements be delayed, and it sets its own bar at more than 50% of the active DRep voting stake. It also says what happens to the money already set aside for the two rounds after those: if approved, the Foundation will work with Intersect to return the treasury allocations approved for rounds fifteen and sixteen to the treasury.
YUTA and the Eternl DRep Committee treated it as a formality. YUTA wrote that there is “no merit” in voting no and that the return of the money for rounds fifteen and sixteen should proceed. The Eternl DRep Committee wrote that there was “not much to approve here” and that if the two parties had agreed it did not see the point in spending time and ada on a vote. KtorZ, the committee member who abstained, called the action “a literal poll” on a community matter, out of the committee’s scope, and noted that as an employee of the Foundation some could see a conflict of interest. One stake pool wrote that Catalyst “has been in a bumpy state lately” and that the Foundation is in a position to manage it responsibly.
This is an information vote supporting an off chain transition, which is a different thing from a vote the ledger executes. The vote supports the handover, and the organisations still have to carry it out, which is the agreement they asked for before proceeding. The proposal is also explicit that the manager of Catalyst and the administrator of the ecosystem budget are separate roles, and that this changes only the first.
Nine requests for ₳162.1M
In the last epoch of the window nine treasury requests were filed together in one transaction, which changes nothing about how they are decided: each is a separate proposal with its own tally, its own committee ruling and its own deadline. They asked for ₳162.1M between them, from ₳3.6M to ₳62.1M apiece, and all nine were still open when the window closed, alongside two earlier requests. Their voting is in the review of epochs 630 to 632. For the treasury, the window ended with ₳67.8M of the ₳350M limit used and ₳162.1M more on the ballot.
The window recorded 496 ballots across the roles, superseded votes included, 148 DReps cast a final ballot somewhere in it, and the count with a ballot in the last 12 epochs read 260 at epoch 626.
Decided in this window
| Action | Outcome | DRep yes |
|---|---|---|
| Cardano x Draper Dragon: Orion Fund | Enacted 624 | 74.9% |
| Cardano Defi Liquidity Budget - Withdrawal 1 | Enacted 625 | 74.1% |
| Dingo: a Production-Grade Block Producer in Go by Blink Labs | Enacted 625 | 70.3% |
| Approve Cardano Foundation as New Managing Entity of Project Catalyst | Closed 626 | 83.4% |
The numbers behind the window
- Delegated to DReps, at the start of epoch 624
- ₳5.82B
- Delegated to DReps, at the start of epoch 626
- ₳5.81B
- Votes cast in the window, superseded votes included
- 496
- DReps whose final ballot fell in the window
- 148
- Treasury, at the start of epoch 624
- ₳1,617.4M
- Treasury, at the start of epoch 626
- ₳1,617.4M
- DRep shares are the share of counted power: abstaining power is left out, while power that cast no ballot and power delegated to the always no confidence option are folded into the no side. Stake pool shares on an information action are the share of stake behind yes ballots.
- The Orion Fund withdrawal was ratified in the window before this one and paid in this one, so its row carries the payment.
- Nine requests submitted in epoch 626 and two submitted earlier were still open at the close of the window and are not in the table.
- What the Orion Fund and the Catalyst transition are for is read from the metadata the proposals themselves carry, not from the data pack.
- Votes cast is every ballot of epochs 624 to 626 across all three roles, superseded votes included. The count of DReps with a recent ballot carries a reliability flag in the data.
Sources and further reading
16 sources, open the list
- YUTA voted yes on the Orion Fund, writing that it was not an easy decision, that the discontinuation of Catalyst became the final push, and that it may be time to try a different approach from Catalyst. the rationale of YUTA on the Orion Fund
- The Cardano Foundation voted yes on the Orion Fund, writing that it is one of the few proposals that actively seeks to grow the treasury, that 90% of the funds are deployed into the ecosystem while about 10% covers operational expenses including a discounted 1.3% management fee, and that the general partner receives no profit share until the treasury's contributions are recouped. the rationale of the Cardano Foundation on the Orion Fund
- The Eternl DRep Committee voted yes on the Orion Fund, writing that Draper is an established entity, that the proposal favours the Cardano treasury over its own profit, and that outside entities need to be given a chance. the rationale of the Eternl DRep Committee on the Orion Fund
- YUTA voted yes on the Go node, writing that it had run it on the main network, that a node written in Go is easier for pool operators to evaluate than one in Haskell, that price competition in node development is extremely important, and comparing three twelve month node budgets at 48,400,000 dollars for the existing node, 3,040,000 for Amaru and 2,070,000 for Dingo. the rationale of YUTA on the Go node
- The Eternl DRep Committee voted yes on the Go node, writing that it had revised its vote from no to yes and that, for node diversity, it would support the Haskell, Rust, Go and TypeScript implementations, because more than one additional implementation is needed for the nodes to check each other. the rationale of the Eternl DRep Committee on the Go node
- Sebastien Guillemot voted yes on the Go node, writing that the team had done impressive work and was furthest along in tackling developer agility at the protocol level, that Go over Rust was a very unfortunate choice for interoperability with the cryptography ecosystem, and that voting yes was a hard decision taken to move things forward. the rationale of Sebastien Guillemot on the Go node
- The Cardano Foundation voted yes on the first liquidity withdrawal, writing that it commends the staged budgeting and the more realistic exchange rate of twenty five cents per ada against the forty cents used in earlier projections, and strongly urges the resolution of outstanding transparency, operational and security concerns before the subsequent ₳50M withdrawal. the rationale of the Cardano Foundation on the first liquidity withdrawal
- The Eternl DRep Committee voted yes on the first liquidity withdrawal, writing that in line with its yes on the budget it also backs the first withdrawal, that costs are higher than previously, but that they need to start somewhere. the rationale of the Eternl DRep Committee on the first liquidity withdrawal
- YUTA voted yes on the Catalyst handover, writing that there is no merit in voting no and that the return of the funding for rounds fifteen and sixteen to the treasury should proceed. the rationale of YUTA on the Catalyst handover
- The Eternl DRep Committee voted yes on the Catalyst handover, writing that there was not much to approve and that if the two parties had agreed it did not see the point in spending time and ada on voting on the action. the rationale of the Eternl DRep Committee on the Catalyst handover
- KtorZ abstained on the Catalyst handover, writing that the action is a poll asking the community for feedback on a community matter, out of scope for the committee, and that as an employee of the Foundation some could see a conflict of interest. the rationale of KtorZ on the Catalyst handover
- One stake pool voted yes on the Catalyst handover, writing that Catalyst had been in a bumpy state lately and that the Cardano Foundation is in a position to manage the fund in a responsible and positive direction. the rationale of a stake pool on the Catalyst handover
- The Catalyst proposal records that the Cardano Foundation, supported by Input Output Group, asks for community approval to become the new managing entity for Project Catalyst, transferring operations and responsibilities from the outgoing organisation in accordance with the statutes of the company that holds Catalyst. Its stated purpose is continuity of operations and the avoidance of delays to milestone reviews and eligible payouts for teams delivering against projects in funds ten to fourteen, and it states that the request is unrelated to the role of Intersect as budget administrator. It says that without approval by the end of May the operations would likely pause and disbursements be delayed, that the Foundation will work with Intersect to return the treasury allocations already approved for funds fifteen and sixteen, and that it counts as approved if more than 50% of the active DRep voting stake votes yes by its expiry. the document behind the Catalyst handover
- The first liquidity withdrawal asks ₳800,000 to set up a legal entity, audit the contract and stand up the multisig the stablecoin liquidity budget needs, within six months, and it lists the circumstances under which funds return to the treasury and discloses that the recipient has received no treasury ada in the previous two years. the document behind the first liquidity withdrawal
- The Go node request asks ₳6.9M for twelve months of engineering on a block producing node written in Go, priced at thirty cents per ada, paid in one withdrawal into an escrow contract that releases funds against milestones and returns unused ada to the treasury at the end of its term, and it places the node next to Amaru as a second independent implementation. the document behind the Go node request
- The Orion proposal describes a multi year, tranche based investment fund managed by an external general partner, investing in Cardano native and Cardano integrated companies, with net proceeds from the direct investments to be returned to the treasury on a repayment schedule and treasury exposure described as incremental, capped and governed. the document behind the Orion fund