Anchor document

{
  "@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": "Vote: YES\n\nThis is a Treasury Withdrawal, \"Scalus 2026: Maintenance, Dijkstra Readiness, Interoperability & Application Runtime\" (gov_action1xg69v73lfzkwyhhuz583x6geyc2ewn3r96sxuqj3wqvrrk0yfpksqqa63yc), submitted June 29, 2026 with voting closing August 2, 2026. Lantr Engineering requests ₳2,464,844 (approximately $394,375 at the $0.16/ADA reference rate) over nine months, July 2026 through March 2027, to maintain the Scalus toolchain — a JVM-native development stack for writing, evaluating, testing, and deploying Cardano smart contracts — keep it compatible with the Dijkstra hard fork including Plutus V4 and new builtins, improve Java/Kotlin and JavaScript/TypeScript interoperability, and deliver a scoped first application runtime. No ADA burning is involved.\n\nThis is a resubmission that took DRep feedback seriously rather than repackaging it. The ask fell from ₳8,503,000 over twelve months to ₳2,464,844 over nine — a 71% reduction — with the team cut from 8.25 to 2.25 FTE, the standalone L1 node and L2 integration removed from scope, the formal verification track dropped, the contingency buffer eliminated entirely, and pricing set at a conservative $0.16/ADA. Few proposals in this cycle have responded to rejection by actually shrinking. The accountability apparatus matches the strongest structures Dracula DAO has seen: funds held in audited SundaeSwap escrow contracts, disbursements requiring approval from a three-member independent oversight board drawn from Blink Labs, the Cardano Foundation, and IOG, quarterly technical review by No.Witness Labs, public quarterly reports and transaction journals, and automatic return of unused funds to the treasury. Lantr's disclosed track record supports the request: ₳328,000 across two Catalyst F11 projects and ₳657,692 from the 2025 Treasury, both fully received with all milestones delivered. The tooling has real users — Scalus is already a dependency of Gummiworm L2, the Bifrost bridge, SugarRush DEX, Vela stablecoin, and DID/DIDComm work — so the maintenance milestone protects infrastructure the ecosystem already depends on rather than speculating on adoption that has not happened.\n\nThe structural objection still applies. This is priced as 2.25 FTE of a named team's time for nine months, not as a grant paid against completed features, and there was no competitive bidding — Scalus is Lantr's own product, and the treasury is funding its upkeep. Dracula DAO names that gap plainly. The application runtime component is also the weakest part of the request: unlike maintenance and hard-fork compatibility, it is new scope whose demand is asserted rather than demonstrated, and it is the piece most likely to consume budget without producing something the ecosystem misses if it never ships. DRep sentiment is currently against, at roughly ₳1.97B no to ₳1.16B yes.\n\nDracula DAO votes YES. Developer tooling that keeps working through a hard fork is unglamorous, foundational, long-term infrastructure — exactly the category this DREP exists to favor over tactical spending. If Scalus breaks at Dijkstra, every project built on it breaks with it, and the cost of that failure lands on builders who made no such request of the treasury. At ₳2.46M this is one of the smallest asks of the cycle, roughly a fifth of the Bifrost Phase 1 request and under half of the Hydra v2 hardening grant, for work with immediate and verifiable consequences. Money moves only when an independent board with no stake in the outcome signs off against a defined quarterly milestone, and undelivered funds return automatically. That is not the competitive completion-grant model Dracula DAO would prefer, but it is honest gating on real deliverables from a team that has delivered before.\n\nDracula DAO will judge any 2027 continuation on whether the runtime component found genuine users and whether the Dijkstra compatibility work shipped on schedule. Maintenance funding earns renewal by keeping things working; new scope earns it by being adopted."
  },
  "hashAlgorithm": "blake2b-256"
}