{ "@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": "Summary\nEMURGO as a DRep votes YES on the treasury withdrawal titled “Cardano Critical Integrations V2”, with rationale outlined below.\nRationale\nThe integrations delivered under CCI V1, specifically Circle USDCx, LayerZero, Pyth, and Dune Analytics, are now live infrastructure. Keeping them live carries recurring operational costs that must be funded on an ongoing basis. Without a ratified V2 budget, individual maintenance line items would require separate governance actions, each with its own timeline, creating operational gaps in infrastructure the ecosystem now depends on. This proposal addresses that risk in a straightforward way.\n\n\nThe addition of Fireblocks as a new integration is a reasonable extension of scope within this cycle. Institutional custody infrastructure is a practical prerequisite for exchange listings, regulated custody, and broader institutional participation in the Cardano ecosystem. Funding the native Fireblocks integration here, alongside existing maintenance obligations, is more efficient than bringing it as a separate governance action.\n\n\nEMURGO notes that specific vendor-level cost breakdowns are not publicly disclosed due to confidentiality obligations with integration partners. The Steering Committee structure, which includes representation from IO, Cardano Foundation, EMURGO, Midnight Foundation, and Intersect as administrator, provides the governance layer that substitutes for full public granularity. EMURGO is a member of that Steering Committee and accepts the accountability that comes with it. On that basis, and given the operational necessity of the maintenance covered here, EMURGO votes YES.\n" }, "hashAlgorithm": "blake2b-256" }