eBL Exclusive-Control Evidence Chain

Check a supplied electronic bill of lading's control-transfer event log against UNCITRAL MLETR Art. 10/11 singularity and exclusive-control elements, then bind the same event log into a hash-chained possession-receipt evidence pack with a Merkle root a holder can present to a bank or court. A jurisdiction-adoption lookup runs on its own branch to answer whether the eBL is legally effective end-to-end for the corridor in question. Zero network, no PII, not a title registry or legal opinion.

OpenChainGraph · 2 Steps + 1 Branch compliance mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII

Chain Stages · 2 Steps

1 ROOT node

ETR Singularity & Exclusive-Control Evidence Checker art-352-etr-control-evidence-checker

Control-transfer event log and verdict feed the possession-chain receipt builder

MCP Call · check_etr_control_evidence

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

↓

2 TERMINAL node

ETR Possession-Chain Receipt Builder art-353-etr-possession-chain-builder

Hash-chained possession receipts and Merkle root -- final stage of the main chain (jurisdiction branch runs independently over the same corridor)

MCP Call · build_etr_possession_chain

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

Branch · Jurisdiction

Runs independently over the same corridor: MLETR Jurisdiction-Adoption Lookup art-354-mletr-jurisdiction-adoption-lookup answers whether the corridor's jurisdictions have adopted MLETR functional-equivalence and singularity/exclusive-control requirements, closing the loop between the technical evidence above and legal effect end-to-end.