{
  "@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 treasury withdrawal titled “IO & VacuumLabs: Enhancing Plutus — Performance, Correctness, and Usability”, with rationale outlined below. This represents a change from our earlier ABSTAIN position.\n\nRationale\n\nEMURGO previously abstained on this proposal, citing caution around the volume of treasury commitments being considered in the current cycle. Having since assessed the aggregate spend across approved and pending proposals, we are satisfied that this proposal fits within responsible treasury limits and that the prioritisation concern that drove our earlier position no longer holds.\n\nOn further reflection, the conformance testing framework and Agda formalization delivered here are not supplementary infrastructure. They are a prerequisite for alternative node implementations to verify their Plutus evaluators ahead of Dijkstra. Deferring this work creates a gap that compounds the longer it remains unfunded, and the sequencing risk of waiting now outweighs the timing concern that informed our abstention.\n\nThe VacuumLabs co-venture further reinforces this position. Distributing Plutus maintenance expertise across multiple expert organisations reduces a single-point-of-failure risk in one of the most critical parts of the stack, and that structural benefit is time-sensitive as node diversity becomes a practical reality. Combined with IO’s demonstrated accountability within the treasury framework, EMURGO is satisfied this is a well-governed proposal that serves the ecosystem’s foundational interests. For these reasons, EMURGO changes its vote to YES."
  },
  "hashAlgorithm": "blake2b-256"
}