⚠ Preprod testnet

Governance ReviewNo. 36Epochs 633 to 63524 May 2026 to 8 Jun 2026

Nine Cardano treasury requests submitted together, six paid

Six of nine treasury requests submitted together were paid in epoch 634, totalling ₳131.5M, while three expired. Developer Experience passed narrowly after Yoroi and EMURGO changed from abstain to yes. Pogun, Blockfrost and Midgard Labs did not secure funding.

₳131.5M
paid out of the treasury in epoch 634 alone, across six withdrawals
₳62.1M
the largest of them, for a maintenance programme
31.4%
behind the scalability request in the same transaction, which expired
₳1.51B
left in the treasury at epoch 635, the lowest since epoch 508

Nine requests, one transaction

Nine treasury requests shared a transaction and a deadline. They were submitted together in epoch 626, and their voting closed at the start of epoch 633. The Constitutional Committee, which votes only on whether an action is constitutional, found no fault with any of the nine, seven yes votes each. Seven of the nine were filed by Input Output, alone or with a partner firm, and each names Intersect to hold the money and release it against milestones, with anything unspent going back to the treasury. Blockfrost and Pogun filed the other two.

Six were ratified and paid one epoch later, ₳131.5M together in epoch 634. IO: Consensus Initiative drew the strongest support of the nine at 88.0% of DRep power, ₳27.7M to take the Leios throughput upgrade from its public testnet to a release candidate. IO: Cardano Upgrades took 86.4% for account addresses that can receive direct deposits, the design of a treasury able to hold stablecoins, and paying transaction fees in assets other than ada. The largest sum, ₳62.1M for the maintenance programme run with Ensurable Systems, nine areas from bug fixing and security reviews to release management, took 82.3%. The narrowest pass was IO: Developer Experience Initiative at 67.9%, less than a point over the 67% a withdrawal needs, and the smallest request in the set at ₳3.6M.

Three expired, and together they had asked for ₳30.6M. Pogun reached 35.7% for a bitcoin lending market, a yield layer and a bridge, with a promise to return 20% of its earnings to the treasury until the funding is repaid and 5% after that. Midgard Labs reached 31.4% for layer two scaling work, the hardening of Hydra and an optimistic rollup. Blockfrost reached 24.2% for an indexer that would let an operator serve a slice of the chain and a subsidy for its free tier. The three that expired received at most 35.7% of DRep power, the six paid ones at least 67.9%.

The nine requests, funding asked and DRep support

Amount requested against the DRep yes share of counted power

Paid or ratifiedExpired
0.0%25.0%50.0%75.0%100.0%10M100MAmount requested67.0% barConsensus Initiative: 27.7M, 88.0%Consensus InitiativeCardano Upgrades: 13.1M, 86.4%Cardano UpgradesHigh Assurance: 13.1M, 84.2%High AssuranceEnsurable Systems: 62.1M, 82.3%Ensurable SystemsVacuumLabs: 11.9M, 71.5%VacuumLabsDeveloper Experience: 3.6M, 67.9%Developer ExperiencePogun: 12.3M, 35.7%PogunMidgard Labs: 10.4M, 31.4%Midgard LabsBlockfrost: 7.9M, 24.1%Blockfrost
Ensurable Systems received 82.3% support for its ₳62.1M request. Pogun's ₳12.3M request expired at 35.7%. Developer Experience passed narrowly at 67.9%.

Why Yoroi and EMURGO changed their votes on Developer Experience

The Eternl DRep Committee published a single rationale for all of them, a checklist with a yes, a no or an abstain against each title. It backed the consensus work and the maintenance programme and voted no on the scaling plan and on the developer experience request that the DReps as a whole let through.

Yoroi and EMURGO changed from abstain to yes on the Developer Experience request. Yoroi W₳llet wrote that it was revising its earlier abstention to a yes on the developer experience request because developer experience is time sensitive and a further delay would be material, and that its yes on the VacuumLabs Plutus work was also a change from an earlier abstention. EMURGO wrote the same on the developer experience request, adding that “the proposal has not changed” and that it did not withdraw its concerns about attribution and third party coordination. At 67.9% the request had less than a point to spare.

