{ "@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\n\nEMURGO as a DRep votes YES on the parameter change titled \"Update Plutus Cost Models\", with rationale outlined below.\n\nRationale\n\nThis governance action updates the Plutus cost models across V1, V2, and V3 to prepare for the van Rossem hard fork and Protocol Version 11. The changes serve three purposes: providing cost model settings for new Plutus primitives that will become available after the hard fork, ensuring consistency by making previously V3-only primitives available in V1 and V2, and updating existing primitive settings based on benchmarking data.\n\nThe new primitives introduced span cryptographic operations, list and array manipulation, and value handling, covering modular exponentiation, multi-scalar multiplication over BLS12-381, array builtins, and MaryEraValue operations. These additions expand the capabilities available to smart contract developers and enable more efficient on-chain computation, particularly for cryptographic and cross-chain use cases.\n\nEMURGO is satisfied that the process behind this change is sound. The changes were recommended by Intersect's Parameter Committee in March 2026, confirmed by the Technical Steering Committee in May 2026, and validated through equivalent enactments on SanchoNet, Preview, and Preprod testnets prior to this mainnet proposal. All cost model values have been benchmarked against the reference architecture, no values are negative, and the action is consistent with constitutional guardrails PCM-01, PCM-02, and PCM-03. For these reasons, EMURGO votes YES.\n\n" }, "hashAlgorithm": "blake2b-256" }