Settlement
Multilateral netting engine for cross-border institutional settlement. Corridor-level obligation compression with cross-corridor aggregation, bilateral pre-netting, and residual carry-forward.
Netting Process
Obligations are recorded throughout the settlement window, compressed through four layers of netting, priced at oracle-determined FX rates, and settled as consolidated net positions.
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 windows) using a CHIPS-model approach, expanding the netting pool across windows for additional compression.
Capabilities
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 carry to the next window (max 3), expanding the netting pool across windows. Configurable per corridor.
Cryptographic Privacy
Pedersen commitments (BN254) for homomorphic netting on encrypted values. AES-256-SIV metadata encryption. Bulletproofs 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. Modes 44/65/87 supported. Hybrid Dilithium+ECDSA available. Batch verification and on-chain key registry.
Chain Specifications
Multi-Tenancy
Per-corridor isolation on a shared chain. All Settlement Computer products coexist with independent configurations.
Access Control
6-level role hierarchy with per-corridor RBAC:
- GOVERNANCE — master key, full visibility
- ADMIN — corridor-level administration
- OPERATOR — netting window management
- PARTICIPANT — obligation recording
- DELEGATE — scoped, time-limited access
- OBSERVER — aggregate statistics only
Corridor Isolation
- Idempotent corridor creation
- Per-corridor configuration limits
- Per-corridor privacy levels (0/1/2)
- Independent settlement windows
- Jurisdiction-specific compliance rules
- Failure isolation between corridors
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, revocablerevokeViewAccess— instant, on-chain- Scopes: ALL, CORRIDOR, COUNTERPARTY, TIME_RANGE
- On-chain audit trail (DelegateDataAccessed event)
canGenerateProofsflag 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
Intellectual Property
Settlement-related patent coverage across 3 provisional applications:
Full API documentation under NDA
Comprehensive API reference, integration guides, and settlement instruction formats are available for qualified institutional participants.
Request Access