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
Zero-Knowledge Compliance - v95

ZK Compliance Proof Illustration

How zero-knowledge proofs allow JIL Sovereign to prove regulatory compliance without revealing any private data to the network or third parties.

What Is Checked

Compliance rules evaluated by the ZK circuit

KYC Verification Status
Confirms identity verification tier without revealing identity details
Sanctions Screening Result
Verifies sender and receiver are not on any sanctions list
Transaction Amount Limits
Checks amount is within jurisdiction and tier limits
Jurisdiction-Specific Rules
Enforces local regulations per compliance zone (BaFin, MAS, FINMA, etc.)
Velocity Checks
Evaluates transaction frequency limits over rolling time windows
Source of Funds Attestation
Confirms fund origin has been attested without disclosing source details
Beneficiary Identity Binding
Cryptographic hash confirms recipient identity matches the intended beneficiary (BEC prevention)
Recipient Sanctions Screening
Confirms receiving party is not on OFAC SDN, EU, or UN sanctions lists
Recipient Country Verification
Validates beneficiary jurisdiction is not restricted or embargoed

What Stays Private

Data never leaves the local node or ZK circuit

Account Balances
Actual holdings and portfolio values remain encrypted
Counterparty Identity
Who is on the other side of the transaction is never disclosed
Trade Details and Positions
Order sizes, prices, and open positions are hidden from validators
Personal Data
Name, address, date of birth, and identity documents stay off-chain
Internal Compliance Scores
Risk scores, trust levels, and entity ratings are not exposed
Historical Transaction Patterns
Past activity, behavioral patterns, and flow analysis remain private

What Is Produced

Verifiable output attached to the settlement record

ZK Proof Reference Hash
Cryptographic hash uniquely identifying this proof
0x7a3f9b2c...e41d8f06a3b7c5d9
Compliance Attestation
Binary result: transaction passed all required checks
PASS
Jurisdiction Zone Approval
Confirms applicable compliance zone was satisfied
CH_FINMA - APPROVED
Timestamp of Verification
Exact time the proof was generated and sealed
2026-02-21T14:32:07.491Z
Validator Consensus Count
Number of validators that attested to the proof
14 / 20 validators (70% BFT threshold)
Proof Expiry Window
Time window during which this proof remains valid
24 hours from generation

How It Works

1

Transaction Submitted

A user or institution submits a transaction to the JIL network for settlement.

2

Compliance Engine Evaluates Rules

The compliance engine runs KYC, AML, sanctions, velocity, and jurisdiction-specific checks against the transaction data.

3

ZK Circuit Generates Proof

A zero-knowledge circuit produces a cryptographic proof that all rules passed - without revealing any of the underlying data.

4

Proof Attached to Settlement

The ZK proof is attached to the settlement record on-chain. Regulators can verify compliance. No private data is exposed.

Privacy-Preserving Compliance

Zero-knowledge proofs allow JIL to prove compliance without revealing private data. Regulators can verify that rules were followed. Neither the network nor any third party can see what was checked.