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
Governance

How JIL Sovereign Is Governed

A controlled governance model designed for institutional stability and regulatory compliance.

Overview

Controlled Governance Model

JIL operates under a controlled governance model. Unlike permissionless protocols where anyone can participate, JIL requires validators to meet jurisdictional, technical, and operational requirements before joining the network. This approach prioritizes institutional stability and regulatory compliance over open participation.

Governance Domains

Four domains of protocol governance.

Validator Admission

Jurisdiction requirements and regulatory standing verified before any node joins the network.

  • 7-gate startup sequence: handshake, config bundle, digest verification, key generation, auth token, service deployment, health confirmation
  • Jurisdiction verification and regulatory standing
  • Minimum hardware and network requirements
  • Cryptographic key generation and digest verification

Protocol Upgrades

Three-stage deployment pipeline with digest verification and rollback at every stage.

  • DevNet to TestNet to MainNet promotion pipeline
  • Container image digest verification at every stage
  • JILHQ fleet controller coordinates rollouts
  • Rollback capability at each stage

Policy Rule Updates

Compliance rule management across regulatory jurisdictions with zero-downtime deployment.

  • Compliance rule management for 10 regulatory jurisdictions
  • Asset-class policy configuration
  • Audit logging for all policy changes
  • Zero-downtime policy deployment

Emergency Procedures

Automated health monitoring and failover with anti-loop protection and golden snapshot recovery.

  • SentinelAI automated health monitoring and failover
  • Fleet cycling with anti-loop protection - max 3 cycles per 2 hours
  • Auto-recovery when fleet health drops below 30% for 5 consecutive cycles
  • Golden snapshot backup and restore
Validator Network

Network Structure

The JIL validator network is designed for geographic distribution, regulatory alignment, and operational independence. Each validator is independently operated with no shared infrastructure.

20
Target Active Nodes
20
Standby Capacity
14/20
BFT Quorum
13
Legal Jurisdictions
Independence

How Validator Independence Is Maintained

JIL validators are distributed across independent infrastructure providers in separate legal jurisdictions. No two validators share the same hosting provider, network segment, or legal entity. The 14-of-20 BFT quorum requirement means that even if 6 validators are compromised or offline, the network continues to operate correctly.

  • Separate Infrastructure - Each validator runs on an independent server with dedicated compute, storage, and network
  • Jurisdictional Diversity - Validators operate under different legal frameworks, preventing any single government from controlling the network
  • Independent Key Management - Each validator generates and holds its own cryptographic keys through a secure boot sequence
  • Quorum-Based Consensus - Settlement requires agreement from 14 of 20 validators, making collusion mathematically impractical
Transparency

Governance Transparency

All governance actions - validator admissions, protocol upgrades, policy changes, and emergency interventions - are logged immutably on the JIL ledger. External validation of settlement proofs, compliance attestations, and network health is available at /proof.

Protocol Governance

Learn More About JIL Governance

Controlled governance designed for institutional stability. Explore the infrastructure, contact the team, or review validation evidence.