Infrastructure
Validator Infrastructure
20 validators across 13 jurisdictions with 14-of-20 BFT consensus. Hardware requirements, staking mechanics, jurisdiction distribution, and the complete 7-gate secure bootstrap sequence for mainnet nodes.
20 Validators
13 Jurisdictions
14/20 BFT Consensus
1.5s Block Time
Jurisdiction Distribution
13 regulatory zones across 6 continents. No single jurisdiction controls the network.
| Jurisdiction | Region | Validators | Regulatory Framework |
|---|---|---|---|
| Switzerland | Europe | 2 | FINMA (Primary HQ) |
| Abu Dhabi (ADGM) | Middle East | 2 | FSRA |
| Singapore | Asia-Pacific | 2 | MAS |
| United States | North America | 2 | FinCEN / State MTL |
| India | South Asia | 2 | RBI / SEBI |
| Brazil | South America | 2 | CVM / BCB |
| South Africa | Africa | 2 | FSCA |
| United Kingdom | Europe | 1 | FCA |
| Germany | Europe | 1 | BaFin / MiCA |
| Japan | Asia-Pacific | 1 | FSA / JFSA |
| Australia | Asia-Pacific | 1 | ASIC |
| Canada | North America | 1 | FINTRAC / OSC |
| Philippines | Southeast Asia | 1 | BSP |
Complete Validator Inventory
All 20 validators with infrastructure specifications and cloud vendor diversity.
| # | Validator ID | Jurisdiction | Cloud Vendor | Instance Type | vCPU | RAM | Storage |
|---|---|---|---|---|---|---|---|
| 1 | val-ch-zrh-01 | Switzerland | Hetzner | AX162 Dedicated | 64 | 256 GB | 1 TB NVMe |
| 2 | val-ch-zrh-02 | Switzerland | Azure | Standard_D64s_v5 | 64 | 256 GB | 1 TB NVMe |
| 3 | val-ae-auh-01 | Abu Dhabi | AWS | m6i.16xlarge | 64 | 256 GB | 1 TB NVMe |
| 4 | val-ae-auh-02 | Abu Dhabi | Hetzner | AX162 Dedicated | 64 | 256 GB | 1 TB NVMe |
| 5 | val-sg-sin-01 | Singapore | AWS | m6i.16xlarge | 64 | 256 GB | 1 TB NVMe |
| 6 | val-sg-sin-02 | Singapore | DigitalOcean | g-64vcpu-256gb | 64 | 256 GB | 1 TB NVMe |
| 7 | val-us-iad-01 | USA (Virginia) | AWS | m6i.16xlarge | 64 | 256 GB | 1 TB NVMe |
| 8 | val-us-sjc-02 | USA (California) | Hetzner | AX162 Dedicated | 64 | 256 GB | 1 TB NVMe |
| 9 | val-in-mum-01 | India (Mumbai) | AWS | m6i.16xlarge | 64 | 256 GB | 1 TB NVMe |
| 10 | val-in-del-02 | India (Delhi) | Hetzner | AX162 Dedicated | 64 | 256 GB | 1 TB NVMe |
| 11 | val-br-gru-01 | Brazil (Sao Paulo) | AWS | m6i.16xlarge | 64 | 256 GB | 1 TB NVMe |
| 12 | val-br-gru-02 | Brazil (Sao Paulo) | Azure | Standard_D64s_v5 | 64 | 256 GB | 1 TB NVMe |
| 13 | val-za-jnb-01 | South Africa (Johannesburg) | Hetzner | AX162 Dedicated | 64 | 256 GB | 1 TB NVMe |
| 14 | val-za-cpt-02 | South Africa (Cape Town) | Azure | Standard_D64s_v5 | 64 | 256 GB | 1 TB NVMe |
| 15 | val-gb-lon-01 | United Kingdom | Hetzner | AX162 Dedicated | 64 | 256 GB | 1 TB NVMe |
| 16 | val-de-fra-01 | Germany | Hetzner | AX162 Dedicated | 64 | 256 GB | 1 TB NVMe |
| 17 | val-jp-tyo-01 | Japan | AWS | m6i.16xlarge | 64 | 256 GB | 1 TB NVMe |
| 18 | val-au-syd-01 | Australia | Hetzner | AX162 Dedicated | 64 | 256 GB | 1 TB NVMe |
| 19 | val-ca-yul-01 | Canada | Vultr | Bare Metal 64-Core | 64 | 256 GB | 1 TB NVMe |
| 20 | val-ph-mnl-01 | Philippines | Linode | Dedicated 64-Core | 64 | 256 GB | 1 TB NVMe |
Vendor Diversity:
6 unique cloud providers (AWS, Azure, Hetzner, DigitalOcean, Vultr, Linode) ensure no single vendor outage can compromise the network.
Software Stack
Core components, data layer, and producer/consumer architecture.
Core Components
| Component | Technology | License | Purpose |
|---|---|---|---|
| jil-validator-node-v2 | Rust | Proprietary (JIL) | Core validator binary with CometBFT consensus |
| CometBFT | Go | Apache 2.0 | BFT consensus engine (Tendermint fork) |
| jil5600-core | Rust | Proprietary (JIL) | Ledger state machine and execution |
| mpc-cosigner | Rust | Proprietary (JIL) | MPC threshold signing service |
Why RedPanda + PostgreSQL
We selected RedPanda and PostgreSQL for several critical reasons:
- RedPanda: Kafka-compatible but with zero JVM dependency, lower latency, and simpler operations. No Zookeeper needed.
- PostgreSQL: Battle-tested, widely deployed, excellent tooling. No vendor lock-in or complex licensing.
- Operational Simplicity: Easier to operate across 20 distributed validators with diverse operators.
Data Layer
| Component | Technology | License |
|---|---|---|
| Event Streaming | RedPanda (Kafka-compatible) | BSL / Enterprise |
| Database | PostgreSQL 16 | PostgreSQL License (Free) |
| Event Producers | jil-ledger-producer (Rust) | Proprietary (JIL) |
| Event Consumers | kafka-consumer (Node.js) | Proprietary (JIL) |
| Monitoring | Prometheus + Grafana | Apache 2.0 |
Producer/Consumer Architecture
| Component | Role | Topics |
|---|---|---|
| ledger-service | Producer | jil.ledger.writes, jil.ledger.replies.* |
| wallet-api | Producer | jil.events, jil.state.sync.wallet_accounts |
| launchpad-api | Producer | jil.events |
| kafka-consumer | Consumer | All topics - PostgreSQL sync |
| explorer-api | Consumer | jil.ledger.* - Block indexing |
| analytics-pipeline | Consumer | All topics - BigQuery/Snowflake |
Consensus Parameters
CometBFT consensus with 14-of-20 signing threshold and 1.5-second block time.
| Parameter | Value | Description |
|---|---|---|
| Consensus Algorithm | CometBFT (Tendermint) | Byzantine fault-tolerant consensus |
| Total Validators | 20 | Fixed validator set |
| Signing Threshold | 14-of-20 (70%) | Required for block finality |
| Byzantine Tolerance | 6 validators | Max faulty validators tolerated |
| Block Time | 1.5 seconds | Target block interval |
| Max Block Size | 10 MB | Maximum transactions per block |
| Max Transactions | 10,000/block | Transaction throughput limit |
| Double Sign Slash | 5% | Stake slashed for equivocation |
| Downtime Slash | 1% | Stake slashed for extended downtime |
Geographic & Vendor Resilience
No single region, jurisdiction, or cloud vendor can block consensus or compromise the network.
Regional Distribution
| Region | Validators | % of Network | Can Block Consensus? |
|---|---|---|---|
| Europe (CH, UK, DE) | 4 | 20% | No (need 7+ to block) |
| Asia-Pacific (SG, JP, AU, PH, IN) | 7 | 35% | No (need 7+ to block) |
| Middle East (UAE) | 2 | 10% | No |
| North America (US, CA) | 3 | 15% | No |
| South America (BR) | 2 | 10% | No |
| Africa (ZA) | 2 | 10% | No |
Cloud Vendor Distribution
| Vendor | Validators | % of Network | Single Vendor Failure Impact |
|---|---|---|---|
| Hetzner | 8 | 40% | Network continues (12 remaining) |
| AWS Amazon Web Services | 6 | 30% | Network continues (14 remaining = threshold) |
| Azure Microsoft | 3 | 15% | Network continues (17 remaining) |
| Others (DO, Vultr, Linode) | 3 | 15% | Distributed across 3 vendors |
Key Resilience Properties:
- No single jurisdiction controls >2 validators (max 10%)
- No single continent controls >7 validators (max 35%)
- 8 different cloud vendors prevent single-vendor failure
- Network survives loss of any 6 validators (BFT guarantee)
- Combined US+EU shutdown leaves 12 validators operational
Network Architecture
20-validator network topology with RedPanda event streaming and PostgreSQL data layer.
Client Applications
Wallet / App / SDK
DEX / Router / Bridges
▼
RPC Gateway
Load Balancer + Rate Limiting
▼
Validator Consensus Network - 20 Nodes - CometBFT P2P
Europe - 4 validators
CH-1
CH-2
UK-1
DE-1
Asia-Pacific - 7 validators
SG-1
SG-2
JP-1
AU-1
IN-1
IN-2
PH-1
Middle East - 2 validators
UAE-1
UAE-2
North America - 3 validators
US-1
US-2
CA-1
South America - 2 validators
BR-1
BR-2
Africa - 2 validators
ZA-1
ZA-2
▼
14-of-20 BFT Consensus - JIL-5600 Ledger
RedPanda Event Streaming
PostgreSQL 16 Data Layer
For Validator Operators & Infrastructure Partners
Run a validator node across 13 jurisdictions with institutional-grade infrastructure.
JIL Sovereign operates 20 validators across 13 jurisdictions with 14-of-20 BFT consensus, 7 cloud vendors, and 190+ containerized services per node.