Governance ReviewNo. 34Epochs 627 to 62924 Apr 2026 to 9 May 2026

HLabs misses by a quarter of a point, then splits its request in two

The HLabs request for ₳8.0M to maintain core tooling, build a browser node and finish a smart contract language was the only one decided in epochs 627 to 629, and it finished at 66.77% of DRep power, 0.23 points short of the 67% a withdrawal needs, with more power abstaining than opposing. The two largest abstainers wrote that a third alternative node was not yet needed, and the Cardano Foundation voted no while asking for a leaner request for the language and the tooling maintenance. One epoch after the deadline HLabs filed two requests, one for that and one for the browser node, ₳4.6M each. Eight new requests asking for ₳97.2M together were submitted in the same three epochs.

66.77%
of counted DRep power behind the only request decided, against a 67% bar
₳1.17B
of delegated power that abstained on it, against ₳0.76B that voted no
₳8.0M
the sum it asked for, covering TypeScript tooling maintenance, a browser node and a smart contract language
1,159
DRep ballots across the three epochs

0.23 points short

Pebble + Gerolamo - HLabs 2026 Budget asked the community for ₳8.0M for a year of work on three things: maintenance of the TypeScript tooling that, by its own account, most Cardano developers use directly or through libraries built on it, a node that runs inside a web browser, and a smart contract language. When its voting closed at the start of epoch 628 it stood at 66.77% of DRep power, 0.23 percentage points under the 67% a withdrawal needs, on 140 yes ballots, 43 no and 20 abstain. 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. It was the only thing decided in these three epochs.

The committee split six yes against one no. The Eastern Cardano Council, the one no, found that the request set aside no ada for periodic independent audits and oversight metrics, which the constitution requires of a withdrawal, with every other requirement met.

What voted on the HLabs request, in delegated ada

Bars show the ballots cast, in delegated ada

YesNoAbstain
HLabsHLabs, Yes: 3.14BHLabs, No: 0.76BHLabs, Abstain: 1.17B66.8%bar 67%
₳1.17B abstained and ₳0.76B voted no. The bars show cast ballots only. The share also counts power that cast no ballot and always no confidence power on the no side, with abstaining power left out, which is why abstaining weight is not opposition.

Why Yoroi and EMURGO abstained

Among the twelve largest DReps on its ballot list, ranked by delegated power at epoch 629, Yoroi W₳llet and EMURGO abstained, Sebastien Guillemot セバ and the Cardano Foundation voted no, and the other eight voted yes. The abstentions were about the node. Yoroi wrote that its conversations with developers had raised “genuine questions about whether TypeScript is the right foundation for a production-grade node”, that with “Amaru and Dingo already funded and progressing” a third alternative node was not yet the best use of treasury money in this cycle, that the ecosystem “does not require a new smart contract language at this point in time”, and that at over 8 million ada the scale of the request warranted reconsideration. EMURGO wrote the same on all three counts and added that it “would warmly welcome the team to resubmit with a revised cost”.

The Foundation voted no while backing Pebble and the maintenance of the TypeScript libraries, writing that “the combined proposal’s costs and uncertain practical value of the Gerolamo browser node prevent our approval”, and that it would “highly encourage a leaner withdrawal specifically for Pebble”. Sebastien Guillemot’s no was about the language: an alternative to Aiken “that’s 50% better” would not be the difference maker for adoption.

The yes votes were about demand. YUTA wrote that it had built a simple demo with both products and saw significant potential demand for them. The Eternl DRep Committee wrote that it had revised its vote on Dingo from no to yes and that, for node diversity, it would support the Haskell, Rust, Go and TypeScript implementations alike.

One epoch later, two requests instead of one

Pebble & Ecosystem maintenance: TypeScript core of Cardano, from the same firm, was submitted in epoch 629, one epoch after the first request expired, for ₳4.6M. It funds two tracks, the language and the maintenance of the TypeScript tooling, the two parts the Foundation had said it would support. A second request came in the same epoch, another ₳4.6M for the browser node on its own, and each of the two is voted on independently. Together they ask ₳9.2M where the expired request asked ₳8.0M, so the refiling is a split rather than a cut. The node the two abstainers had questioned now stands alone, and the language and tooling no longer depend on it.

