Map your settlement asset (CBM token, tokenized deposit, regulated stablecoin, e-money token) against its legal-finality regime (EU SFD 98/26/EC, CPMI-IOSCO PFMI Principle 8, UCC Article 12) to receive a finality tier 1–4, a singleness-of-money verdict, and a list of finality gaps. This tool gates ART-58 (cross-network settlement). Cash/settlement layer — distinct from Wave 8 Canton asset finality.
Educational classifier · not legal or settlement advice · Status: 2026-06-20 — verify EU SFD 98/26/EC, UCC Art.12, CPMI-IOSCO PFMI P.8 against current sources
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
⏱ Hard deadlines: ECB Pontes TARGET-link pilot end-Q3 2026 · DTCC Collateral AppChain full production Oct 2026 · BIS Agorá Phase 2 TBD
–
Finality tier
–
OpenChainGraph v0.4 artifact · execution_hash:
–
Solana DvP profile (additive note)
Trust model. The Solana Foundation DvP program is a bilateral two-escrow swap. A third-party settlement authority is the only signer that can settle or cancel, and it cannot redirect proceeds. Matching, pricing, netting, partial fills and any off-ledger leg are outside the program (program docs, retrieved 2026-10-16).
Escrow per leg. Each party funds its own escrow token account by a plain token transfer; the program-owned record is 458 bytes, so a funder should check owner, length, parties, mints, amounts, timestamps and destinations before funding (README State @df9919ed, SwapDvp struct @df9919ed).
Finalized is not legal finality. The doc treats an on-chain finalized commitment as the settlement point and states that legal finality is contractual. Legal finality stays with the governing contracts and the regimes classified on this page set.
Eligibility sits in the mint controls. The program has no allowlist or KYC. Token-2022 mint controls (PermanentDelegate, Pausable, DefaultAccountState, freeze authority, Token ACL) are accepted by the program and carry counterparty risk for the funder; they are the eligibility layer, not the program.
Educational note, not legal or settlement advice. Pinned to program source commit df9919ed; verify the deployed program and upgrade authority on chain before relying on it.
Ask your agent
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.
Run the AINumbers MCP tool `classify_settlement_asset_finality`. Task: Classify the settlement asset (CBM token / tokenized commercial bank deposit / regulated stablecoin / e-money token) against its legal-finality regime (EU SFD 98/26/EC / CPMI-IOSCO PFMI Principle 8 / UCC Article 12 control) -> finality tier 1-4 + singleness-of-money verdict.
Call it with arguments: {"policy_parameters":{}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Over MCP, the run happens on the AINumbers worker. No AINumbers server stores your inputs.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-59-settlement-asset-finality-classifier.html#p=v1.H4sIAAAAAAAA_wECAP3_e31Dv6ajAgAAAA