Governance ReviewNo. 14Epochs 561 to 56329 May 2025 to 13 Jun 2025
Amaru's ₳1.5M node budget closes at 80.4%
Amaru's ₳1.5M budget for an alternative Cardano node closed with 80.4% DRep support. Of the five actions closing in these epochs, it was the only one above 50%. Both proposals to lower the treasury spending limit, to ₳200M or ₳300M, fell short.
EMURGO, YUTA and the Eternl DRep Committee back Amaru’s budget
Cardano Blockchain Ecosystem Budget: Amaru Node Development 2025 closed at the start of epoch 563 with 80.4% of DRep power behind it, on 232 yes votes to 14 no and 10 abstain, ₳4.32B of power for it against ₳28.7M. Six committee members found it constitutional and the Cardano Japan Council abstained. All 32 pool votes recorded on it were yes.
It asks ₳1.5M for the second half of 2025 to fund Amaru, a block producing node written mainly in Rust. The project sits under PRAGMA, a not for profit association whose five members are Blink Labs, the Cardano Foundation, dcSpark, Sundae Labs and TxPipe. Its document gives five reasons for another node, among them lower resource use, monitoring built on industry standards and the argument that a single implementation is “a single point of failure and a central point of control”. It names as administrator Amaru’s maintainer committee, Arnaud Bailly, Matthias Benkort, Pi Lanningham, Santiago Carmuega and Damien Czapla, assisted by a smart contract on chain.
EMURGO wrote that the existing node “leaves developers with little flexibility” and that it has great confidence in PRAGMA. YUTA wrote that the budget corresponds directly to the roadmap the DReps had approved and that Amaru “has the qualities of a public good”. The Eternl DRep Committee wrote that node diversity is important. Pi Lanningham, one of those scope owners, abstained over a conflict of interest because Sundae Labs would be one of the development teams, while writing that reimplementing the protocol forces every design decision to be “opened and re-examined”. The Cardano Japan Council abstained because a maintainer committee made up “exclusively of core project members” raises concerns about independence.
The five actions that closed, in delegated ada
Bars show delegated ada behind votes cast, the percentage is yes power as a share of counted power
Elder Millenial’s liquidity budget closes with a mismatched hash
Cardano Treasury DeFi Liquidity Budget closed at the start of epoch 563 with ₳0.20B of DRep power for it against ₳2.14B, on 10 yes votes to 135 no. The document at its link asks for ₳50M over twelve months for stablecoin liquidity, but the file carries one character more at its end than the one whose hash was recorded on chain, so tools showed the hash as incorrect. Elder Millenial, named in the document as a member of its administrative committee, had posted that he submitted the action and would have to resubmit it. YUTA voted no “to prevent the proposal from being adopted twice”, and CardanoYoda (MANDA Pool) because the action “is invalid and will reportedly be resubmitted”. Input Output, the Cardano Atlantic Council, the Eastern Cardano Council and the Intersect Constitutional Council found it unconstitutional, and the Cardano Foundation abstained. The Intersect Constitutional Council wrote that the content of an action must be identical to its off chain version.
Seven committee members find the community builders budget unconstitutional
2025 Cardano Blockchain Ecosystem Budget - 7.5M ₳ for community builders closed at the start of epoch 563 with 34.5% of DRep power, on 103 yes votes to 66 no. It asks ₳7,568,810 for seven community proposals, among them Midgard, Starstream and Dolos, that cleared ₳2.69B in the off chain poll for Intersect’s budget, a bar it computes as a majority of all active registered voting stake rather than of the ada that voted. It leaves out the proposals of the founding entities and notes that community builders may not have the ₳100k deposit needed to go on chain alone.
Five of the seven members gave reasons with their votes. The Eastern Cardano Council wrote that it designated no administrator and no process for overseeing the use of funds, and the Cardano Atlantic Council that it had no such process. Input Output wrote that it did not specify an administrator for every item, Starstream being one without. The Intersect Constitutional Council wrote that the budget did little more than name Intersect, that naming an administrator without its consent does not appoint one, and that it lacked an allocation for audits. EMURGO found no clear provision for auditing the use of funds.
Yoroi W₳llet wrote that “we support every proposal listed” but that all of them were already in Intersect’s budget process, so approving them again “risks double-funding”. EMURGO voted no over the same overlap. Dave supported Midgard, Starstream and Dolos but voted no because each should be voted on individually and because the named administrator had not clearly consented. SIPO abstained because no process existed for choosing which version of a proposal proceeds when it sits in both bundles. YUTA voted yes, and so did CardanoYoda, counting three of the seven projects as answers to scalability, “the most pressing need”.
The ₳200M and ₳300M ceilings close below 50%
2025 Cardano NCL, ₳200M for the period from epoch 532 to the end of epoch 604, closed at the start of epoch 561 with 43.9% of DRep power, on 213 yes votes to 85 no. Set a 300 million ADA Net Change Limit for Epochs 563 to 635 closed at the start of epoch 563 with 37.3%, on 109 yes to 87 no. Its document argued that the limits in place or pending only covered 2025, while many budgets run twelve months into 2026. The ₳200M document names more than 50% of active DRep voting stake as the bar for a ceiling. Six committee members found each constitutional, and the Eastern Cardano Council abstained on both, writing that such an action is neither a budget nor a signal on an action the chain could enact, so the committee is not empowered to assess it. The ₳350M ceiling, running to the end of epoch 604, remained the one in force.
Yoroi W₳llet, EMURGO and the Cardano Foundation voted no on both. Yoroi wrote on the ₳300M one that it had voted for the ₳350M limit and “will continue to align with that voting stance”, and EMURGO that “repeatedly adjusting the cap could create delays” and that the approved limit is “not a fixed target that must be fully used”. The Eternl DRep Committee voted yes because ₳300M “should cover most proposal costs” into the next year, and SIPO because budget items running into 2026 would otherwise become ineligible for withdrawals. YUTA voted yes on both, SASA_nagamaru_ながまる on ₳300M as “the more cautious end” of a realistic range, and CardanoYoda because it covered a budget of about ₳281M that DReps had approved with about ₳20M to spare. BTBF_XSP voted no because a period spanning two calendar years “creates an awkward timeframe”.
Nothing is paid from the treasury
Cardano Blockchain Ecosystem Budget - 275M ada Administered by Intersect, ₳275,269,340 for 39 proposals that each named Intersect as administrator, stood at 65.4% of DRep power as of the close of epoch 563, its last epoch of voting.
DReps cast 374 votes in epochs 561 to 563, committee members 32 and pools 43, 449 in all with superseded votes included, and 151 distinct DReps cast a final vote. The power delegated to DReps went from ₳5.32B at epoch 561 to ₳5.37B at epoch 563. The treasury reading rose ₳8.5M to ₳1.78B, and nothing had been drawn against the ₳350M ceiling.
Decided in this window
| Action | Outcome | DRep yes |
|---|---|---|
| Cardano Blockchain Ecosystem Budget: Amaru Node Development 2025 | Closed 563 | 80.4% |
| 2025 Cardano NCL | Closed 561 | 43.9% |
| Set a 300 million ADA Net Change Limit for Epochs 563 to 635 | Closed 563 | 37.3% |
| 2025 Cardano Blockchain Ecosystem Budget - 7.5M ₳ for community builders | Closed 563 | 34.5% |
| Cardano Treasury DeFi Liquidity Budget | Closed 563 | 4.0% |
Open at the close of the window
| Action | Status | DRep yes |
|---|---|---|
| Cardano Blockchain Ecosystem Budget - 275M ada Administered by Intersect | Undecided at the close of epoch 563 | 65.4% |
The numbers behind the window
- Delegated to DReps, at the start of epoch 561
- ₳5.32B
- Delegated to DReps, at the start of epoch 563
- ₳5.37B
- Votes cast in the window, superseded votes included
- 449
- DReps whose final vote fell in the window
- 151
- Treasury, at the start of epoch 561
- ₳1,769.1M
- Treasury, at the start of epoch 563
- ₳1,777.6M
- 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. Pool vote counts are every pool vote recorded on an action up to the close of epoch 563.
- Information actions are never ratified or enacted by the ledger. They close when their voting ends. The constitution still sets conditions a budget has to meet, among them an active spending ceiling and a named administrator with an oversight process, and committee members record whether they find a budget constitutional.
- What the proposals ask for and argue is read from their own documents, named under the sources below. The file at the liquidity budget's link ends with one line break more than the file whose hash was recorded on chain, and hashes to the recorded value without it, so its content is what was filed. That Elder Millenial filed it rests on his own post, quoted in the rationale of Agora | Cardano, under the handle the document gives for him. The committee reasons are the rationales the members gave with their votes, the other reasons quoted are the published rationales of the voters named, and neither says anything about voters who gave none.
- The aggregate budget closes at the boundary that ends this window, so its stored tally is the state at the close of epoch 563 and nothing later. It is quoted without an outcome, because it had none yet.
- No treasury withdrawal had been enacted through epoch 563. Votes cast is every vote of epochs 561 to 563 across all three roles, superseded votes included, spread over six proposals. The ceiling in force runs to the end of epoch 604, which is not the end epoch the site registry carries today.
Sources and further reading
36 sources, open the list
- EMURGO voted yes on the node budget, writing that it has great confidence in PRAGMA and its members as leading experts, and that the existing node implementation leaves developers with little flexibility. the rationale of EMURGO on the node budget
- YUTA voted yes on the node budget, writing that it corresponds directly to the roadmap the DReps had approved and that it has the qualities of a public good. the rationale of YUTA on the node budget
- The Eternl DRep Committee voted yes on the node budget, writing that node diversity is important. the rationale of the Eternl DRep Committee on the node budget
- Pi Lanningham abstained on the node budget over a potential conflict of interest, as one of the scope owners on the project with Sundae Labs one of its development teams, while writing that reimplementing the protocol in another language forces every design decision and detail to be reexamined and documented. the rationale of Pi Lanningham on the node budget
- The Cardano Japan Council abstained on the node budget, writing that the maintainer committee designated to handle the budget consists exclusively of core project members, which raises concerns about independence and third party oversight. the rationale of the Cardano Japan Council on the node budget
- The node budget asks for ₳1.5M of additional funding for the second half of 2025 for Amaru, an open source block producing node written mainly in Rust under PRAGMA, a not for profit association whose five members are Blink Labs, the Cardano Foundation, dcSpark, Sundae Labs and TxPipe. Its text gives five reasons for another node, among them lower resource use, standard monitoring and tracing, and the argument that a single node implementation is a single point of failure and a central point of control. It names Amaru's maintainer committee, Arnaud Bailly, Matthias Benkort, Pi Lanningham, Santiago Carmuega and Damien Czapla, as direct administrator of the budget, assisted by an on chain smart contract. the document behind the node budget
- The document at the liquidity budget's anchor link asks for 50,000,000 ada over twelve months to increase stablecoin liquidity on Cardano, managed by an administrating committee of seven, and lists Nick Schaub, aka Elder Millenial, with the handle @ElderM, among the six members it names. the document at the liquidity budget's anchor link
- Agora | Cardano voted no on the liquidity budget, quoting a post by @ElderM in which its author writes that he submitted the info action requesting 50 million ada, that an extra character inserted at the end of the file meant most tools showed the hash as incorrect, and that he will have to resubmit. the rationale of Agora | Cardano on the liquidity budget
- YUTA voted no on the liquidity budget, writing that it was planned to be resubmitted and that a no prevents the proposal being adopted twice, before and after the resubmission. the rationale of YUTA on the liquidity budget
- CardanoYoda voted no on the liquidity budget, writing that the action is invalid and would reportedly be resubmitted. the rationale of CardanoYoda on the liquidity budget
- The Intersect Constitutional Council found the liquidity budget unconstitutional because an error during submission meant that the hash of the provided metadata did not match, and the constitution requires the content of every on chain governance action to be identical to the final off chain version. the rationale of the Intersect Constitutional Council on the liquidity budget
- The community builders budget is an objection to how the main budget was assembled. It asks for 7,568,810 ada for seven community proposals, among them Midgard, Starstream and Dolos, that cleared a bar of ₳2.69B in the off chain poll, which it computes as a majority of the active registered voting stake rather than of the ada that voted. It leaves out the proposals of the founding entities and notes that a proposer needs a ₳100k deposit to go on chain alone, which community builders may not have. the document behind the community builders budget
- The Eastern Cardano Council published a rationale for its no vote: the constitution requires a budget to specify a process for overseeing the use of withdrawn funds and to designate one or more administrators responsible for that oversight, and this action did neither. the rationale of the Eastern Cardano Council on the community builders budget
- The Cardano Atlantic Council found the community builders budget unconstitutional because it does not provide any process for overseeing the use of funds from treasury withdrawals. the rationale of the Cardano Atlantic Council on the community builders budget
- Input Output found the community builders budget unconstitutional, writing that it does not specify an administrator for each of the included proposals, and that while some of them designate their own, at least one, Starstream, does not. the rationale of Input Output on the community builders budget
- The Intersect Constitutional Council found the community builders budget unconstitutional, writing that it gives no information on its administrator beyond naming Intersect, that naming an administrator without its consent does not meet the requirement to appoint one, that it had been raised in public forums that Starstream did not wish to have Intersect as its administrator, and that a budget also needs an allocation of funds for audits. the rationale of the Intersect Constitutional Council on the community builders budget
- EMURGO, voting as a committee member, found the community builders budget unconstitutional, writing among other reasons that it includes no clear provision for auditing the use of funds or any other oversight mechanism. the committee rationale of EMURGO on the community builders budget
- Yoroi voted no on the community builders budget, writing that all of the initiatives are already included in the Intersect budget process, that approving them again risks double funding, and that it supports every proposal listed but not the approach. the rationale of Yoroi on the community builders budget
- EMURGO voted no on the community builders budget, writing that it had voted for most of the initiatives inside it, that all of them were already being considered under the larger budget, and that an overlapping action risks duplicated funding. the rationale of EMURGO on the community builders budget
- Dave voted no on the community builders budget, writing that it strongly supports several of the projects inside it, among them Midgard, Starstream and Dolos, but that each should be voted on individually, that the named administrator had not clearly consented, and that Starstream had said publicly it did not agree to be included under that administration. the rationale of Dave on the community builders budget
- SIPO abstained on the community builders budget, writing that some proposals appear in both budget packages and that there is no unified process for selecting which version of a proposal proceeds to a treasury withdrawal. the rationale of SIPO on the community builders budget
- CardanoYoda voted yes on the community builders budget, writing that three of its seven projects address scalability, the most pressing need for the Cardano ecosystem. the rationale of CardanoYoda on the community builders budget
- The ₳200M ceiling asks for ₳200M for the period from the start of epoch 532 to the end of epoch 604, states that in the event of conflict it supersedes any prior limit covering 2025, and names a threshold of greater than 50% of the active voting DRep stake for a ceiling to pass. the document behind the ₳200M ceiling
- The ₳300M ceiling asks for ₳300M for the period from the start of epoch 563 to the end of epoch 635, on the reasoning that existing and pending limits only cover periods through the end of 2025 while many budget proposals run on twelve month timelines into 2026, and states that it would replace any previous limit if agreed. the document behind the ₳300M ceiling
- The ceiling in force for this period is ₳350M, running from the start of epoch 532 to the end of epoch 604, as the proposal that set it states. the document behind the ceiling in force
- The Eastern Cardano Council abstained on the ₳300M ceiling, writing that as an information action it neither relates to a budget nor gauges sentiment towards an action that could be enacted on chain, so the committee is not empowered to assess its constitutionality. the rationale of the Eastern Cardano Council on the ₳300M ceiling
- The Eastern Cardano Council abstained on the ₳200M ceiling in the same words as on the ₳300M one: the action neither relates to a budget nor gauges sentiment towards an action that could be enacted on chain, so the committee is not empowered to assess its constitutionality. the rationale of the Eastern Cardano Council on the ₳200M ceiling
- Yoroi voted no on the ₳300M ceiling, writing that it had voted for the ₳350M limit proposed by Intersect and would continue to align with that stance. the rationale of Yoroi on the ₳300M ceiling
- EMURGO voted no on the ₳300M ceiling, writing that repeatedly adjusting the cap could delay governance and keep critical funding from projects, and that the limit already approved is a maximum rather than a target. the rationale of EMURGO on the ₳300M ceiling
- The Eternl DRep Committee voted yes on the ₳300M ceiling, writing that ₳300M for the rest of the year and the first half of the next should cover most proposal costs. the rationale of the Eternl DRep Committee on the ₳300M ceiling
- YUTA voted yes on both the ₳200M and the ₳300M ceiling, writing that ₳350M is too large for the second half of the year alone but that ₳200M would not cover budgets running twelve months into the next year. the rationale of YUTA on the ₳300M ceiling
- SIPO voted yes on the ₳300M ceiling, writing that many proposals in the ₳275M budget follow a twelve month cycle into the first half of the next year, and that without a limit covering that period they would become ineligible for withdrawals. the rationale of SIPO on the ₳300M ceiling
- SASA voted yes on the ₳300M ceiling, writing that a limit of 300,000,000 to 350,000,000 ada is realistic and this one sits at the more cautious end. the rationale of SASA on the ₳300M ceiling
- CardanoYoda voted yes on the ₳300M ceiling, writing that DReps had approved a budget of about 281,000,000 ada whose action had not yet been submitted, that ₳300M leaves about 20,000,000 ada of room, and that a one year period from the third quarter makes sense. the rationale of CardanoYoda on the ₳300M ceiling
- BTBF_XSP voted no on the ₳300M ceiling, writing that the calendar year is the clearer reference point and that a period spanning two years creates an awkward timeframe. the rationale of BTBF_XSP on the ₳300M ceiling
- The aggregate budget asks for ₳275,269,340 across 39 proposals, each of which named Intersect as its administrator. the document behind the aggregate budget