OpenChainGraph Suite · CONTRACT A3 · arch #5

Canton Counterparty Onboarding 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.

KYA screening and party allowlist validation for Canton Network onboarding.

OpenChainGraph · 1 Step compliance mandate Hash-Anchored §4 chain_depth:1 Client-Side · Zero PII
Chain Topology — Canton Party Allowlist Validator
§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 · 1 Step
1 ROOT · TERMINAL · D0 node
Canton Party Allowlist Validator 509-canton-party-allowlist-validator
allowlist_verdict,fatf_flags,parties_approved: Exports counterparty onboarding mandate, final stage
MCP Call · validate_canton_party_allowlist
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_canton_party_allowlist",
    "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.