Settlement Process

Obligations are recorded throughout the settlement window, compressed through four layers of netting (bilateral, per-corridor multilateral, cross-corridor, and residual carry-forward), priced at oracle-determined FX rates, and settled as consolidated net positions.

Netting Flow

Record

Via API / ISO 20022

Bilateral

Per-pair pre-netting

Multilateral

Per-corridor + cross-corridor

Price

AFXO oracle

Settle

Net positions only

Sub-threshold net positions (<$100K default) carry forward to the next window (max 3) using a CHIPS-model approach, expanding the netting pool across windows for additional compression.

Chain Architecture

The Settlement Computer runs on the Lagrange chain — a dedicated Avalanche L1 with permissioned validators. All settlement logic is implemented as consensus-level native precompiles, not smart contracts. This provides deterministic gas costs, guaranteed execution, and prevents front-running.

Chain
Lagrange L1 (Avalanche, Subnet-EVM v0.7.1)
Finality
Sub-second (<1s)
Peak TPS
1,601 (301 obligation TPS)
Gas Token
FSC (utility only, zero market value)
Precompiles
11 consensus-level native precompiles
Codebase
10,800+ lines Go, Solidity interfaces
Corridors
11 live on testnet
Compression
91.2% average ($12.13B gross processed)

Native Precompiles

All settlement logic runs at the consensus layer as native Go precompiles — not EVM smart contracts. This provides deterministic gas costs, prevents front-running, and enables cryptographic operations that would be prohibitively expensive in the EVM.

Cryptographic Privacy

The Settlement Computer implements a hybrid privacy architecture. Amounts are protected by Pedersen commitments (BN254) enabling homomorphic netting on encrypted values. Metadata is encrypted with AES-256-SIV. Key distribution uses Shamir's Secret Sharing.

Amount Privacy
Pedersen commitments (BN254) — homomorphic, netting-compatible
Metadata Privacy
AES-256-SIV — deterministic authenticated encryption
Range Proofs
Bulletproofs — 70ms proving, no trusted setup
Key Distribution
Shamir's Secret Sharing (3/4 threshold active)
Key Derivation
HKDF for per-window and per-corridor key material
Corridor Privacy Levels
Level 0 (plaintext), Level 1 (AES-SIV), Level 2 (Pedersen + AES-SIV + proofs)

Tiered view key model with 5 access levels: Governance (master), Admin (corridor), Participant (own data), Delegate (scoped, time-limited, revocable), Observer (aggregates only). Participant-sovereign delegation — participants control who sees their data via grantViewAccess / revokeViewAccess with full on-chain audit trail.

Post-Quantum Authentication

ML-DSA (FIPS 204) deployed via cloudflare/circl — real post-quantum signatures, not simulated. This provides harvest-now-decrypt-later protection for all settlement transactions.

Algorithm
ML-DSA (CRYSTALS-Dilithium, FIPS 204)
Modes
ML-DSA-44, ML-DSA-65, ML-DSA-87
Implementation
cloudflare/circl — production library
Hybrid Mode
Dilithium + ECDSA available for transition

Multi-Tenancy

All six Settlement Computer products coexist on a single chain with per-corridor isolation. Each corridor has independent configuration, settlement windows, privacy levels, and compliance rules.

Access Control
6-level RBAC: Governance, Admin, Operator, Participant, Delegate, Observer
Corridor Isolation
Idempotent creation, independent config, failure isolation
Products
Settlement, PayNet, RiskNet, Trade, Grid, Nexus
Jurisdiction
Per-corridor compliance rules and privacy levels

ISO 20022 CBPR+

Born-native ISO 20022 CBPR+ — not a translation layer. Level 1 (schema conformance) and Level 2 (SWIFT usage guidelines) validation passed across all 5 message types. PayNet provides AI-powered translation (Haiku 4.5 / Sonnet) for non-ISO inputs.

pain.001
Customer Credit Transfer Initiation
pacs.008
FI to FI Customer Credit Transfer
pacs.002
Payment Status Report
camt.054
Bank to Customer Debit/Credit Notification
camt.053
Bank to Customer Statement
FX Oracle
AFXO — deterministic global FX rate feeds

Design Principles

Intellectual Property

5 U.S. patent applications pending (~287 claims) covering the Settlement Computer, agentic clearing, cryptographic privacy, and post-quantum authentication.

PROV-001 — 63/943,488
Settlement Determination Architecture
PROV-002 — 64/013,030
RiskNet, PayNet, Cross-Product Architecture
PROV-003 — 64/013,031
Trade + Grid — Maturity-Aware Temporal Netting
PROV-004 — 64/013,645
Agentic Clearing — 65 claims, 7 invention families
PROV-005 — 64/032,665
Privacy + PQ Cryptography — 49 claims, 5 invention families
Status
All implemented and live on testnet. Non-provisional conversions in progress.

Full documentation under NDA

Detailed API specifications, integration guides, precompile documentation, and compliance materials are available for qualified institutional participants.

Request Briefing