All Tools›Shared-Ledger Settlement
Permissioned-EVM Settlement

Shared-Ledger Settlement Hub

Browser-based verify-only tools plus ready-made workflows for permissioned-EVM shared-ledger settlement: mapping an ISO 20022 payment message to a contract call, linting a settlement contract against paired-or-revert and compliance-gate invariants, classifying an L2-to-L1 finality window, screening a transfer batch pre-commit, and attesting the off-chain orchestrator that decides commit or halt. Ties into the ISO 20022 messaging profile and the Besu/EVM-compatible settlement-rail concepts already covered on this site.

Tools · Workflows Verify-Only, Zero-Chain-Query Draft-Pinned Where Unpublished
Last Reviewed: 2026-07-13
Shared-Ledger Settlement Hub chain and tool matrixMatrix for Shared-Ledger Settlement Hub: columns are the tools this guide covers, each row is one chain, and a filled cell marks a chain that runs through the tool. Linea L2 Finality Window ClassifierLinea L2 Finality Windo… Settlement Orchestrator AttestationSettlement Orchestrator… ISO 20022-to-EVM Calldata MapperISO 20022-to-EVM… Besu Settlement Contract LinterBesu Settlement Contrac… On-Ledger Transfer Batch ScreenOn-Ledger Transfer Batc… Besu Settlement Contract… Besu Settlement Contract Conformance Gate run through Settlement Orchestrator Attestation Besu Settlement Contract Conformance Gate run through Besu Settlement Contract Linter Intraday Finality Attestation ReceiptIntraday Finality… Intraday Finality Attestation Receipt run through Linea L2 Finality Window Classifier Intraday Finality Attestation Receipt run through Settlement Orchestrator Attestation Shared-Ledger Transfer… Shared-Ledger Transfer Readiness Receipt run through Linea L2 Finality Window Classifier Shared-Ledger Transfer Readiness Receipt run through ISO 20022-to-EVM Calldata Mapper Shared-Ledger Transfer Readiness Receipt run through On-Ledger Transfer Batch Screen Chains using the tool 2 2 1 1 1
Chain and tool matrix for Shared-Ledger Settlement Hub: each column is a tool this guide covers, most used first, each row is one chain, and a brighter cell means more of that row's chains run through the tool. Hover a cell to list them.
What "shared ledger" means here

A permissioned, EVM-compatible settlement layer let banks move bank-issued tokenized deposits and settle interbank payment commitments using ISO 20022 messages, with cross-chain routing handled separately. None of these tools query that layer, submit a transaction to it, or move value. Every tool here operates on bytes you supply: an ISO 20022 message, a contract source or ABI, a finality-state snapshot, a transfer batch, or an orchestrator manifest. Where a field-binding table or contract shape has not been publicly published, the tool says so and marks its output draft-pinned rather than claiming conformance it cannot verify.

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Tools
ART-288
ISO 20022-to-EVM Calldata Mapper
Binds a pacs.008 or pacs.009 message to EVM contract-call arguments and reports what could not be mapped.
ART-289
Besu Settlement Contract Linter
Static lint of a settlement contract against atomic paired-or-revert transfer, native-token dependence, finality events, and compliance-gate coverage.
ART-290
Linea L2 Finality Window Classifier
Classifies a transfer's finality tier from supplied L2-batch and L1-finalization state and returns a safe-to-release verdict.
ART-291
On-Ledger Transfer Batch Screen
Pre-commit sanctions and purpose-code screen for a shared-ledger transfer batch, with per-transfer hits and coverage gaps.
ART-292
Settlement Orchestrator Attestation
Attests the off-chain orchestrator deciding commit or halt: manifest, decision policy, kernel bindings, and transport.
Workflows
Shared-Ledger Transfer Readiness Receipt
Mapping, batch screen, finality classification, and cash-leg finality check compose into one receipt. An unmapped field or a screening hit halts the workflow before commit.
Open workflow →
Tokenized Deposit Settlement Proof
Settlement fit, asset-finality classification, a zk compliance proof, and an anchor compose into a settled-compliantly proof without leaking counterparty data.
Open workflow →
Besu Settlement Contract Conformance Gate
Contract lint, orchestrator attestation, and receipt aggregation compose into a pre-deployment conformance record.
Open workflow →
Intraday Finality Attestation Receipt
Asset-finality classification, L2 finality-window classification, cash-leg finality check, and orchestrator attestation compose into a replayable "final at window Y" receipt, with an optional document-integrity anchor.
Open workflow →

For the Ethereum-standard tools behind these workflows, see the Ethereum hub.

Part of the web3 hub family: the full directory lives at web3-hub.html.