{
  "@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\nYoroi DRep abstains on \"IO & VacuumLabs: Enhancing Plutus — Performance, Correctness, and Usability\". This position is not a reflection on the quality of the proposal or the teams behind it, but a considered view on timing and treasury prioritisation in the current cycle.\nRationale\nTechnical merit is not in question. The targeted primitives, scope check investigation, and conformance testing framework are well-scoped and address real gaps. Each deliverable is tied to a concrete artifact, making progress independently verifiable. Yoroi has no reservations about the substance of the work proposed.\nTiming and aggregate treasury commitments. This cycle has seen significant treasury obligations across core infrastructure. Yoroi believes it is appropriate to pause and assess the cumulative impact before approving further large withdrawals, even well-justified ones. The proposal would benefit from being considered in a cycle where the broader funding landscape is less congested.\nA question of sequencing, not capability. IO's track record within the Intersect framework, including return of unused funds, and the VacuumLabs partnership model are both genuine positives. Yoroi would look favourably on a resubmission with the same scope and governance structure in a future funding cycle.\nConclusion\nYoroi's abstention is not a rejection of this proposal or the teams behind it. It reflects a cautious approach to treasury commitments at a moment when the community is still calibrating aggregate spend across the current cycle. Yoroi encourages resubmission and hopes to be in a position to support this work in the future.\n"
  },
  "hashAlgorithm": "blake2b-256"
}