YUTA voted no on the scaling plan, writing that Hydra “makes up 80% of this proposal”, had received significant investment in the past, and that it was “hard to envision a future” in which it drives transaction volume. On Blockfrost, YUTA wrote that the service is better positioned as one competing with other providers than as a public service, and Yoroi and EMURGO abstained on it and on Pogun over the structure of the requests and the scale of the commitment. Sebastien Guillemot セバ abstained on Pogun with one line: he likes many of the ideas, but generally abstains on commercial proposals.

The five largest DReps on the nine requests

One cell per final vote

YesNoAbstainDid not vote
YoroiYUTABlockdaemonEMURGOEternl DRepCommitteeDeveloper ExperienceYoroi on Developer Experience: Yes✓YUTA on Developer Experience: Yes✓Blockdaemon on Developer Experience: Yes✓EMURGO on Developer Experience: Yes✓Eternl DRep Committee on Developer Experience: No✕Cardano UpgradesYoroi on Cardano Upgrades: Yes✓YUTA on Cardano Upgrades: Yes✓Blockdaemon on Cardano Upgrades: Yes✓EMURGO on Cardano Upgrades: Yes✓Eternl DRep Committee on Cardano Upgrades: Yes✓Consensus InitiativeYoroi on Consensus Initiative: Yes✓YUTA on Consensus Initiative: Yes✓Blockdaemon on Consensus Initiative: Yes✓EMURGO on Consensus Initiative: Yes✓Eternl DRep Committee on Consensus Initiative: Yes✓Ensurable SystemsYoroi on Ensurable Systems: Yes✓YUTA on Ensurable Systems: Yes✓Blockdaemon on Ensurable Systems: Yes✓EMURGO on Ensurable Systems: Yes✓Eternl DRep Committee on Ensurable Systems: Yes✓Midgard Labs scalingYoroi on Midgard Labs scaling: Abstain−YUTA on Midgard Labs scaling: No✕Blockdaemon on Midgard Labs scaling: Abstain−EMURGO on Midgard Labs scaling: Abstain−Eternl DRep Committee on Midgard Labs scaling: No✕High AssuranceYoroi on High Assurance: Yes✓YUTA on High Assurance: Yes✓Blockdaemon on High Assurance: Yes✓EMURGO on High Assurance: Yes✓Eternl DRep Committee on High Assurance: Abstain−VacuumLabs PlutusYoroi on VacuumLabs Plutus: Yes✓YUTA on VacuumLabs Plutus: Yes✓Blockdaemon on VacuumLabs Plutus: Yes✓EMURGO on VacuumLabs Plutus: Yes✓Eternl DRep Committee on VacuumLabs Plutus: Yes✓BlockfrostYoroi on Blockfrost: Abstain−YUTA on Blockfrost: No✕Blockdaemon on Blockfrost: Abstain−EMURGO on Blockfrost: Abstain−Eternl DRep Committee on Blockfrost: No✕PogunYoroi on Pogun: Abstain−YUTA on Pogun: No✕Blockdaemon on Pogun: did not vote·EMURGO on Pogun: Abstain−Eternl DRep Committee on Pogun: No✕
Equal cells show decisions, not voting weight. The five are the largest DReps by delegated power at epoch 635. Yoroi and EMURGO abstained on the three that expired, YUTA voted no on them, and Blockdaemon abstained on Midgard Labs and Blockfrost and did not vote on Pogun.

Abstaining power leaves the count, while delegated power that did not vote stays in it as no. On each of the three that expired more power voted against than for, and the abstaining power was roughly equal to the power voting no: on Blockfrost ₳2.12B voted no, the heaviest opposition cast anywhere in the nine.

Singapore: baseline sponsorship approved, Summit funding falls short

