Tokenized Deposit / Deposit-Token Compliance

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-B. Deposit-token classification, at-par redemption and holder-eligibility tests (ART-57) -> instrument/regime classification (510) -> Merkle integrity over the issuance/redemption set (cry-04). Distinguishes a redeemable bank-liability deposit token (JPMD/RLN) from a reserve-backed stablecoin or e-money token.

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

Chain Stages · 3 Steps

1 ROOT · D0 node

Deposit-Token Compliance Validator art-57-deposit-token-compliance-validator

token_class and classification_grade (H1) feed the classifier

MCP Call · validate_deposit_token_compliance

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

↓

2 D2 node

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

regime classification (H2) feeds the integrity verifier

MCP Call · classify_digital_asset_regulatory

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

↓

3 TERMINAL · D3 node

Merkle Batch Verifier cry-04-merkle-batch-verifier

Exports composite deposit-token artifact with execution_hash (H3), final stage

MCP Call · verify_merkle_batch

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

Question: The issuer calls this coin a deposit token. Does its liability structure actually read as a bank deposit? Run the AINumbers MCP tool `run_chain` with {"chain":"wholesale-settlement-deposit-token"} and read `art-57-deposit-token-compliance-validator.test_results.liability.result`. Re-run with `inputs` for `art-57-deposit-token-compliance-validator`, reusing the values that result echoed, with `liability_treatment` set to "on-balance-sheet-deposit". 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-deposit-token.html

Tokenized Deposit / Deposit-Token Compliance

Ask your agent