{"@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"}}},"hashAlgorithm":"blake2b-256","body":{"comment":"As a DRep, I decided to vote NO on the proposal: Withdraw 11,787,063 ada for the OpenZeppelin Stack administered by Intersect\n\nOur rationale:\n\nThe proposal's direction is correct. A credible library with audited reference implementations could lower the barrier to entry for Cardano developers and improve confidence among institutional integrators.\n\nHowever, the current proposal does not provide enough evidence that the proposed work is sufficiently differentiated from ongoing Cardano ecosystem initiatives.\n\nThere is a significant risk of duplication or fragmentation. The Input Output contracts-library repository already describes an OpenZeppelin-like reusable Cardano contracts library, including on-chain and off-chain components. Its public roadmap includes areas such as governance, upgradeability, CIP-113-related work, vesting, and DeFi compatibility.\n\nThe Cardano Foundation is also working on CIP-113 programmable-token infrastructure and regulated-asset reference implementations.\n\nThese projects are not identical to the OpenZeppelin proposal, but they demonstrate that important parts of the proposed infrastructure are already being developed elsewhere.\n\nThe proposal states that the specific Cardano smart-contract language will be selected during the initial evaluation phase. This means DReps are being asked to approve a large budget before the core technical architecture, language choice, and exact deliverables are finalized.\n\nThe choice between Aiken, Plutus-based approaches, and off-chain frameworks directly affects staffing, implementation costs, testing methodology, auditability, and long-term maintenance. A budget cannot be meaningfully assessed when a central technical decision is deferred until after funding.\n\nThe proposal does not provide a meaningful cost breakdown. There are no clear details of the number of full-time equivalent contributors, hourly or daily rates, long-term maintenance, etc.\n\nOpenZeppelin has extensive experience with EVM-based smart-contract infrastructure and does have relevant non-EVM UTxO-related experience through its Midnight/Compact work. However, this is not the same as a demonstrated track record of delivering Cardano eUTxO contracts using the Cardano toolchain, including Aiken or Plutus.\n\nAt a minimum, a resubmission should include:\n\n- A public gap and overlap analysis covering the IOG contracts-library, Cardano Foundation CIP-113 work, CF regulated-asset references, and other relevant ecosystem projects.\n\n- A fixed technical scope before funding, including the selected language and frameworks.\n\n- A complete budget showing named roles, FTE allocation, rates, etc.\n\n- A named Cardano technical team with demonstrated Aiken, Plutus, and eUTxO experience, together with declared availability and responsibility for each deliverable.\n\nIf you'd like to support my work, consider delegating to the MANDA pool and backing me as a DRep. Your support is the only way I can get time for governance.\n\nMANDA Pool ID:\npool1c3fjkls7d2aujud8y5xy5e0azu0ueatwn34u7jy3ql85ze3xya8\n\nMy DRep ID:\ndrep1y2m0g4r66pyaw3p7u454wc0p4f0ygm8ueaev0mgd3tvwm7sskqwqp\n\nBuy me a beer:\nhttps://pay.cexplorer.io/pay/c0410d5b237b6ec0"}}