Two events in Singapore were up for a vote: the TOKEN2049 conference, where EMURGO asked for a sponsorship package for Cardano, and the Cardano Summit, the Cardano Foundation’s own event, for which it asked ₳7.8M. The three requests had started life as one bundle that expired in epoch 630, told in the review of epochs 630 to 632. The Baseline Sponsorship asked for ₳3.3M for Cardano’s presence at TOKEN2049 at a tier one step below the bundle, and was paid at epoch 635 on 70.2%. The Sponsorship Upgrade asked for ₳1.77M more for extras at the same conference, the higher tier, a larger booth and a keynote slot, and reached 27.3%. The Cardano Summit request came closest of anything that expired, finishing at 65.1%, about 1.9 percentage points short, on 129 yes votes against 61. The DReps paid for the presence at the conference and not for the extras, and the Cardano Summit request received no treasury funding.

The three requests came from two organisations that also act as DReps, EMURGO and the Cardano Foundation, and both wrote about it. EMURGO, the proposer of the baseline sponsorship, wrote that its “initial position was to abstain, recognising the conflict of interest that comes with voting on a proposal we” submitted, and voted yes after changes to the proposal. Yoroi, which describes itself as a related entity, wrote that its first inclination had been to abstain and that EMURGO had since “waived its 15% management fee in full”. The Cardano Foundation, the proposer of the revised summit request, abstained on it, writing that it had not sufficiently engaged with the community before the first proposal, and KtorZ abstained on the same request as an employee of the Cardano Foundation.

The others drew the line between the baseline and the rest. The Eternl DRep Committee abstained on the Cardano Summit request and the upgrade, writing that Singapore in that week “is exceptionally expensive”, that Cardano must be at the conference, and that it did not want to stand in the way by voting no. YUTA voted no on the upgrade because the proposal did not show that a larger keynote and booth make a significant difference.

The durian request finishes at 0.8%

The clearest no of the window went to a request for ₳2.4M to trace individual durians grown in Vietnam without a physical label on each fruit. It drew 8 yes votes against 132 and expired at 0.8%, with Phil_uplc the only committee member for it and five against, the only action decided in these three epochs that a majority of the committee opposed, on the procedural requirements for a withdrawal. The Cardano Foundation voted no because the request “seeks a non-refundable grant for a private commercial venture”, and encouraged a resubmission structured as a loan.

Tweag files a smaller request before the first one expires

Tweag asked for ₳39.8M for seventeen work packages of core infrastructure over two years, chief among them bringing the Peras finality upgrade to the main network, and expired at 6.1%, on 44 yes votes against 85. The Cardano Foundation voted no over “the bundled two-year scope, unresolved 2025 delivery, and insufficient budget transparency” and encouraged a leaner resubmission. Before the request expired at the start of epoch 635, a second one from Tweag had been submitted in epoch 634, for ₳18.3M over one year, keeping three of the seventeen packages. Two other withdrawals were paid at the start of epoch 635: the baseline sponsorship, and ₳4.6M for Pebble, twelve months of work on a smart contract language and the TypeScript libraries other Cardano toolkits build on, at 69.3%, itself a smaller second request after a larger one had expired in epoch 628.

The treasury at its lowest point so far

The treasury reading was ₳1.64B at the start of epoch 633 and ₳1.51B at the start of epoch 635, a fall of ₳131.8M, and that second reading was lower than any since epoch 508. By epoch 635 twelve withdrawals had used ₳207.3M of the ₳350M limit for epochs 613 to 713, most of it in the six paid in epoch 634. Across the window DReps cast 1,070 votes and committee members 54, superseded votes included, and 204 DReps cast a final vote.

The treasury balance, epochs 613 to 635

In billions of ada

