Settlement

Capabilities

Settlement engine capabilities

All metrics from testnet operation on the Lagrange chain. 11 precompiles deployed at the consensus layer.

Multilateral Netting

Per-corridor multilateral netting with O(n) complexity. Configurable settlement windows with oracle-priced FX at window close. ISO 20022 CBPR+ native obligation recording.

Cross-Corridor Netting

Second layer of netting across corridors sharing the same currency. Additional savings on residual net positions after per-corridor netting. Effect scales with every new corridor per currency.

Bilateral Pre-Netting

Per-pair bilateral position tracking via recordBilateralObligation. Single transaction records sender debit + receiver credit + bilateral flow data. Foundation for SWIFT pacs.008 settlement instruction generation.

Residual Carry-Forward

CHIPS-model carry-forward. Sub-threshold net positions (<$100K default) carry to the next window (max 3), expanding the netting pool across windows for genuine compression improvement. Configurable per corridor.

Cryptographic Privacy

Pedersen commitments (BN254) for homomorphic netting on encrypted values. AES-256-SIV metadata encryption. Bulletproofs zero-knowledge range proofs (70ms proving, no trusted setup). Shamir's Secret Sharing for key distribution.

Post-Quantum Authentication

ML-DSA (FIPS 204) deployed via cloudflare/circl — not simulated. Modes 44/65/87 supported. Hybrid Dilithium+ECDSA available. Batch verification and on-chain key registry.

Multi-Tenancy

Per-corridor isolation on a shared chain

Access Control

6-level role hierarchy with per-corridor RBAC:

GOVERNANCE — master key, sees everything
ADMIN — corridor-level administration
OPERATOR — netting window management
PARTICIPANT — obligation recording
DELEGATE — scoped, time-limited access
OBSERVER — aggregate statistics only

Corridor Isolation

All six Settlement Computer products coexist on one chain with isolated corridor configurations.

Idempotent corridor creation
Per-corridor configuration limits
Per-corridor privacy levels (0/1/2)
Independent settlement windows
Jurisdiction-specific compliance rules

Data Sovereignty

Participant-sovereign data delegation

Participants control who sees their data. Delegation is granular, time-limited, revocable, and produces an immutable on-chain audit trail.

Delegation Model

grantViewAccess — granular scope, expiry, revocable
revokeViewAccess — instant, on-chain
Scopes: ALL, CORRIDOR, COUNTERPARTY, TIME_RANGE
On-chain audit trail (DelegateDataAccessed event)
canGenerateProofs flag for proof delegation

Designed For

Regulators and central bank supervisors
External auditors and compliance officers
Correspondent banking partners
Insurers and credit assessors
Legal and dispute resolution

Privacy Architecture

Tiered view key model

Five tiers of data access, from full visibility to aggregate-only. Each tier uses distinct cryptographic key material. Corridor privacy levels are configurable: Level 0 (plaintext), Level 1 (AES-SIV metadata), Level 2 (Pedersen + AES-SIV + range proofs).

Governance

Master key — full visibility

Admin

Corridor key — all obligations

Participant

Own obligations + net positions

Delegate

Scoped, time-limited, revocable

Observer

Aggregate statistics only