The revised Pebble and tooling request values five full time equivalents at 1,150,000 dollars with a 15% contingency. The original 2,812,500 dollar request, ten full time equivalents with a 25% refundable contingency, also covered the browser node, which now has a request of its own, so the two dollar figures are not the same work at two prices. The exchange rate changed as well: thirty five cents per ada in the expired request, a method it says it borrowed from the Amaru node proposal, twenty five cents in the new one. It also adds a periodic independent audit of how the money is used, the item the Eastern Cardano Council’s no vote had named. Its path is in the review of epochs 633 to 635, and the browser node’s in the review of epochs 636 to 638.

HLabs, one request and the two that replaced it

The sum asked, in millions of ada

First request, expired at epoch 628First request, expired at epoch 628: 8M8MPebble and tooling, filed in epoch 629Pebble and tooling, filed in epoch 629: 4.6M4.6MThe browser node, filed in epoch 629The browser node, filed in epoch 629: 4.6M4.6M
The two requests filed in epoch 629 ask ₳9.2M together, more than the ₳8.0M of the request they replace. What changed is that each part is voted on alone.

Eight new requests for ₳97.2M

Eight new requests were submitted in epochs 627 to 629, asking for ₳97.2M between them, and all eight were still open when the window closed. Revised requests were returning to the ballot before the original had expired. Revised Cardano Summit 2026 Singapore came in epoch 627, ₳7.8M from the Cardano Foundation for that one conference on its own. Its text is precise about what changed: the request is decoupled from the sponsorship of a second conference, and the summit budget is cut by 22%, which it puts at 550,000 dollars, by going from three stages to two and by raising the Foundation’s own contribution from 250,000 to 380,000 dollars. The 22% is measured against the summit part of the earlier request, not against the ₳14.1M the bundle asked for in total. The conference request came back split too, like the HLabs one.

The bundle it was written to replace, Cardano Summit 2026 and TOKEN2049 Singapore, reached its own deadline exactly at the close of the window, at 10.0% of DRep power as of that close.

The largest of the eight was a ₳39.8M request from Tweag for two years of core infrastructure work, seventeen work packages with the Peras finality upgrade as its primary focus, submitted in epoch 628, and the second largest Cardano Vision 2026: Human Centred, Scalable, Post Quantum Secure - IO Research at ₳32.9M, submitted in epoch 629. That one buys a year of research rather than software: its document puts the sum at 7.9 million dollars for forty two outputs across seven work packages, papers, problem statements, prototypes and improvement proposals, from a consortium of nine research partners with thirty six full time equivalents, under three priorities it names as usability and governance participation, scalability, and post quantum security.

Nothing paid

The treasury paid nothing in the window. Between the readings at epoch 627 and epoch 629 its balance rose by ₳7.6M, from ₳1.62B to ₳1.63B. DReps cast 1,159 ballots: 374 in epoch 627, 299 in epoch 628 and 486 in epoch 629. Committee members cast another 17. Those totals include superseded votes, and 153 DReps cast a final ballot somewhere in the window. No stake pool ballot fell in it.

Decided in this window

ActionOutcomeDRep yes
Pebble + Gerolamo - HLabs 2026 BudgetExpired 62866.8%

The numbers behind the window

Delegated to DReps, at the start of epoch 627
₳5.81B
Delegated to DReps, at the start of epoch 629
₳5.83B
Votes cast in the window, superseded votes included
1,176
DReps whose final ballot fell in the window
153
Treasury, at the start of epoch 627
₳1,621.1M
Treasury, at the start of epoch 629
₳1,628.7M
  • 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.
  • One request had its voting deadline exactly at the closing boundary of this window. Its tally is quoted as it stood at that close, without an outcome.
  • Eight requests submitted inside this window were still open at its close and are not in the table. Nine more, submitted one epoch before the window, were still open at its close.
  • That the two Pebble requests come from the same firm, and that the revised Summit request was written to replace the bundle, is read from the metadata the proposals themselves carry, not from the data pack.
  • Votes cast is every ballot of epochs 627 to 629 across all three roles, superseded votes included. No stake pool ballot fell in the window.

