Independent validation, security verification, and operational evidence
JIL publishes architecture documentation, security models, performance benchmarks, operational evidence, and governance boundaries. Every claim is mapped to artifacts. Every gap is disclosed. Select an assurance domain below to verify directly.
Architecture Assurance
Settlement model, trust assumptions, and system boundary documentation
Settlement Assurance Model
Complete transaction lifecycle from intent submission through deterministic finality. Four settlement stages, SCN validator responsibility model, and integrity guarantees.
- 4-stage transaction lifecycle
- Deterministic settlement - no probabilistic finality
- SCN Validator responsibility and attestation model
System Trust Assumptions
Every security system makes trust assumptions. JIL documents what the system trusts, what it verifies, what it cannot prevent, and where residual risk exists.
- 5 core trust domains documented
- Cryptographic assumptions and boundaries
- Known limitations transparently disclosed
Trust Boundary Diagram
Visual mapping of trust boundaries across 6 layers - from user-facing applications through settlement protocol to SCN validator infrastructure.
- 6 trust boundary layers visualized
- Data flow and authentication boundaries
- External system integration points
Data Architecture
JIL never custodies funds, never holds keys, never stores customer data at rest. Customer-owned AWS S3 + Snowflake share + 14-of-20 BFT L1 audit record across 13+ jurisdictions. Subpoena-resistant by design.
- Zero customer data at rest in JIL infrastructure
- Customer-owned AWS S3 with Apache Iceberg
- FRE 902(14) self-authentication via L1 anchor
Security Assurance
Threat models, security invariants, controls, and identity verification
Adversarial Threat Model
Structured threat analysis covering 4 adversary categories, 5 attack surfaces, consensus/wallet/bridge/infrastructure attack scenarios, and residual risk assessment.
- 4 adversary categories with capability analysis
- 5 attack surfaces with mitigations
- Residual risks transparently disclosed
Security Invariants
Properties that must always hold true regardless of system state. Consensus, transaction, wallet, bridge, and supply invariants with failure detection mechanisms.
- 7 invariant categories defined
- Automated violation detection
- Failure response procedures
Security Controls
Security architecture is published, not hidden. Evaluate the threat model, key management, authorization design, and data boundaries directly.
- Threat model summary
- MPC 2-of-3 key management
- Authorization lanes and data boundaries
Identity Verification
BID performs exhaustive identity verification before funds move. Five check categories, seven vendor integrations, fail-safe architecture.
- Phone, email, address, person, company checks
- 7 vendor integrations
- Fail-safe architecture
Performance Assurance
Benchmarks, test results, and institutional-grade evidence packs
Performance Benchmarks
Performance claims are backed by deterministic benchmarks, disclosed methodology, and live monitoring across the SCN validator fleet.
- Less than 800ms settlement finality
- 10,000+ settlements per second
- Live monitoring dashboard
Evidence Pack
Institutional-grade evidence pack. Every claim mapped to artifacts, every artifact linked to proof, every gap disclosed.
- 16 diligence sections
- Claims register with evidence mapping
- Risk register and evidence gaps
Operational Assurance
Resilience, infrastructure, and settlement protocol documentation
Operational Resilience
Resilience philosophy, SCN validator network fault tolerance, partition handling, infrastructure design, monitoring architecture, and disaster recovery procedures.
- Node failure tolerance model
- Network partition handling
- Incident response and disaster recovery
Platform Infrastructure
Every component documented. 250+ production services, 18 API specifications, 83 patent claims, 22 technical specs, 7 deployed mainnet contracts.
- 18 API specs linked
- 83 patent claims indexed
- 7 mainnet smart contracts
Proof of Settlement
Every settlement produces a cryptographically signed finality receipt binding policy, identity, authorization, and timing into a single verifiable artifact.
- Finality receipt with SCN validator attestation
- Verification demo - look up any settlement
- Receipt fields explained
Settlement Verification Services
12 real-time verification services power every settlement - OFAC sanctions screening, address validation, email/phone verification, PEP screening, fraud detection, corridor risk, velocity monitoring, and continuous re-screening.
- 12 verification services with live data sources
- OFAC SDN, FATF, OIG LEIE, GLEIF, SEC EDGAR
- 24-hour continuous re-screening cycle
Compliance Certification Report
512M+ certified test cases across 12 frameworks - SOC 2 Trust Service Criteria, NIST CSF 2.0, OWASP API Security, FIPS 140-3, smart contract formal verification, mainnet stress testing, and cross-jurisdiction compliance. 99.70% pass rate.
- SOC 2 readiness across all 5 TSC categories
- 512M+ tests, 99.70% pass, 12 frameworks
- 13 compliance zones across 13+ jurisdictions
Governance and Claims
Policy evaluation, scope boundaries, and institutional readiness
Policy Evaluation
Settlement policies are versioned, hashed, and enforced at the protocol layer. Every policy decision is recorded as evidence.
- Policy corridor configuration
- Enforcement evidence mapping
- Policy versioning and hashing
Scope and Boundaries
Clarity about what JIL does and does not do is itself a form of proof. Institutional counterparties deserve precise scope boundaries.
- What JIL does - 4 core capabilities
- What JIL does not do - clear exclusions
- Self-custody by design
Institutional Readiness
Everything an institutional counterparty needs to evaluate, integrate, and deploy JIL settlement infrastructure.
- Integration checklist
- POC plan (2 to 4 weeks)
- Compliance review packet
Why BFT-Style Proof of Stake
JIL uses a BFT-style Proof-of-Stake consensus with deterministic finality. SCN Validators stake JIL to participate in block production across 13 compliance jurisdictions. This is combined with a hybrid architecture - JIL-5600 unified ledger, ATE/ATCE compliance controls, and AMM V5 fair-market execution - to deliver institution-ready settlement.
Deterministic Finality
Settlement is final when SCN validators attest. No probabilistic confirmation windows or chain reorganization risk.
Lower Overhead
No mining competition, no gas auctions. Settlement costs are predictable and fixed per corridor.
Predictable Performance
Known SCN validator set enables consistent sub-second settlement under load without throughput degradation.
Reduced Energy
SCN Validator attestation consumes orders of magnitude less energy than proof-of-work mining.
Clearer Governance
Each SCN validator operates under a compliance agreement. Accountability is jurisdictional, not anonymous.
Security Review Roadmap
Mainnet launch is gated by completion of the independent protocol security audit. Institutional onboarding during pilot phase operates under sandbox conditions.
Ready to verify?
Start with a structured POC. Evaluate JIL settlement infrastructure on a single corridor with measurable success criteria.