Anchor document

{
  "@context": {
    "CIP100": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#",
    "authors": {
      "@container": "@set",
      "@context": {
        "name": "http://xmlns.com/foaf/0.1/name",
        "witness": {
          "@context": {
            "publicKey": "CIP100:publicKey",
            "signature": "CIP100:signature",
            "witnessAlgorithm": "CIP100:witnessAlgorithm"
          },
          "@id": "CIP100:witness"
        }
      },
      "@id": "CIP100:authors"
    },
    "body": {
      "@context": {
        "comment": "CIP100:comment",
        "externalUpdates": {
          "@context": {
            "title": "CIP100:update-title",
            "uri": "CIP100:uri"
          },
          "@id": "CIP100:externalUpdates"
        },
        "references": {
          "@container": "@set",
          "@context": {
            "GovernanceMetadata": "CIP100:GovernanceMetadataReference",
            "Other": "CIP100:OtherReference",
            "label": "CIP100:reference-label",
            "referenceHash": {
              "@context": {
                "hashAlgorithm": "CIP100:hashAlgorithm",
                "hashDigest": "CIP100:hashDigest"
              },
              "@id": "CIP100:referenceHash"
            },
            "uri": "CIP100:reference-uri"
          },
          "@id": "CIP100:references"
        }
      },
      "@id": "CIP100:body"
    },
    "hashAlgorithm": "CIP100:hashAlgorithm"
  },
  "hashAlgorithm": "blake2b-256",
  "body": {
    "comment": "Constitution v2.4 retains and strengthens the governance architecture introduced in earlier versions, particularly the clear definition of roles and thresholds, the standardized and immutable governance‑action document model, and the comprehensive guardrails around protocol changes and treasury withdrawals.\n​\nBy formally removing non‑binding “expectation” and “encouragement” clauses and the mandated CC code of conduct from the constitutional text, this version focuses the Constitution on enforceable rules and on‑chain guardrails, while leaving codes of conduct and tooling expectations to be defined and evolved through community practice and separate processes. This is more consistent with a durable, technology‑aligned constitutional document.\n​\nThe removal of the Budget Info Action mechanism, combined with the re‑assignment of its audit, administrator, and reporting safeguards directly to all Treasury Withdrawal actions, simplifies governance while materially improving accountability. Every withdrawal must now meet the same high standard for transparency, auditability, and administrator responsibility, which aligns with best practices for treasury risk management.\n​\nThe targeted reversions from v2.3 to restore the original v1.0 wording on ada “owners”, custodians, and independent audits address EMURGO’s specific concerns without weakening the underlying constitutional requirements for custody and oversight. This adjustment supports broad stakeholder acceptance and practical ratifiability while preserving the substantive protections introduced in later versions.\n​\nTaken as a whole, v2.4 is a carefully scoped refinement rather than a structural redesign. It maintains the improvements I previously supported in v2.3, clarifies and simplifies where experience has shown friction, and strengthens the link between on‑chain governance actions and immutable, auditable documentation. For these reasons, it merits a YES vote as the most coherent and operationally sound version of the Cardano Constitution to date."
  }
}