Governance

Anchor document

https://most-brass-sun.quicknode-ipfs.com/ipfs/QmRdAJN7Hun3sBRWUpGgqZxhr4RknbMDArFevHjHFTLA24
Hash matches the chain Open original

This document doesn't follow CIP-108 or CIP-119, so there is nothing to lay out. The raw JSON is below.

Document

Hash (BLAKE2b-256)
85cd0f924a93871ec458337497325a7aa25a415d89a52f63b73469f93cc94d99
Hash on chain
85cd0f924a93871ec458337497325a7aa25a415d89a52f63b73469f93cc94d99
Raw JSON-LD
{
  "@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": "I'm voting No on the Scalus: Cardano's Application Platform for Building, Launching, and Scaling proposal.\n\nI recognize Lantr Engineering's strong delivery track (Catalyst F11/F13 at 100%, 2025 Treasury Budget on track), the existing Scalus adoption by Hydrozoa, Bifrost, Mesh, Lucid Evolution, and CCL, and the solid governance hygiene (SundaeSwap escrow, credible oversight board, candid 2025 retrospective). That said, I'm voting No on the scope and priorities for two reasons.\n\n1. The demand the proposal is trying to address isn't demonstrated as a Cardano-specific problem.\n\nThe core value proposition here is \"bringing 26M developers from the JVM ecosystem to Cardano.\" But Cardano already has JVM-side tooling in operation, such as Bloxbean's Cardano Client Library (CCL) and Yaci DevKit, and there's no evidence presented that JVM developers aren't coming to Cardano because of the absence of an integrated application platform.\n\n2. Both client diversity and dev tooling are already being addressed by multiple projects in progress.\n\nOn the L1 node side, alongside the Haskell node, Amaru (Rust) and Dingo (Go) are already underway with treasury funding, and the Gerolamo (TypeScript browser) proposal is on the table in this same cycle. The differentiated value of adding a JVM-native L1 node on top of that isn't clear. On the application platform side, Mesh SDK, Lucid Evolution, CCL and others have already become the standard stack for the builder ecosystem, so the case for a separate integrated platform being \"essential\" is weak."
  }
}