{
  "@context": {
    "@language": "es-ES",
    "CIP100": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#",
    "CIP119": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0119/README.md#",
    "hashAlgorithm": "CIP100:hashAlgorithm",
    "body": {
      "@id": "CIP119:body",
      "@context": {
        "summary": "CIP119:summary",
        "rationale": "CIP119:rationale",
        "references": "CIP119:references"
      }
    }
  },
  "hashAlgorithm": "blake2b-256",
  "body": {
    "summary": "IO: Cardano High Assurance Technical Collaboration",
    "rationale": "**Vote: Yes**\n\nFormal verification is foundational infrastructure for Cardano's next phase. As smart contracts grow in complexity — composing multiple scripts, interacting with oracles, MCPs, and autonomous agents — the attack surface expands beyond what testing and manual audits can reliably cover. Formal methods are the only approach that can prove the absence of vulnerabilities, not merely detect the ones testers thought to look for.\n\nCardano's eUTxO model is uniquely suited to formal reasoning: discrete state, determinism, no side effects. Blaster operating on UPLC as the common compilation target means investment in verification infrastructure benefits every smart contract language simultaneously — Aiken, Pebble, Scalus, Futura, and any future language that compiles to UPLC.\n\nThe technical scope is well-designed. Extending Blaster from single-contract to DApp-level verification addresses a real gap: production protocols are multi-script systems, and verifying scripts in isolation cannot capture cross-script invariants. The equivalence checking tool enables aggressive UPLC optimization with machine-checked correctness guarantees, directly improving throughput utilization. The Common Vulnerability Library and VS Code extension lower the barrier so that formal verification becomes part of the standard development workflow rather than an expert-only capability.\n\nThe collaboration model distributing work across Lantr, Harmonic Labs, SAIB, Midgard Labs, TxPipe, and No.Witness Labs is a welcome step toward decentralizing critical tooling expertise beyond IO.\n\nCBDE addresses a real friction point. Multi-day environment setup is a measurable barrier to developer adoption, and packaging the full high-assurance toolkit into a single-command initialization is a practical contribution to onboarding.\n\n**However, this approval comes with noted concerns:**\n\nThe budget allocates 86% to \"Development\" across both workstreams but provides no breakdown by collaborating team. The pr",
    "references": []
  },
  "authors": [
    {
      "name": "drep15jspgw8ea9pw3w0fwyqam2lw58ulw7z6qhr8qyuah7j0yj962w7",
      "witness": {
        "witnessAlgorithm": "ed25519",
        "publicKey": "078c04a088ee52fe58d3257993ea6ec90f0b1dd59e4456a6b0e97e81f09525df"
      }
    }
  ]
}