Settlement Process

Settlement 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 windows) using a CHIPS-model approach, expanding the netting pool across windows for additional compression.

Chain Specifications

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
95% combined ($12.13B gross processed)

Native Precompiles

All settlement operations execute as native Go precompiles at the consensus layer — not as EVM smart contracts. This guarantees deterministic gas costs, prevents MEV extraction, and enables cryptographic operations that are infeasible within the EVM execution environment.

  • 0x0300 Netting Engine — multilateral netting with O(n) complexity
  • 0x0301 Oracle — deterministic FX rate feeds from AFXO
  • 0x0302 Corridor Manager — multi-tenant corridor lifecycle
  • 0x0303 Access Control — 6-level RBAC per corridor
  • 0x0304 Settlement Claims — non-transferable institutional tokens
  • 0x0305 Compliance — audit trail with sanctions screening hooks
  • 0x0306 Cross-Corridor — netting across corridors sharing currencies
  • 0x0307 Bilateral — per-pair pre-netting with SWIFT pacs.008 output
  • 0x0308 Privacy — Pedersen commitments, AES-256-SIV, SSS
  • 0x0309 ML-DSA — FIPS 204 post-quantum authentication
  • 0x030A Delegation Registry — participant-sovereign view key grants

Design Principles

  • Non-Custodial

    The Settlement Computer coordinates settlement instructions but never holds funds. All regulated activities remain with licensed institutional partners.

  • Corridor Isolation

    Each corridor operates independently with its own settlement windows, participant lists, privacy levels, and compliance rules. Failures in one corridor do not propagate.

  • Deterministic Execution

    FX rates are determined at window close via AFXO oracle feeds, not executed in market. Oracle prices are locked, ensuring no slippage or front-running.

  • Consensus-Level Settlement Logic

    All settlement operations run as native Go precompiles, not EVM smart contracts. This guarantees deterministic gas costs, prevents MEV extraction, and enables cryptographic operations infeasible in the EVM.

  • Technology Service Provider

    FiatRails is a non-custodial coordination protocol — not a bank, PSP, e-money issuer, or remittance company. We never hold fiat, never custody user funds, and never execute settlement.

Intellectual Property

5 US provisional patent applications covering approximately 287 claims across the Settlement Computer stack. Patent coverage spans netting architecture, cross-corridor coordination, agentic clearing, multi-tenant corridor management, and cryptographic privacy.

PROV-001 · 63/943,488
Settlement Determination Architecture
PROV-002 · 64/013,030
Cross-corridor netting, bilateral tracking, risk intelligence
PROV-003 · 64/013,034
Agentic AI clearing (Nexus)
PROV-004 · 64/032,660
Multi-tenant corridor management
PROV-005 · 64/032,665
Privacy + PQ Crypto (49 claims)

Comprehensive documentation under NDA

Full architecture specifications, precompile interfaces, and integration guides are available for qualified institutional participants.

Request Access