{
  "@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 ABSTAIN on the treasury withdrawal titled \"Tweag Core Cardano Infrastructure: Treasury Withdrawal 2026-2028\", with rationale outlined below.\nRationale\nTweag has a long and well-documented track record on Cardano's core infrastructure, and the work packages in this proposal address areas of genuine importance to the ecosystem. The focus on Peras mainnet readiness, including production cryptography, conformance testing, and operational hardening, is directly aligned with one of the most consequential protocol milestones in the current cycle. EMURGO recognises the value of that continuity and does not question Tweag's capability to deliver.\n\n\nThe primary concern is the scale and duration of the commitment being requested. At 39.79M ADA over two years, this is one of the larger single-team allocations in the current budget cycle, and the proposal covers 17 work packages spanning a wide range of scope and maturity. A multi-year, multi-package request of this size benefits from clearer year-by-year prioritisation and more granular milestone gates that allow the community to assess progress before the full amount is committed.\n\n\nEMURGO would be more comfortable supporting this proposal if it were structured in annual tranches, with the second year's funding contingent on verified delivery of the first. This would preserve the continuity of Tweag's work while giving the community appropriate oversight over a commitment of this magnitude. We would encourage the team to consider whether a phased submission would better serve both the project and the broader governance process.\n"
  },
  "hashAlgorithm": "blake2b-256"
}