{ "@context": { "CIP100": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#", "hashAlgorithm": "CIP100:hashAlgorithm", "body": { "@id": "CIP100:body", "@context": { "references": { "@id": "CIP100:references", "@container": "@set", "@context": { "GovernanceMetadata": "CIP100:GovernanceMetadataReference", "Other": "CIP100:OtherReference", "label": "CIP100:reference-label", "uri": "CIP100:reference-uri", "referenceHash": { "@id": "CIP100:referenceHash", "@context": { "hashDigest": "CIP100:hashDigest", "hashAlgorithm": "CIP100:hashAlgorithm" } } } }, "comment": "CIP100:comment", "externalUpdates": { "@id": "CIP100:externalUpdates", "@context": { "title": "CIP100:update-title", "uri": "CIP100:uri" } } } }, "authors": { "@id": "CIP100:authors", "@container": "@set", "@context": { "name": "http://xmlns.com/foaf/0.1/name", "witness": { "@id": "CIP100:witness", "@context": { "witnessAlgorithm": "CIP100:witnessAlgorithm", "publicKey": "CIP100:publicKey", "signature": "CIP100:signature" } } } } }, "authors": [], "body": { "comment": "I vote NO on the Treasury Withdrawal action \"Withdraw 11,787,063 ada for the OpenZeppelin Stack administered by Intersect\" (418df5986f50547ec4a709f1a5bce6b850753ad6614c873386b7c953fee84a9f#0).\n\nAt the time I am writing this rationale, there appears to be little to no support for this treasury withdrawal, with DRep approval currently sitting at 3.94%. When this proposal was first submitted there were multiple questions regarding the potential overlap with the already approved and funded [\"IO: Developer Experience Initiative\"](https://gov.tools/outcomes/governance_actions/73e171a4c0730b4b59ecae271ab89f12a9d56360b02920e1f95107dbdc1d6762#0). With that proposal requesting ₳3,601,926, while this one is requesting ₳11,787,063. Considering the sum requested, I would have expected more community and DRep engagement beyond the first few epochs that this was on-chain. It almost feels like an afterthought.\n\nThe 2025 Cardano Developer Survey highlighted the main pain points for developers were documentation, transaction-building tooling, and the eUTxO learning curve. While Open Zeppelin has a renowned track record in the wider crypto industry, questions remain regarding targeted spending of treasury funds to those areas most in need at the moment. I would like to see what impact the IO: Developer Experience Initiative has on the outcomes of the next Developer Survey, to see if it succeeds in addressing these issues, before evaluating the next areas for improvement and how much funding we are willing to commit to closing those gaps as an ecosystem." }, "hashAlgorithm": "blake2b-256" }