01 - The Settlement Engine

One sovereign L1. One kernel. Eight industries.

JIL Sovereign is not eight platforms. It is one settlement engine, configured eight ways. The kernel predates these verticals by 18+ months. Each new industry is a check pack on top of the same engine - not a new platform. That asymmetry is the moat.

~1.4M
Lines of original code (not a fork).
18+ mo
Kernel age, predates the verticals.
~1 week
Add-a-vertical effort on the kernel.
8 / 8
Industries live with public-data POCs.
75
Patent claims filed across attestation, evidence, and consensus.
273
Production services running on the reference mainnet.
In plain English

What the settlement engine does for you.

If you operate the payment rail, run the exchange, or settle the trades, this is what the JIL settlement engine actually changes about your day.

If you run a payment / settlement operation

Every transit gets a yes/no/review verdict in milliseconds with a signed evidence package attached. Disputes that used to take weeks of forensics now resolve in minutes against the on-chain record.

If you're a CISO

The settlement engine never holds funds, never holds keys, never sits in the trust path. Compromise of JIL is ledger-visible, not silent. The blast radius for the worst-case attack is bounded to known evidence packages, not your customer accounts.

If you're a treasury / finance lead

Per-event verification cost replaces percentage-of-volume risk. Instead of paying 35-90 bps to a fraud-screen vendor whose model you can't audit, you pay per cleared event with a deterministic price and an audit trail.

If you're a counterparty in a settlement dispute

The CREB(TM) bundle from the moment of settlement is the evidence. No 'show me your logs' / 'show me yours' standoff. Both sides verify the same cryptographically-anchored record.

02 - The thesis

We didn't build eight platforms. We built one and configured it eight ways.

Most "blockchain for compliance" startups fork Ethereum, repackage it, and try to bolt regulation on top. We didn't. We built a sovereign L1 from line one - our own consensus, our own ledger, our own validator admission, post-quantum signing in production today. ~1.4 million lines of original code. The kernel is 18+ months old.

That kernel produces a Court Ready Evidence Bundle (CREB) for every interaction. Same output format whether the input is a Medicare claim, a tokenized-Treasury settlement, an EB-5 source-of-funds document, an H-1B Labor Condition Application, or a $10K USDC transfer. The verticals are testimony to the modularity, not separate products.

Adding a vertical to JIL takes a week. Building JIL from scratch takes 18 months. That's the platform value.JIL platform thesis

03 - The leverage math

Build-the-kernel vs add-a-vertical.

The economics of the platform come from the asymmetry. The kernel is built once. Verticals ride on top. The cost to add the next vertical is a fraction of the cost to add the first one - because the first one paid for the kernel.

Build the kernel

Sovereign L1 + attestation network

18+ months

  • 14-of-20 BFT consensus across 13 jurisdictions
  • Post-quantum signing (Ed25519 + Dilithium-III hybrid) in production
  • HSM-backed validator keys, 7-day rotation
  • Sealed CREB output, FRE 902(14) self-authenticating
  • 175 check attestation catalog, MPC custody, BIP-44 multi-chain
  • Kafka + Redpanda settlement consumer, Postgres ledger router
  • Orchestrator + tier1-pipeline + ava agentic-AI trio
  • 75 patent claims (20-30 net-new in active drafting)
Add a vertical

Customer-profile-LOB-gated check pack

~1 week

  • ~3 check definitions (SQL aggregates over a vertical schema)
  • 1 public-data ingest script (federal CSV / API / blockchain RPC)
  • 1 template pack (3 narrative + 3 remediation, gated on lob)
  • 1 schema migration (vertical-specific tables + finding store)
  • 1 proof page on the public site, sample CREB
  • ~12-15 files total, 1 PR, deployable inside a session
Defensive moat asymmetry. A competitor entering any of these eight industries must first build a kernel that took us 18+ months. We add new industries in days. That asymmetry is the platform value, and it compounds with every additional vertical we ship.
04 - The kernel itself

What's underneath every CREB we seal.

The kernel is the part the verticals do not touch and never replace. It is the reason a Medicare-claim CREB and a tokenized-Treasury CREB are evidentiarily indistinguishable to a court, regulator, or auditor.

L1 substrate

Sovereign Compliance Network (SCN)

10 mainnet validators across 13 jurisdictions today. 14-of-20 BFT quorum. Every validator is a named legal entity with a documented jurisdiction, HSM-backed key custody, and post-quantum signatures. Anonymous validators are not permitted by design.

Cryptography

Post-quantum from line one

Ed25519 + Dilithium-III hybrid signing in production today, not on a roadmap. Kyber KEM in production. ML-DSA-65 implemented. Every key is generated and held inside an HSM and rotated on a 7-day cadence. A record sealed on JIL in 2026 will still be verifiable in 2050.

Output contract

CREB sealed receipt

