OpenChainGraph Suite · CONTRACT A3 · arch #5

Canton DvP Readiness 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.

Validate DvP atomicity and collateral eligibility for Canton settlement. PFMI P12 atomicity model + DTC/Fed/HQLA eligibility verdict.

OpenChainGraph · 2 Steps collateral mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII
Chain Topology — Canton DvP Atomicity Validator → Tokenized Collateral Eligibility Checker
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
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
Canton DvP Atomicity Validator 507-canton-dvp-atomicity-validator
dvp_verdict,atomicity_model,finality_model feed Stage 2 collateral eligibility
MCP Call · validate_canton_dvp_atomicity
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_canton_dvp_atomicity",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 TERMINAL · D2 node
Tokenized Collateral Eligibility Checker 505-tokenized-collateral-eligibility-checker
hqla_tier,dtc_eligible,haircut_pct: Exports DvP readiness mandate, final stage
MCP Call · check_tokenized_collateral_eligibility
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_tokenized_collateral_eligibility",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
▶ Run this chain (live) browser · real execution · composite §4 hash
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition — no new hash is minted. Available after hash computation.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: Does our delivery-versus-payment design settle both legs atomically with irrevocable finality, or does it leave Herstatt risk open?
Run the AINumbers MCP tool `run_chain` with {"chain":"canton-dvp-readiness"} and read `507-canton-dvp-atomicity-validator.verdict`.
Re-run with `inputs` for `507-canton-dvp-atomicity-validator`, reusing the values that result echoed, with `platform` changed so platform is traditional_csd with every other input unchanged. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/canton-dvp-readiness.html