{
  "@context": {
    "@language": "en-us",
    "CIP100": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#",
    "CIP136": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0136/README.md#",
    "hashAlgorithm": "CIP100:hashAlgorithm",
    "body": {
      "@id": "CIP136:body",
      "@context": {
        "references": {
          "@id": "CIP100:references",
          "@container": "@set",
          "@context": {
            "GovernanceMetadata": "CIP100:GovernanceMetadataReference",
            "Other": "CIP100:OtherReference",
            "label": "CIP100:reference-label",
            "uri": "CIP100:reference-uri",
            "RelevantArticles": "CIP136:RelevantArticles"
          }
        },
        "summary": "CIP136:summary",
        "rationaleStatement": "CIP136:rationaleStatement",
        "precedentDiscussion": "CIP136:precedentDiscussion",
        "counterargumentDiscussion": "CIP136:counterargumentDiscussion",
        "conclusion": "CIP136:conclusion",
        "internalVote": {
          "@id": "CIP136:internalVote",
          "@container": "@set",
          "@context": {
            "constitutional": "CIP136:constitutional",
            "unconstitutional": "CIP136:unconstitutional",
            "abstain": "CIP136:abstain",
            "didNotVote": "CIP136:didNotVote",
            "againstVote": "CIP136:againstVote"
          }
        }
      }
    },
    "authors": {
      "@id": "CIP100:authors",
      "@container": "@set",
      "@context": {
        "did": "@id",
        "name": "http://xmlns.com/foaf/0.1/name",
        "witness": {
          "@id": "CIP100:witness",
          "@context": {
            "witnessAlgorithm": "CIP100:witnessAlgorithm",
            "publicKey": "CIP100:publicKey",
            "signature": "CIP100:signature"
          }
        }
      }
    }
  },
  "hashAlgorithm": "blake2b-256",
  "body": {
    "govActionId": "gov_action1zljrlljt9cxlz7ra2nep43nxg0r54wcnrgexyuhuam9ah0ws607qq2vcg4x",
    "summary": "Tingvard judges this Treasury Withdrawals governance action constitutional.",
    "rationaleStatement": "This governance action is properly framed as a Treasury Withdrawals action and must therefore be assessed under Article II, Section 6 and Article II, Section 7 of the Constitution, together with the applicable treasury guardrails in Appendix I.\n\nThe proposal satisfies Article II, Section 6, §1 by presenting the governance action in a standardized and legible format. It includes an abstract, motivation, rationale, work package structure, budget justification, administration model, refund conditions, Net Change Limit statement, audit and oversight statement, and references to supporting proposal documents.\n\nThe proposal satisfies Article II, Section 6, §2 by providing sufficient rationale for the requested withdrawal. It explains that the funding is intended to support three related core infrastructure work packages: Peras v1 mainnet readiness and maintenance, History Expiry, and Conformance Testing for Peras and Leios. These work packages are presented as interdependent parts of a delivery pipeline for resilience, scalability, faster finality, and node sustainability.\n\nThe action satisfies Article II, Section 7, §1 by specifying the terms of the withdrawal. The proposal requests 18,263,496 ada to fund delivery over 2026–2027. It identifies the purpose of the withdrawal, the work packages to be funded, the delivery model, the relevant cost basis, and the circumstances under which unused or reduced-scope funds will be returned to the Treasury.\n\nThe proposal satisfies Article II, Section 7, §2 by disclosing prior treasury receipts. It states that Tweag has previously been accountable for treasury-funded work, with 11,070,322.68 ada allocated within the Treasury Smart Contract.\n\nThe proposal satisfies Article II, Section 7, §3 and TREASURY-02a by stating that the requested amount does not, at the time of submission, on its own or in aggregate, breach the applicable 350M ada Net Change Limit covering Epoch 613 to Epoch 713. It also satisfies TREASURY-03a because the withdrawal is denominated in ada.\n\nThe proposal satisfies Article II, Section 7, §4 by including audit and oversight within the funding and administration model. It states that audit and oversight costs are included within the overhead applied to the proposal, that Intersect’s administration fee covers administrative oversight, and that independent oversight will be provided through Intersect and a technically capable third party. It also includes reporting obligations, milestone-based disbursement controls, public demos, regular status updates, and community-facing project tracking.\n\nThe proposal satisfies Article II, Section 7, §5 by designating Intersect as the proposal, contract, and audit administrator. It further states that a written off-chain legal contract will be created between Tweag and Cardano Development Holdings, administered by Intersect, with project delivery monitored through Intersect’s delivery assurance function and supported by a third-party assurer.\n\nThe proposal satisfies Article II, Section 7, §6 by stating that funds will be administered through the Treasury Reserve Smart Contract and Project-Specific Smart Contract framework. It states that all instances of the relevant contracts cannot be staked with a Stake Pool Operator and will be delegated to the auto-abstain predefined DRep. It also states that a dashboard will be available for the community to audit the TRSC or PSSC and track metrics related to the withdrawn ada.\n\nTingvard therefore finds that the proposal satisfies the applicable constitutional requirements for a Treasury Withdrawals action.",
    "precedentDiscussion": "This decision is consistent with prior Tingvard assessments of treasury withdrawal proposals where the constitutional review focuses on whether the proposal provides a clear withdrawal purpose, delivery period, cost basis, prior treasury receipt disclosure, audit and oversight structure, administrator designation, custody protections, refund conditions, and Net Change Limit compliance.\n\nThis proposal concerns core protocol infrastructure and related delivery support. The Constitution does not require the CC to determine whether Peras, History Expiry, or Conformance Testing should be prioritized over other infrastructure needs. That is a policy and technical prioritization question for DReps and ada owners.\n\nFor constitutional purposes, the proposal provides a sufficiently clear scope, names the administrator, describes the smart contract custody framework, includes audit and oversight commitments, discloses prior treasury funding, and defines refund conditions for unused or reduced-scope funds.",
    "counterargumentDiscussion": "One potential counterargument is that the proposal combines three work packages rather than submitting them as separate treasury withdrawals. Tingvard does not find this unconstitutional. The proposal explains that the work packages are interdependent and form a single delivery pipeline. Combining related workstreams is not a constitutional defect where the proposal still identifies the funded activities, cost basis, administration model, and oversight structure.\n\nAnother possible concern is that some success conditions depend on broader governance or ecosystem activation, including future hard fork activation and CIP progression. The proposal addresses this by distinguishing between ready-for-activation deliverables and governance outcomes. It commits to deliverables such as merged code, reproducible releases, runbooks, benchmarks, and governance-action packages. This separation is sufficient for constitutional review.\n\nA further concern could be the size of the requested amount. The requested withdrawal is significant, but the Constitution does not require the CC to judge whether the amount is the best possible use of treasury funds. The proposal provides a cost basis, delivery structure, administration model, audit and oversight commitments, refund conditions, and Net Change Limit compliance. Whether the amount is proportionate is primarily a DRep question.\n\nAnother concern could be that some details will be finalized in the legal contract between Tweag and Cardano Development Holdings. Tingvard does not find this unconstitutional, because the submitted proposal already provides the core terms, work packages, administration structure, oversight model, refund conditions, and public reporting commitments required for constitutional review.",
    "conclusion": "Tingvard finds this governance action constitutional.\n\nThe proposal satisfies Article II, Section 6 and Article II, Section 7 by providing a clear withdrawal purpose, defined work packages, delivery structure, prior funding disclosure, audit and oversight commitments, named administrator, refund conditions, Net Change Limit compliance, and treasury custody protections.",
    "internalVote": {
      "constitutional": 4,
      "unconstitutional": 0,
      "abstain": 0,
      "didNotVote": 1,
      "againstVote": 0
    },
    "references": [
      {
        "@type": "RelevantArticles",
        "label": "Cardano Blockchain Ecosystem Constitution",
        "uri": "ipfs://bafkreieyuknozbtewyurfqoagvplvykadn6a4u6wglupavdz46bbsnnl6e"
      }
    ]
  },
  "authors": [
    {
      "name": "Tingvard",
      "imageUrl": "ipfs://QmPkHXdK6GLtDNyyKFBWRwARFEy9TPFcbpDganixmRXwWJ"
    }
  ]
}