Every check, every verdict, every finding ships as a Court Ready Evidence Bundle. FRE 902(14) self-authentication, 15+ year retention, content-addressable hash, full reproducibility manifest (code version, query plan, signal thresholds). Independently verifiable without JIL's cooperation.

Agentic layer

Ava: in-house agentic AI

Tier 1 verdict path is deterministic - SQL aggregates only, no stochastic LLM. Ava groups, narrates, and routes findings; never produces the underlying flag. Numeric-drift-guarded LLM refinement; 4-way AND-gate prevents accidental GPU spend on POC engagements. No external LLM API - JIL operates the model directly.

05 - Eight industries on the same kernel

Every vertical is a configuration, not a product.

Each card below points to the live public-data POC for that industry. Same kernel underneath all of them. Same CREB output. Same Ava agentic layer. Different check packs, different schemas, different ingest sources, different LOB gating.

Capital Markets

Capital Markets Settlement Integrity

$287.48B chronic FTD exposure. 14,156 chronic-offender CUSIPs surfaced from 339,992 SEC fails-to-deliver records. Top: SPY $13.0B, IWM $8.76B, LQD $7.46B.

See the POC ->

Federal Grants

Federal Grants Integrity

$2.96T obligations surveyed. 1,000 CY2024 federal awards / 321 recipients / 15 agencies. 66 concentration findings (39 critical). California DHCS 21.36% of HHS, Amtrak 39.33% of DOT.

See the POC ->

H-1B

H-1B Wage & Sponsor Integrity

337,367 real DOL LCAs. FY2024 Q3+Q4 LCA disclosures, 47,132 distinct sponsors. 459 findings: 134 wage-below-prevailing, 250 employer-concentration, 75 NAICS anomaly.

See the POC ->

P2P

P2P Settlement Integrity

12 OFAC SDN hits on day one. 1,000 USDC transfers from Etherscan + 46 sanctioned-address seed (Tornado Cash, Lazarus, Hydra, Garantex). 38 findings.

See the POC ->

EB-5

EB-5 Investor Visa Integrity

5 terminated RCs flagged. USCIS Data Hub processing-times + regional center list. 25 findings: 2 terminated regional centers with recent processing activity, I-526 denial-rate spike, 22 long-pending I-829 cohorts.

See the POC ->

Trade Finance

Trade Finance Integrity

206 sanctioned-partner anomalies. 924 trade flows / 527 corridors. Cross-referenced against 8 OFAC programs (IRN, PRK, CUB, SYR, RUS, BLR, VEN, MMR). 450 findings.

See the POC ->

P&C Insurance

P&C Insurance Integrity

60,762 real NHTSA crashes. FARS 2022 National CSV. 450 findings: VIN-repeat clusters, geographic crash clustering at 500m, make/model fatal-rate outliers.

See the POC ->

Workers' Comp

Workers' Compensation Integrity

260% spike in NAICS 56. 1,848 NAICS-state-year cohorts indexed. 207 findings: 124 NAICS outliers, 83 state-concentration patterns. CA holds 65% of NAICS 62 health-care DAFW.

See the POC ->

Aggregate proof. ~1,945 findings across 740,000+ real federal and on-chain records. All produced on day one of each engine. All sealed as CREB records. All replayable bit-identically by a third party with the same source files and the manifest. The economics are not hypothetical.
06 - Kernel maturity timeline

The 18 months of work that the verticals ride on.

The verticals are recent. The kernel is not. The work below is what makes a one-week vertical add-on possible.

Q1 2025

L1 consensus + ledger v1

Validator key ceremony. First named-entity validators admitted under documented criteria.

Q2 2025

Post-quantum signing

Ed25519 + Dilithium-III hybrid in production across the validator set.

Q3 2025

14-of-20 BFT mainnet quorum

Across 13 jurisdictions. Adaptive 70% target, halt below 10 healthy.

Q4 2025

CREB sealed-receipt format finalized

FRE 902(14) self-authentication, 15+ year retention, manifest format frozen.

Q1 2026

175 check attestation catalog

Production-ready. MPC custody multi-chain, BIP-44 derivation across 13 chains.

Q2 2026

Ava agentic-AI trio

Orchestrator + tier1-pipeline + ava. Agentic AI in-house, no external LLM API.

Apr 2026

First vertical engine

Capmarkets shipped + live POC on real SEC FTD data in 2 hours.

May 2026

All 8 verticals live

Public-data POC pages on the same kernel. Kernel unchanged.

07 - What this means for your industry

Pick the vertical you need today. Add the next one when you need it.

The customer engagement model follows the leverage: you commit to the vertical you actually need this quarter (one of the eight live), and adding a sibling vertical later is cheaper than your initial deployment because the kernel is already in place. Same applies to your industry's adjacent line of business - bringing it onto JIL is a check-pack add, not a re-platform.

Pricing reflects this. The four-SKU model (Tier 1 public-data baseline / Tier 2 commercial enrichment / Tier 3 court-ready CREB / Sovereign Stack in-tenant) prices the kernel once and the verticals on top.