Canton Securities Issuance Chain

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

Reading mode (READINESS-BUILD): These checks can be gathered in any order; the sequence below is for convenience. Regulatory classification and Daml lifecycle validation each check a separate fact about the security and are combined into one readiness answer, not an executed issuance.

Regulatory classification and Daml lifecycle validation for tokenized securities.

OpenChainGraph · 2 Steps compliance mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII

Live Execution

This page is the chain definition (plan). To run the chain step by step in your browser, with each step's kernel executing in-page and a composite hash over the outputs, open the live runner:

▶ Run this chain in your browser

Chain Stages · 2 Steps

1 ROOT · D0 node

Digital Asset Regulatory Classifier 510-digital-asset-regulatory-classifier

frameworks_applied,mifid_instrument,dlt_pilot_eligible feed Stage 2 lifecycle validator

MCP Call · classify_digital_asset_regulatory

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "classify_digital_asset_regulatory",
    "arguments": {}
  },
  "id": 1
}

↓

2 TERMINAL · D2 node

Tokenized Security Lifecycle Validator 512-tokenized-security-lifecycle-validator

lifecycle_verdict,daml_gaps: Exports securities issuance mandate, final stage

MCP Call · validate_tokenized_security_lifecycle

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_tokenized_security_lifecycle",
    "arguments": {}
  },
  "id": 1
}