Sources and further reading

12 sources, open the list
  • Yoroi abstained on the HLabs request, writing that its conversations with developers had raised genuine questions about whether TypeScript is the right foundation for a production grade node, that with Amaru and Dingo already funded it was not yet persuaded a third alternative node was the best use of treasury resources in this cycle, that the ecosystem does not require a new smart contract language at this point, and that at over 8 million ada the scale of the request warranted reconsideration. the rationale of Yoroi on the HLabs request
  • EMURGO abstained on the HLabs request, writing that discussions with external technologists and its own technical team suggested reservations about TypeScript as the foundation for a production node, that with Amaru and Dingo already funded the case for a third alternative node was not yet established, that it did not believe a new smart contract language was critical, and that it would warmly welcome a resubmission with a revised cost. the rationale of EMURGO on the HLabs request
  • The Cardano Foundation voted no on the HLabs request, writing that it highly values the Harmonic Laboratories team and sees strategic value in Pebble and in the maintenance of the TypeScript libraries, but that the combined proposal's costs and the uncertain practical value of the Gerolamo browser node prevented its approval, and that it highly encourages a leaner withdrawal specifically for Pebble. the rationale of the Cardano Foundation on the HLabs request
  • Sebastien Guillemot voted no on the HLabs request, writing that an alternative to Aiken that is 50% better would not be the difference maker in getting Cardano more adoption, and that he would rather fund a different approach to smart contracts on the UTXO model. the rationale of Sebastien Guillemot on the HLabs request
  • YUTA voted yes on the HLabs request, writing that it had built a simple demo with both products and felt there was significant potential demand for them. the rationale of YUTA on the HLabs request
  • The Eternl DRep Committee voted yes on the HLabs request, writing that it had revised its vote on Dingo from no to yes and that, for node diversity, it would support the Haskell, Rust, Go and TypeScript implementations. the rationale of the Eternl DRep Committee on the HLabs request
  • The committee member Eastern Cardano Council found the HLabs request unconstitutional because it provided no allocation of ada for periodic independent audits and oversight metrics, which the constitution requires of a treasury withdrawal, while finding every other requirement met. the rationale of the Eastern Cardano Council on the HLabs 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 expired request covers twelve months with three headline deliveries: maintenance through an upcoming hard fork, a production ready light node, and a production ready imperative language for smart contracts. It values ten full time equivalents at 2,812,500 dollars including a 25% refundable contingency and converts at thirty five cents per ada, and it borrows its costing method from the Amaru node proposal. the document behind the expired request
  • The ₳4.6M request that followed funds two tracks, the language and the maintenance of the TypeScript tooling the majority of Cardano developers use directly or through libraries built on it, and says the light node goes to a separate proposal voted on independently. It values five full time equivalents at 1,150,000 dollars including a 15% contingency and converts at twenty five cents per ada, and it adds a periodic independent financial audit of how the funds are used. the document behind the smaller request
  • The research request asks ₳32.9M, which it puts at 7.9 million dollars, for a year long programme of forty two outputs across seven work packages, papers, problem statements, prototypes and improvement proposals, delivered by a consortium of nine research partners with thirty six full time equivalents, and it names three priorities: usability and governance participation, scalability, and post quantum security. the document behind the research request
  • The revised conference request states that it is decoupled from the sponsorship proposal for a second conference, that the budget is reduced by 22% or 550,000 dollars while keeping a tier one event, achieved by going from three stages to two, and that the Foundation raised its own estimated internal contribution from 250,000 to 380,000 dollars to cut external vendor costs. the document behind the revised conference request