Decision summary
Withdraw 11,787,063 ada for the OpenZeppelin Stack administered by Intersect
gov_action1gxxltxr02p28a398p8c6t08xhpg82wkkv9xgwvuxkly48lhgf20sqlkl2l8 · Treasury withdrawal
Recorded by a member of the Institute · published 9 Oct 2026
What was reviewed
The proposal metadata anchor, whose on-chain hash matched. It asks for 11,787,063 ada (USD 1,831,000 for delivery at a USD 0.16 reference rate plus a 3% Intersect fee), 20% at signature and the rest over four quarterly milestones, converted to stablecoin at signature, with an oversight committee and sweep-back of unused funds.
Primary rationale
OpenZeppelin's security record is not the issue, and Intersect has set this up properly: milestone payments it verifies, an independent oversight committee, automatic sweep-back of unused funds. I am voting No mainly because the treasury has already funded part of this work and the proposal does not say so. In May 2026 DReps approved Input Output's Developer Experience Initiative, which includes an OpenZeppelin-style contracts library now in development. This proposal says Cardano has no standardised, audited contract library and mentions neither that work nor the other libraries in the ecosystem. An 11.79M ada request should start from what exists and explain what it adds. I also cannot rebuild the cost. Delivery is five equal payments of 2,288,750 ada with no roles, headcount or day rates. The contract language, which drives staffing, audit method and maintenance, is picked after funding, and 20% goes out at signature before anything is delivered. S&P Global's agreement to buy OpenZeppelin came after the proposal was written, and there is no disclosure or change-of-control provision. Nothing improper in that, but the counterparty has materially changed. A Yes would fund a second library before the first is delivered and compared, on a budget I could not check. My No has a cost too: the work does not start on this timeline, and OpenZeppelin may not come back.
Risks
The obvious risk is that Cardano passes up a trusted, audited standard that could have shortened the path for institutions looking at the chain. OpenZeppelin says it will come back with a revised proposal regardless of this vote. The conditions below are what I would want in it. Funding overlapping libraries without a comparison lets size and reputation stand in for a gap analysis. That is a poor precedent. With the amount fixed at USD 0.16 and converted at signature, the treasury carries the price movement until then and the vendor none after. The proposal does not mention it.
Uncertainty
How the library differs from, depends on or duplicates Input Output's. Not stated. The contract language and toolchain. To be decided after funding. How the 22 researcher-weeks of security capacity and the five equal payments were derived, and on what roles and rates. Not stated. Whether the acquisition affects staffing, licensing or continuity. Not stated. Whether OpenZeppelin has delivered production eUTxO work on Cardano. Midnight is cited; I found no Cardano artefacts. I obtained no expert or peer input before the deadline.
Conflicts
I worked at the Cardano Foundation until mid-2023 and have had no role, payment or equity there since. The Foundation is one of six entities on this withdrawal's Oversight Committee, would get a dedicated technical account manager, and is named as a recipient in year two. Given the time and no ongoing tie, I treat it as a past association, disclosed so delegators can judge for themselves.
What could change this position
A published gap and overlap analysis against the Input Output library, the Cardano Foundation's CIP-113 work and other maintained libraries. A contract language and toolchain fixed before funding. An itemised budget: roles, headcount, rates, and how the security retainer was sized. A named team with Aiken or Plutus delivery that can be checked. No payment at signature, or a first milestone instead. Disclosure of the S&P Global deal with a change-of-control provision.
Proposal source
Submitted on chain with Intersect as metadata author and administrator. The proposal says OpenZeppelin brought it forward independently, without Intersect's sponsorship or endorsement.