Platform

Overview

How It Works

Beneficiary Identity

Policy Corridors

Deterministic Finality

Architecture

Security Model

Governance

Integration

Solutions

Corridors Overview

Institutional Overview

Pricing

All Scenarios

Humanitarian Impact Fund

Assurance

Technical Assurance

Verify Receipt

Receipt Example

Developers

Documentation

APIs & Bridges

Architecture Docs

Glossary

BID API

Company

About

Team

Partners

Roadmap

Investors

Contact

Blog

All Documentation

Schedule Consultation
Architecture Assurance

Settlement Assurance Model

Complete transaction lifecycle from intent submission through deterministic finality. Every settlement passes through four defined stages, each with specific validation gates and integrity checks.

← All Assurance

Transaction Lifecycle

Every JIL settlement follows a deterministic 4-stage lifecycle. Each stage has defined entry criteria, validation gates, and exit conditions. No stage can be skipped or reordered.

Stage 1
Intent Submission
Client submits settlement intent with beneficiary, amount, and policy corridor
Stage 2
Compliance Validation
BID verification, policy enforcement, jurisdiction fencing, AML/sanctions check
Stage 3
Consensus Attestation
14-of-20 validators attest to settlement validity across compliance zones
Stage 4
Finality and Receipt
Ledger commit, cryptographic receipt generation, audit trail persistence

Settlement Finality

JIL provides deterministic finality - not probabilistic. When a settlement reaches Stage 4, it is final. There is no confirmation window, no chain reorganization risk, and no rollback possibility.

What Deterministic Finality Means

  • Settlement is complete when 14-of-20 validators attest - there is no "waiting for confirmations"
  • Once finalized, the settlement cannot be reversed, reorganized, or invalidated
  • Finality is cryptographically provable via the settlement receipt
  • Receipt contains validator signatures, timestamp, policy hash, and beneficiary binding

Comparison to Probabilistic Systems

PropertyJIL (Deterministic)Bitcoin/Ethereum (Probabilistic)
FinalityImmediate on attestation6+ confirmations (Bitcoin), 12+ blocks (Ethereum)
Reorganization riskNonePossible until sufficient depth
Time to finalitySub-second60+ minutes (Bitcoin), 6+ minutes (Ethereum)
ReceiptCryptographic, validator-signedBlock inclusion (no institutional receipt)

Deterministic Settlement Properties

The settlement protocol enforces several properties that distinguish it from general-purpose blockchains.

  • Order independence: Settlement outcome is the same regardless of transaction ordering within a block
  • Idempotency: Resubmitting the same settlement intent produces the same result - no double-settlement risk
  • Atomicity: A settlement either completes fully or not at all - no partial states
  • Auditability: Every stage transition is logged with timestamps, validator IDs, and policy evaluations
  • Non-repudiation: The finality receipt provides cryptographic proof that both parties authorized the settlement

Validator Responsibility Model

Each validator in the 14-of-20 consensus operates under defined responsibilities. Validators are not anonymous miners - they are identified nodes operating under compliance agreements.

ResponsibilityDescriptionEnforcement
Settlement attestationValidate and sign settlement proposalsConsensus protocol
Policy enforcementVerify corridor policies match settlement parametersPolicy engine
Uptime commitmentMaintain availability for consensus participationSentinelAI monitoring
Key securityProtect validator signing keys from compromiseHSM + AES-256-GCM
Jurisdictional complianceOperate within assigned compliance zone7-gate bootstrap

Integrity Guarantees

The settlement assurance model provides the following integrity guarantees to institutional counterparties.

  • No unauthorized settlement: Requires MPC 2-of-3 authorization from the user - the platform cannot settle without user participation
  • No policy bypass: Every settlement is validated against the active policy corridor before consensus
  • No silent failure: Failed settlements produce explicit error receipts with failure reasons
  • No data leakage: Settlement data is partitioned by jurisdiction - validators only process data for their assigned zones
  • No retroactive modification: Finalized settlements are immutable - the ledger does not support state rollback

Monitoring and Observability

Settlement assurance is continuously monitored across the validator fleet.

  • SentinelAI Fleet Inspector: Automated health monitoring with threat scoring and auto-recovery
  • Real-time telemetry: Settlement latency, throughput, and error rates tracked per validator
  • Consensus health: Quorum participation monitored - adaptive threshold adjusts if validators go offline
  • Heartbeat monitoring: Every validator sends periodic heartbeats - missed heartbeats trigger investigation

Ready to verify?

Start with a structured POC. Evaluate JIL settlement infrastructure on a single corridor.

Request a POC All Assurance