01Executive Summary
JIL Sovereign introduces the first fully on-chain protection coverage registry, where policy terms, coverage limits, premium schedules, and payout logic are stored immutably on the blockchain ledger. Unlike traditional crypto insurance products that rely on manual claims filing and off-chain adjudication, JIL's coverage system detects loss events automatically and executes payouts through a 14-of-20 validator attestation protocol.
Every Premium tier account receives $250,000 of automatic protection coverage funded by 100 basis points per year on monthly average assets under management. Loss events - including key compromise, bridge failure, custodial breach, and smart contract exploits - are detected by on-chain monitoring and verified by decentralized validator consensus before payout execution.
02Problem Statement
Crypto asset protection today is fundamentally broken. Traditional insurance carriers treat digital assets as exotic risk that commands prohibitive premiums and lengthy claims processes. Crypto-native insurance protocols require manual claims filing, governance votes, and weeks of adjudication. During the 2022 collapse cycle, affected users waited months or years for partial payouts - or received nothing at all.
2.1 The Protection Gap
2.2 Why Existing Solutions Fail
- Traditional Insurance (Lloyd's, Marsh): Policies require detailed underwriting, exclude most crypto-specific risks, and claims take 6 to 18 months to resolve. Coverage caps rarely exceed $50M industry-wide.
- Nexus Mutual: Requires manual claims filing with detailed evidence. Claims are adjudicated by token-weighted governance vote - creating perverse incentives where large token holders can block payouts to preserve the pool.
- InsurAce / Bridge Mutual: Application-layer products with no consensus-level integration. Premium pricing relies on historical data that does not exist for novel risk categories. Payouts require multi-step governance approval.
- Exchange Coverage (Coinbase, Binance): Only covers assets held on the exchange. Not applicable to self-custody or DeFi positions. Coverage amounts are opaque and not individually guaranteed.
03Technical Architecture
3.1 Policy Registry Contract
The on-chain policy registry stores all active coverage policies as structured records on the JIL L1 ledger. Each policy is linked to a specific account, defines coverage terms, and is updated automatically as premiums are collected and AUM changes.
| Field | Type | Description |
|---|---|---|
| policy_id | bytes32 | Unique policy identifier (hash of account + activation block) |
| account | address | Protected account address |
| tier | enum | Coverage tier (Standard: $50K, Premium: $250K+, Premium Plus: $1M) |
| coverage_limit_usd | uint256 | Maximum payout in USD equivalent |
| premium_bps | uint16 | Annual premium in basis points (100 = 1%) |
| last_premium_block | uint256 | Block at which last premium was collected |
| total_premiums_paid | uint256 | Cumulative premiums paid (for audit trail) |
| status | enum | ACTIVE, LAPSED, CLAIMED, EXHAUSTED |
| activated_at | uint256 | Block number of policy activation |
3.2 Premium Collection Mechanism
Premiums are collected automatically via on-chain micro-transactions at monthly intervals. The premium amount is calculated as (monthly_avg_aum * premium_bps) / 10000 / 12. If an account's balance is insufficient to cover the premium, the policy enters a 30-day grace period before lapsing. Premiums fund the coverage reserve pool, which is visible and auditable on-chain at all times.
3.3 Loss Detection Architecture
Key Compromise Detection
The MPC cosigner detects unauthorized signing attempts that bypass normal authentication. When a transaction is signed without proper biometric or passkey verification, the policy engine flags a potential key compromise event.
Bridge Failure Detection
Cross-chain settlement timeouts exceeding 24 hours trigger automatic proof-of-failure generation. The bridge relayer produces a signed attestation that the expected settlement did not complete within the protocol window.
Custodial Breach Detection
HSM compromise or jurisdiction seizure events are detected through the validator key verification protocol. If a validator's HSM fails its periodic challenge-response, the associated custody accounts are flagged.
Smart Contract Exploit Detection
Unexpected fund movements from verified contracts trigger the proof-verifier anomaly detection system. Transactions that deviate from the contract's expected behavior pattern generate automated alerts.
04Implementation
4.1 Validator Attestation Protocol
When a loss event is detected, the detecting service submits an attestation request to the validator network. Each validator independently evaluates the evidence and produces a signed attestation (approve or deny). The payout executes when 14 of 20 validators attest positively.
- Detection: Loss event detected by monitoring service (MPC cosigner, bridge relayer, proof-verifier).
- Evidence Package: Detecting service assembles cryptographic evidence (transaction hashes, timestamps, failure proofs).
- Broadcast: Evidence package broadcast to all 20 validators via the fleet gossip protocol.
- Independent Evaluation: Each validator independently verifies the evidence against the policy terms stored on-chain.
- Attestation: Validators submit signed attestations (approve/deny) to the attestation aggregator contract.
- Threshold Check: When 14 positive attestations are collected, the payout transaction is automatically constructed.
- Payout Execution: Coverage reserve pool transfers the covered amount to the affected account. Policy status updated to CLAIMED.
4.2 Coverage Tiers
| Tier | Coverage Limit | Premium (Annual) | Covered Events | Payout Speed |
|---|---|---|---|---|
| Standard | $50,000 | 50 bps on AUM | Key compromise, bridge failure | Within 1 hour |
| Premium | $250,000 | 100 bps on AUM | All 4 event types | Within 30 minutes |
| Premium Plus | $1,000,000 | 100 bps on AUM | All 4 event types + extended | Within 15 minutes |
| Institutional | Custom (up to $50M) | Negotiated | Full coverage + SLA | Within 15 minutes |
05Integration with JIL Ecosystem
5.1 MPC Cosigner Integration
The MPC cosigner service (port 8200) is the primary detection point for key compromise events. Every signing request passes through the cosigner's policy engine, which verifies authentication state, device attestation, and behavioral signals. Anomalous signing patterns trigger the loss detection pipeline.
5.2 Bridge Relayer Integration
The bridge relayer service (port 8150) monitors cross-chain settlement for timeout conditions. When a deposit confirmation or withdrawal execution exceeds the protocol-defined timeout, the relayer generates a cryptographic proof of failure and submits it to the attestation pipeline.
5.3 Settlement Layer Integration
The settlement consumer processes payout transactions through the same compliance pipeline as regular transactions. Payouts are tagged with a special COVERAGE_PAYOUT transaction type that bypasses velocity limits but still undergoes sanctions screening and zone compliance checks.
5.4 Proof Verifier Integration
The proof-verifier service (port 8250) generates ZK proofs for each payout event, creating an immutable, privacy-preserving record that the payout was legitimate without revealing the specifics of the loss event to public observers. These proofs are posted to the public proof bulletin board.
06Prior Art Differentiation
| Provider | Coverage Model | Claims Process | Adjudication | Payout Speed |
|---|---|---|---|---|
| Nexus Mutual | On-chain pool, manual claims | User files claim with evidence | Token-weighted governance vote | Days to weeks |
| InsurAce | Application-layer coverage | Manual claims portal | Multi-step governance | Weeks |
| Lloyd's / Marsh | Traditional insurance policy | Broker-mediated claims | Adjuster investigation | Months |
| Coinbase Coverage | Exchange-held assets only | Support ticket | Internal review | Weeks to months |
| JIL Sovereign | On-chain registry, automatic | No claims filing required | 14-of-20 validator attestation | Minutes |
07Implementation Roadmap
Policy Registry Foundation
Deploy on-chain policy registry contract. Implement coverage tier system (Standard, Premium, Premium Plus). Automatic premium collection via monthly micro-transactions. Coverage reserve pool with transparent on-chain balance. Basic loss detection for key compromise events.
Validator Attestation Protocol
14-of-20 validator attestation for payout authorization. Evidence package format and broadcast protocol. Independent evaluation logic per validator. Attestation aggregator contract. Automatic payout execution upon threshold.
Full Loss Detection Suite
Bridge failure detection via settlement timeout monitoring. Smart contract exploit detection via proof-verifier anomaly analysis. Custodial breach detection via HSM challenge-response failures. ZK proof generation for payout privacy.
Institutional Coverage and Reinsurance
Custom institutional coverage limits (up to $50M). Reinsurance pool integration with third-party underwriters. Actuarial modeling for dynamic premium adjustment. Cross-chain coverage for wrapped assets (jBTC, jETH, jUSDC). Regulatory filing for coverage product in key jurisdictions.