Anchor document

{
  "@context": {
    "CIP100": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#",
    "hashAlgorithm": "CIP100:hashAlgorithm",
    "body": {
      "@id": "CIP100:body",
      "@context": {
        "comment": "CIP100:comment"
      }
    },
    "authors": {
      "@id": "CIP100:authors",
      "@container": "@set"
    }
  },
  "hashAlgorithm": "blake2b-256",
  "body": {
    "comment": "We vote NO on the proposal to withdraw 11,787,063 ada for the OpenZeppelin Stack administered by Intersect. We value OpenZeppelin’s capability and welcome their engagement with the Cardano ecosystem. Our objection is to the proposal’s scope, structure, and price.\n\nFirst, the core deliverable duplicates work the treasury has already funded. Input Output’s Developer Experience Initiative (3,601,926 ada, approved in May) already commits to building an OpenZeppelin-style smart contract library with at least five ready-to-audit contracts. The Cardano Foundation maintains audited CIP-113 infrastructure, and MeshJS, TrustLevel, and Anastasia Labs also publish open-source libraries. The proposal mentions none of these efforts, and the public question from the author of the IOG library remains unanswered.\n\nSecond, the proposal lacks transparency. The programming language has not been chosen, even though it determines staffing, costs, and auditability. The budget gives no headcount, rates, or maintenance costs. Two of the three reference implementations are poorly targeted, and the team has not demonstrated eUTxO experience with Aiken or Plutus.\n\nWe recommend a single, unified developer support strategy for 2027, and we will consider a resubmission that includes a public overlap analysis, a fixed scope, a detailed budget, and a named Cardano technical team."
  },
  "authors": []
}