This proposal funds a 12-month program by Harmonic Laboratories to deliver:
Funds are managed through audited smart contract escrow with milestone-based disbursement and independent oversight.
Assessment: Pass
Assessment: Strong
Assessment: Medium
| Dimension | Score (1–5) |
|---|---|
| Constitutional clarity | 5 |
| Governance quality | 4 |
| Execution credibility | 4 |
| Ecosystem value | 5 |
| Risk balance | 3 |
RCADA supports this treasury withdrawal proposal from Harmonic Laboratories (HLabs) as a high-impact infrastructure investment aligned with Cardano’s long-term decentralization, developer accessibility, and ecosystem resilience.
The proposal presents a coherent and well-structured funding request across three interrelated workstreams: Gerolamo (a TypeScript-based node implementation), Pebble (a developer-friendly smart contract language and tooling suite), and ongoing maintenance of critical TypeScript ecosystem libraries. While these components are bundled, we find that they form a vertically integrated and mutually reinforcing stack spanning infrastructure, developer experience, and ecosystem continuity. This distinguishes the proposal from broader multi-project bundles and supports its evaluation as a unified initiative.
From a governance and treasury perspective, the proposal demonstrates a mature and robust design. Funds are held in audited smart contract escrow, disbursements are milestone-based, and an independent oversight board with credible ecosystem representation has meaningful enforcement powers, including the ability to pause funding and co-sign releases. Importantly, unused funds are automatically returned to the treasury at contract expiry. These mechanisms provide strong safeguards against misuse and materially reduce execution risk.
We also recognize the strategic importance of the proposed deliverables. Gerolamo contributes directly to client diversity and decentralization, particularly through its light-node and browser-based capabilities. Pebble lowers the barrier to entry for a large pool of Web2 and EVM developers, expanding Cardano’s potential developer base without displacing existing tooling. Continued maintenance of foundational TypeScript libraries ensures ecosystem stability across protocol upgrades and reduces fragmentation risk. Collectively, these contributions align with the Cardano 2030 vision and represent meaningful public goods for the network.
That said, this proposal is not without concerns.
First, the inclusion of a 25% contingency buffer within the upfront funding ask raises important governance considerations. While the justification—accounting for uncertainty and optimism bias in complex R&D work—is reasonable, and while the escrow model ensures that these funds are not automatically disbursed, we remain cautious about the precedent this sets. Large pre-allocated contingencies, even when refundable, risk inflating treasury requests and reducing funding discipline over time. We strongly encourage future proposals to explore more conditional or milestone-triggered contingency mechanisms rather than incorporating significant buffers into the initial ask.
Second, although we find the bundling in this case to be justified due to the tight coupling of the three workstreams, we reiterate our general preference for modular governance actions wherever feasible. Bundling inherently limits DRep granularity in decision-making and should be applied carefully. This proposal sits at the acceptable boundary of that practice, but broader or less cohesive bundling approaches would likely not receive the same level of support.
In summary, RCADA views this proposal as meeting the bar for responsible treasury allocation: it is strategically aligned, technically credible, and supported by strong governance and oversight mechanisms. Our support should be interpreted as endorsement of this specific implementation and structure—not as blanket approval of bundled proposals or large upfront contingencies as a general standard.
We therefore vote YES, while signaling clearly that future proposals adopting similar patterns—particularly around contingency design—may face increased scrutiny and could result in an Abstain or No vote if not sufficiently justified or refined.