1.45B1.52B1.60B1.68B1.75BEpoch 613: 1.64B613Epoch 614: 1.64BEpoch 615: 1.64B615Epoch 616: 1.65BEpoch 617: 1.65BEpoch 618: 1.65BEpoch 619: 1.66BEpoch 620: 1.66B620Epoch 621: 1.66BEpoch 622: 1.66BEpoch 623: 1.66BEpoch 624: 1.62BEpoch 625: 1.61B625Epoch 626: 1.62BEpoch 627: 1.62BEpoch 628: 1.63BEpoch 629: 1.63BEpoch 630: 1.63B630Epoch 631: 1.64BEpoch 632: 1.64BEpoch 633: 1.64BEpoch 634: 1.52BEpoch 635: 1.51B635Epoch 634: Six withdrawals paidSix withdrawals paid
Between payouts the balance climbs a few million an epoch. The epoch 634 payouts took it below its level at epoch 625.

Decided in this window

15 actions, open the full list

The numbers behind the window

Delegated to DReps, at the start of epoch 633
₳5.85B
Delegated to DReps, at the start of epoch 635
₳5.83B
Votes cast in the window, superseded votes included
1,124
DReps whose final vote fell in the window
204
Treasury, at the start of epoch 633
₳1,643.8M
Treasury, at the start of epoch 635
₳1,512.0M
  • The committee data behind this review carries no name for one hot key. The chain links it to the cold key that the committee compensation document lists as Phil_uplc, who cast the yes on the durian traceability request.
  • DRep shares are the share of counted power: abstaining power is left out, while power that did not vote and power delegated to the always no confidence option are folded into the no side.
  • Committee shares are yes votes over the members active at the decision minus those who abstained. A member who does not vote at all is not an abstainer and lowers the share.
  • How the largest DReps voted is read from the pack vote by vote. It shows what they did, not why, and it is not proof that the rest followed them.
  • Votes cast is every vote of epochs 633 to 635 across all three roles, superseded votes included.

Sources and further reading

