{
  "@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": "I vote YES on the hard fork initiation action titled “Hard Fork to Protocol Version 11 ('van Rossem' Hard Fork)” (fdd468da5cc4ac8431dcd7e2b3211666c73bc229f85879469f67f1d9d51d344d#0). This vote is submitted as both SPO and DRep and can be found in the same transaction.\n\nI had wanted to hold off on voting until after the epoch boundary on June 28, 2026, and vote in epoch 640 as it has been my personal preference that this action not ratify on June 28, causing an enactment on July 3. Why? The July 3 epoch boundary lands on a Friday, late for UTC time zones and right before a major US holiday on July 4. Yes, we have had upgrades land close to major holidays before and this is an intra-era upgrade and so should have little-to-no breaking changes. However, given all of the headlines that Cardano has had to contend with recently, I’d much rather see this hard fork ratify on July 3 with an enactment on July 8 when we can guarantee more hands on deck to resolve any potential issues. They say, “don’t push to production on Friday”, it probably should count for hard forks too.\n\nWith that said, I do want to vote YES. This hard fork has been many months in the making, with Plutus Cost Model updates and hard fork initiation actions having passed through SanchoNet, Preview and Preprod test networks over the months of April, May and June.\n\nReadiness is now looking strong. 87% of block production for this epoch, at time of writing, has been on node version 11. This satisfies the HARDFORK-04 constitutional guardrail of “At least 85% of stake pools by active stake should have upgraded to a Cardano Blockchain node version that is capable of processing the rules associated with the new protocol version”. This week has also seen massive progress from exchanges, with 77.37% readiness by liquidity being reported.\n\nI have conceded to submitting my vote this epoch as there is a non-zero chance that this ratifies while I am away from my computer later today and the ledger does not care about our individual preferences, therefore this is submitted now to maintain my voting record. My voting weight certainly is not of any size to sway things one way or another, especially as a sub-1M SPO."
  },
  "hashAlgorithm": "blake2b-256"
}