Built for the Regulatory Era
The digital asset industry is entering a compliance-first phase. JIL Sovereign is the only policy and attestation infrastructure designed from day one with regulatory alignment as a core architectural principle - not a retrofit.
What this means for your General Counsel.
If you're general counsel, chief compliance officer, or regulatory affairs lead at a customer evaluating JIL, this is the regulatory-fit summary. The full page goes deep on the legal theory; this section is the short answer.
JIL is non-custodial by construction
JIL does not hold customer assets. Pre-Clearance attestations are signatures on the verdict, not the transaction. Asset Intelligence works from public + lawfully-obtained records. Sealed CREBs live in the vendor's SDV, not JIL's. Non-custodial posture keeps JIL outside MTL, MSB registration, and qualified-custodian scope in every US state we operate in.
Tier 1 (today) vs Tier 2 (Sealed Escrow)
Tier 1 = co-signing only, no custody. Operates as a compliance attestation provider + cryptographic signature service. Tier 2 (Managed Egress) = JIL takes constructive custody during the transit window and requires MTL / trust charter / qualified-custodian status. Tier 2 is a separately licensed product, not the default.
Court admissibility framework
CREB™ packages designed to satisfy FRE 902(14) for self-authenticating electronic records. Authenticated by cryptographic signature + L1 anchor + 14-of-20 BFT validator quorum. No JIL fact witness required at trial - a court-appointed expert can verify independently.
Customer compliance retains
JIL operates as a service provider TO the customer for OFAC, FinCEN BSA, sanctions, and AML obligations. The customer remains the regulated entity. JIL's attestations support the customer's compliance program; they do not replace it.
Per-jurisdiction posture
JIL maintains a state-by-state legal opinion file for the US, plus equivalent-regime opinions for EU (MiCA, DORA, GDPR), UK (FCA), Singapore (MAS), Switzerland (FINMA), Japan (JFSA). For any new jurisdiction, the open question is whether Tier 1's compliance-attestation framing maps cleanly - typically yes; we re-paper if not.
Vendor diligence package
Standard customer-side legal review fits a normal SaaS vendor template (no MTL clauses, no custodian indemnities, no special licensing). MSA + DPA template at /vendor-due-diligence. SOC 2 Type II in flight. NIST CSF 2.0 + CSC v8 control mapping pre-filled for security questionnaires.
Most digital asset platforms were built to move fast and break things. JIL was built to move fast and prove things - with an audit trail that regulators can verify independently.JIL Sovereign Regulatory Architecture Brief, 2026
Three shifts reshaping digital asset infrastructure.
Regulation Is No Longer Optional
MiCA enforcement begins June 2025. The EU Digital Operational Resilience Act (DORA) applies January 2025. FATF Travel Rule enforcement is expanding globally. Platforms without built-in compliance will lose market access.
Institutions Demand Audit Trails
Banks, custodians, and asset managers require deterministic evidence of compliance at settlement - not retroactive reporting. Settlement proof must be generated before value moves, not reconstructed after.
Cross-Border Complexity Is Growing
Multi-jurisdictional transactions face conflicting requirements across AML directives, sanctions regimes, and data localization rules. Corridor-level policy evaluation is becoming a competitive requirement.
Architectural compliance - not bolted-on compliance.
JIL does not add compliance after the fact. Every settlement passes through policy validation, beneficiary binding, and deterministic proof generation as part of the core protocol.
Markets in Crypto-Assets Regulation
JIL's architecture supports the MiCA requirements for operational resilience, reserve transparency, and customer asset segregation.
- Deterministic settlement receipts with policy hash
- On-chain reserve attestation capability
- Beneficiary identity binding before transfer
Digital Operational Resilience Act
JIL's 14-of-20 decentralized Sovereign Compliance Network (SCN) validator architecture across 13 jurisdictions provides operational resilience by design.
- Multi-jurisdiction SCN validator distribution
- Adaptive quorum with automatic fault tolerance
- Immutable audit trail with hash-chained evidence
FATF Travel Rule Compliance
Beneficiary identity data is cryptographically bound to every settlement intent as a protocol-level requirement, not an optional add-on.
- Originator and beneficiary data embedded at initiation
- Corridor-level jurisdiction enforcement
- Cross-border VASP compliance verification
Anti-Money Laundering & Sanctions
Real-time sanctions screening integrated at the verification layer. Transactions are flagged, held, or rejected according to institution-defined policy before execution - not flagged retroactively.
- OpenSanctions and OFAC list screening at settlement
- Risk scoring with automatic hold/reject thresholds
- BEC detection with domain age and email verification
Global regulatory landscape and JIL's response.
Active Legislation
- MiCA (EU)
Crypto-asset service providers, stablecoin issuers, exchanges. Full enforcement June 2025. · Enforcing - DORA (EU)
ICT risk management for financial entities. Applies January 2025. · Enforcing - Travel Rule (FATF)
Originator/beneficiary data for virtual asset transfers. Expanding enforcement globally. · Enforcing - PSR (UK)
Payment Systems Regulator APP fraud reimbursement. Mandatory October 2024. · Enforcing
Pending & Proposed
- FIT21 (US)
Financial Innovation and Technology Act. Defines SEC/CFTC digital asset jurisdiction. · Pending - GENIUS Act (US)
Federal payment stablecoin framework. Signed July 2025. Reserve requirements, issuer licensing, compliance standards. · Signed - VARA (UAE)
Virtual Assets Regulatory Authority. Dubai-specific licensing and compliance framework. · Enforcing - PSA (Singapore)
Payment Services Act amendments for digital payment tokens. MAS oversight. · Amending
How to talk about JIL in a regulatory context.
What JIL Is
Classification. JIL is policy and attestation infrastructure - a neutral verification layer that produces proof. JIL does not custody assets, execute trades, or replace regulated intermediaries.
Relationship to Regulators. JIL augments existing regulatory compliance by adding cryptographic audit trails, beneficiary binding, and policy evaluation at the verification layer - strengthening rather than circumventing oversight.
Value Proposition. Institutions use JIL to reduce fraud exposure, compress settlement time, embed compliance at execution, and generate deterministic finality receipts that are audit-ready from the moment of settlement.
What JIL Is Not
Not a Custodian. JIL never holds, controls, or has access to user assets. Users maintain custody through MPC 2-of-3 threshold signing where they hold their own shard.
Not an Exchange. JIL does not match orders, execute trades, or provide market-making services. The DEX is an on-chain order book with policy-enforced corridors - not a centralized trading venue.
Not a Bank Replacement. JIL strengthens the verification layer for banks and custodians. It sits between counterparties and provides verification, not banking services.
Three deployment paths. Three compliance postures.
Where the customer has standardized on a certified data platform, JIL inherits that posture by running inside it. Where JIL operates its own platform, JIL stands on its own controls. Both paths track NIST CSF 2.0 across Govern, Identify, Protect, Detect, Respond, and Recover.
Inherited from Snowflake
JIL Verdict Engine deployed as a Snowflake Native App via Snowpark Container Services. Customer data never leaves the customer's Snowflake account. JIL services run as containers in the customer's tenant.
- HITRUST r2
- SOC 2 Type II
- ISO 27001
- HIPAA + BAA
- FedRAMP MOD
- PCI DSS
Inherited from Databricks
JIL Verdict Engine deployed as a Databricks Brickbuilder App inside the customer's Databricks workspace. Delta Lake substrate, Unity Catalog governance, Photon query engine. Best fit for lakehouse-native, ML-heavy customers.
- HITRUST r2
- SOC 2 Type II
- ISO 27001
- HIPAA + BAA
- FedRAMP MOD
- PCI DSS
JIL standalone posture
Direct deployment on JIL-operated EKS infrastructure (KMS, IAM, GuardDuty). Customer VPC or peered. Best fit for federal customers requiring FedRAMP authorization paths and any institution requiring maximum operational control.
- SOC 2 Type 1 signed; Type 2 target Q4 2027
- HIPAA SRA + BAA signed
- HITRUST i1 signed; r2 24 months
- NIST CSF 2.0 mapped
- FRE 902(14) engineered
- FedRAMP MOD roadmap; GovRAMP Ready 3-4 months
All three paths share the same JIL services, the same Verdict Engine, the same Court Ready Evidence Bundle output, the same anchor to CourtChain™, and the same 14-of-20 SCN validator quorum. What differs is the substrate the customer chose. Customer data never leaves the customer's account regardless of deployment choice.
Compliance-first is the new competitive advantage.
Market Access
Platforms without MiCA compliance will lose access to EU markets. JIL's architecture enables partners to demonstrate compliance from day one.
Institutional Trust
Banks and custodians require deterministic audit trails. JIL produces cryptographic settlement proof that satisfies both internal risk teams and external regulators.
Defensible Position
84 patent claims covering beneficiary binding, policy evaluation, and deterministic finality. The regulatory-first approach is not just a feature - it is a protected competitive moat.
Explore regulatory topics in detail.
MiCA Compliance
EU Markets in Crypto-Assets regulation alignment and settlement proof.
DORA Resilience
Digital Operational Resilience Act and decentralized SCN validator architecture.
Travel Rule
FATF Recommendation 16 and protocol-level beneficiary identity binding.
Ready for the regulatory era?
JIL is operational and onboarding institutional partners. Schedule a consultation to see how compliance-first policy and attestation infrastructure works in practice.
Request a briefing
One mailbox for partner briefings, regulator desk, and integration coordination. Response within one business day.
Schedule a call
For confidential institutional inquiries. Routed to the partner desk for diligence and consultation scheduling.