Cardano’s ₳13.1M Upgrades Proposal Turns Treasury Voting Into a Governance Test

IO’s ₳13.1 million Cardano Upgrades proposal remains open for voting until May 24, 2026, putting Babel Fees, CIP-159 and multi asset treasury design in front of DReps at the same time as the ecosystem debates treasury accountability.

The proposal asks the Cardano treasury to allocate ₳13,103,039 to a coordinated upgrade package that could affect transaction fees, DApp architecture and the future structure of treasury management. From a technical perspective, the proposal is significant. From a governance perspective, it has become more than a vote on whether the upgrades are useful.

After a public NO vote from the Cardanians DRep, the debate shifted toward a larger question, what level of financial detail, delivery evidence and public accountability should Cardano require when treasury funds are used for core protocol and economic layer development?

Cardano Upgrades Proposal Combines Babel Fees, CIP-159 and Treasury Design

The IO proposal combines three major workstreams into a single delivery plan running from Q3 2026 through Q2 2027.

The first workstream focuses on CIP-159, enhanced account addresses and multi asset microfees. The goal is to support cheaper micro transactions for wallets and DeFi applications, direct deposits to account style addresses, future PlutusV4 functionality and new DApp architectures built around more scalable interaction models.

The second workstream centers on Babel Fees. This is one of the most important user experience changes in the package because it would allow users to pay transaction fees with native assets they already hold, instead of first acquiring ada only to submit a transaction. IO states that the MVP target is Q1 2027, with production readiness expected by February 2027 and planned integration with Lace wallet. Examples involving assets such as $USDM are presented as illustrations of the model, not as confirmed supported assets.

The third component focuses on multi asset treasury design through CPS-23. This does not mean the Cardano treasury would immediately convert reserves into stable assets. The proposal funds the design framework and community consultation process needed to explore a legal and technical path toward a treasury capable of holding multiple forms of value. For an ecosystem increasingly relying on treasury funded public goods, treasury stability is becoming a strategic issue, not only a financial one.

The proposal also includes milestone based payments through the Intersect treasury reserve smart contract, third party assurance at every sign off stage and a commitment that unused funds would return to the treasury. Those safeguards matter, but they have not resolved the governance concerns now shaping the vote.

DRep Voting Turns the IO Proposal Into a Treasury Accountability Test

Cardanians_io voted NO with 17.71 million ada in voting power. Their criticism was not that Babel Fees, CIP-159 or multi asset treasury design lack value. Cardanians described the proposal as directionally meaningful, while objecting to the governance standard around the funding request.

According to their published rationale, a treasury request of this size for core economic layer work should include a more auditable cost model, named delivery teams, FTE counts, workstream level rates and artifact driven milestone acceptance criteria. In practical terms, they argue that Cardano governance should not only receive milestone promises, but also clear evidence standards showing what will be delivered, how it will be tested and what officially counts as completion.

That distinction is important because Cardano’s treasury is no longer operating like an experimental governance sandbox. As treasury funding grows, DReps need comparable proposals, measurable value for money benchmarks and a stronger audit trail for future review. The larger the request, the harder it becomes to separate technical importance from financial accountability.

Cardanians also criticized the proposal for bypassing the full Intersect Budget Process. Their position is that the process exists to improve comparability, discovery and structured review between DReps and proposers before on chain voting begins. If large founding entities can route major treasury requests directly on chain outside the broader budget process, some DReps believe that creates an uneven standard across the ecosystem.

Other DReps have taken different positions. SIPO voted YES and described the proposal as strategically important for adoption, governance and ledger development. Dave voted NO, criticizing the bundled structure, overall size and lack of sufficiently granular development breakdowns. Jaromir Tesar supported the proposal with reservations, acknowledging transparency concerns while still supporting the broader strategic direction.

Cardano Governance Faces a Precedent Beyond One Upgrade Vote

At the time of writing, no publicly available response from IO, Charles Hoskinson, Intersect or the Cardano Foundation directly addresses the Cardanians criticism regarding category budgeting, artifact driven milestones, FTE breakdowns or the decision to bypass the full Intersect budget review flow.

That does not necessarily mean additional detail is unavailable to DReps through governance tools. Publicly, however, IO’s communication remains focused mainly on the technical value of the upgrades, the delivery structure and milestone based treasury protections.

Governance tracking tools such as Cexplorer continue to show live voting activity for the proposal, giving the ecosystem a way to monitor how DReps, SPOs and Constitutional Committee members position themselves ahead of the May 24 deadline.

That is why this vote has become larger than one ₳13.1 million treasury action. If the proposal passes, Cardano may secure several strategically important upgrades, including Babel Fees, CIP-159 and a path toward multi asset treasury design, while also setting a precedent for how much financial detail large proposers must provide when requesting public funds. If it fails, the result would not necessarily read as a rejection of the upgrades themselves. It would send a different message, that Cardano governance is beginning to treat treasury transparency as part of protocol legitimacy, not as an optional layer around it.