30 sources, open the list
  • The committee compensation document identifies Phil_uplc as a serving committee member by the cold key whose authorised hot key cast the one committee yes on the durian traceability request. the committee compensation document, on Phil_uplc's key
  • The Eternl DRep Committee published one rationale for the nine requests and the Tweag request, a checklist marking each yes, no or abstain. the rationale of the Eternl DRep Committee on the nine requests
  • Yoroi wrote that it revised its prior abstain to yes on the Developer Experience Initiative, because developer experience is time sensitive and a further delay would be material, and that its yes on the VacuumLabs Plutus request was also a change from an earlier abstention. the rationale of Yoroi on the Developer Experience Initiative
  • EMURGO wrote that it revised its prior abstain to yes on the Developer Experience Initiative, that the proposal had not changed and that it did not withdraw its concerns about attribution and third party coordination. the rationale of EMURGO on the Developer Experience Initiative
  • YUTA voted no on the scalability request, writing that Hydra, which makes up 80% of the proposal, had received significant investment in the past and that it was hard to envision it meaningfully contributing to transaction volume. the rationale of YUTA on the scalability request
  • YUTA voted no on the Blockfrost request, writing that the service should be positioned as one competing with other providers, guiding users from a free tier to a paid one, rather than as a public service that eliminates competition. the rationale of YUTA on the Blockfrost request
  • Sebastien Guillemot abstained on the Pogun request, writing that he liked many of its ideas but generally abstains on commercial proposals. the rationale of Sebastien Guillemot on the Pogun request
  • EMURGO, the proposer of the baseline sponsorship, wrote that its initial position was to abstain because of the conflict of interest in voting on its own proposal, and that it voted yes after changes to the proposal. the rationale of EMURGO on the baseline sponsorship
  • Yoroi wrote that EMURGO is the proposer of the baseline sponsorship, that its initial inclination as a related entity was to abstain, and that EMURGO had since waived its 15% management fee in full. the rationale of Yoroi on the baseline sponsorship
  • The Cardano Foundation, the proposer of the revised Cardano Summit request, abstained on it, writing that it had not sufficiently engaged with the community before the first proposal. the rationale of the Cardano Foundation on the revised summit request
  • KtorZ abstained on the revised summit request, writing that as an employee of the Cardano Foundation abstaining avoided any heated debate on the topic. the rationale of KtorZ on the revised summit request
  • The Eternl DRep Committee abstained on the revised summit request and on the sponsorship upgrade, writing that Singapore in that week is exceptionally expensive, that Cardano must be at the conference, and that it did not want to stand in the way by voting no. the rationale of the Eternl DRep Committee on the sponsorship upgrade
  • YUTA voted no on the sponsorship upgrade, writing that the proposal did not adequately support the claim that a larger keynote and booth make a significant difference. the rationale of YUTA on the sponsorship upgrade
  • The Cardano Foundation voted no on the durian traceability request, writing that it seeks a non refundable grant for a private commercial venture with negligible treasury return, and encouraged a resubmission structured as a loan. the rationale of the Cardano Foundation on the durian traceability request
  • Five committee members found the durian traceability request unconstitutional on the procedural requirements for a treasury withdrawal. the rationale of the committee member Tingvard on the durian traceability request
  • The Cardano Foundation voted no on the two year Tweag request, writing that the bundled scope, unresolved 2025 delivery and insufficient budget transparency prevented its approval, and encouraged a leaner resubmission. the rationale of the Cardano Foundation on the two year Tweag request
  • The document behind the consensus request funds taking the Leios throughput upgrade from its public testnet to a mainnet ready release candidate, with Intersect administering the funds against milestones and unspent funds returned to the treasury. the document behind the consensus request
  • The document behind the upgrades request funds three workstreams: account addresses that can receive direct deposits, the design work for a treasury able to hold stablecoins and other native assets, and paying transaction fees in assets other than ada. Intersect administers the funds against milestones and unspent funds return to the treasury. the document behind the upgrades request
  • The document behind the maintenance request is filed by Input Output and covers nine functional areas of core maintenance, from bug fixing and security reviews to release management, from the second half of 2026 through the first quarter of 2027, with Intersect administering the funds against milestones and unspent funds returned to the treasury. the document behind the maintenance request
  • The document behind the developer experience request funds a six month programme on developer tooling, documentation and onboarding, with Intersect as administrator, milestone based disbursement and unspent funds returned to the treasury. the document behind the developer experience request
  • The document behind the Pogun request describes a bitcoin credit market, a yield layer and a bridge, and commits to returning 20% of earnings to the treasury until the initial funding is repaid, followed by a perpetual 5%. the document behind the Pogun request
  • The document behind the scalability request funds three workstreams: shared data availability infrastructure for layer two systems, production hardening of Hydra, and the mainnet launch of an optimistic rollup. the document behind the scalability request
  • The document behind the Blockfrost request splits the sum between building an indexing architecture that lets operators index and serve a slice of the chain rather than all of it, and an operational subsidy for the free tier the company states it has funded alone since inception. the document behind the Blockfrost request
  • The document behind the Tweag request covers 17 work packages across 9 core infrastructure areas over two years, with the mainnet deployment of the Peras finality upgrade as its primary focus. the document behind the Tweag request
  • The document behind the second Tweag request covers 3 work packages over one year, the first Peras release, partial history nodes and conformance testing, all of them among the packages of the first request. the document behind the second Tweag request
  • The document behind the baseline sponsorship states that it was restructured as an independent request after concerns about the scale of the combined summit and sponsorship proposal, lowering the sponsorship tier by one step. the document behind the baseline sponsorship
  • The document behind the sponsorship upgrade describes it as a top up to be voted on in conjunction with the baseline sponsorship, restoring the higher tier with a larger booth and a keynote slot, and commits to returning all of the funds within 30 days if it is enacted without the baseline. the document behind the sponsorship upgrade
  • The document behind the revised summit request describes a budget reduced by 22% against the combined proposal, achieved by going from three stages to two, and a request decoupled from the sponsorship of the other conference. the document behind the revised summit request
  • The document behind the Pebble request funds twelve months of two tracks, a smart contract language and the maintenance of the TypeScript libraries that other Cardano toolkits depend on. the document behind the Pebble request
  • The document behind the durian request proposes tamper evident traceability for durian grown in Vietnam, identifying each fruit without a physical label. the document behind the durian request