Cross-Network Atomic DvP/PvP Settlement

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.

W-A. Cross-network atomicity + finality-compatibility + settlement-risk window (ART-58) -> asset-leg DvP atomicity (507) -> FX-leg PvP (511). The flagship Wave-13 decision chain: is this tokenized settlement all-or-nothing across the cash network and the asset network?

OpenChainGraph · 3 Steps settlement mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII

Chain Stages · 3 Steps

1 ROOT · D0 node

Cross-Network Atomic Settlement Validator art-58-cross-network-settlement-validator

atomicity_verdict and settlement_risk_window (H1) feed the DvP validator

MCP Call · validate_cross_network_settlement

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

↓

2 D2 node

Canton DvP Atomicity Validator 507-canton-dvp-atomicity-validator

asset-leg atomicity (H2) feeds the PvP validator

MCP Call · validate_canton_dvp_atomicity

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

↓

3 TERMINAL · D3 node

Multi-Currency PvP Validator 511-multi-currency-pvp-validator

Exports composite cross-network settlement artifact with execution_hash (H3), final stage

MCP Call · validate_pvp_settlement

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

Question: Our trade settles across two networks that do not talk to each other. Does either side still face settlement risk? Run the AINumbers MCP tool `run_chain` with {"chain":"wholesale-settlement-cross-network-dvp"} and read `511-multi-currency-pvp-validator.verdict`. Re-run with `inputs` for `511-multi-currency-pvp-validator`, reusing the values that result echoed, with `has_unwind_procedure` set to false. 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/wholesale-settlement-cross-network-dvp.html

Cross-Network Atomic DvP/PvP Settlement

Ask your agent