Custodian-to-custodian asset transfer.
Asset transfers between custodians often rely on messaging-layer confirmations that lack binding verification. JIL enforces identity-bound instructions and receipt-based reconciliation at the verification layer.
Here's what we verify for you before the transfer leaves.
If you run integration, custody operations, or transaction policy at an institutional crypto custodian (Fireblocks, BitGo, Anchorage Digital, Coinbase Custody) - or you're a custodian customer routing transfers between counterparties - this is what JIL screens at the moment your policy engine asks "is this destination safe?". JIL never holds your asset. JIL produces a court-ready attestation in under 500ms that your policy engine acts on.
Destination wallet is freshly attributed to a sanctioned entity
The destination address was clean yesterday but was attributed to OFAC SDN, a DPRK incident report, or a community phishing list this morning. JIL's address-intelligence index pulls from 6 anonymous public sources (33,547 labeled wallets) and flags the match before your transfer signs. Sources are surfaced in the attestation so your team can audit the attribution chain.
Counterparty exchange address mismatch
You're sending to what you think is the customer's Coinbase Prime deposit address, but the destination doesn't match Coinbase's published deposit-address pattern, OR Coinbase has just rotated the customer's deposit address. JIL flags the mismatch before your TAP signs.
Mixer or DPRK-linked address
Tornado Cash exit, a DPRK Lazarus wallet documented in a Chainalysis or TRM incident report, or any of the 121 OFAC-sanctioned crypto addresses across 7 chains. JIL hard-fails the attestation; your policy engine receives the verdict + source provenance + recommended action.
Destination is a DEX router (informational, not a fail)
The destination is a known Uniswap, Curve, 1inch, or other DEX router contract. That's not necessarily a fraud signal - but it changes the policy decision your TAP needs to make. JIL labels the destination so your policy engine can apply the right rule (e.g., "DEX routing requires step-up approval").
First-time destination, no prior history
The customer is sending to a destination they've never sent to before. JIL runs the destination through the address-intelligence index, sanctions screen, KYC service, and risk-scoring stack, and returns a verdict + reasoning. Your policy engine can require an out-of-band confirmation if the verdict warrants it.
Sealed evidence per transit
Every transit your policy engine asks JIL about gets a Pre-Settlement Attestation (PSA) - signed by 14 of 20 validators across 13 jurisdictions, court-ready under FRE 902(14), reproducible from canonical bytes. Receiving exchange can independently verify the PSA via JIL's verify endpoint before crediting the deposit.
A signed PSA per transit. JIL never touches the asset.
For every transit your policy engine asks JIL about, you get back: a verdict (clear / hold / fail) at p50 350ms, a Pre-Settlement Attestation (PSA) signed by the 14-of-20 BFT validator quorum across 13 jurisdictions, source provenance for every finding (which list flagged it, which check returned what), and a 60-second validity window your policy engine acts within. The asset never enters the JIL system. JIL attests; your policy engine decides; your custody quorum signs the on-chain transaction. The receiving exchange can verify the PSA independently before crediting the deposit.
Plug into your TAP / policy engine.
1 · TAP webhook to JIL
Fireblocks Co-Signer SDK / BitGo policy module / Anchorage Workflow API integrations available. Your policy engine fires POST /v1/preclearance/validate before signing.
2 · PSA in 350ms
JIL runs address intelligence, KYC, sanctions, and risk in parallel. PSA + 14 signatures + source provenance returned synchronously. Your TAP applies its existing rules.
3 · Receiving exchange verifies
Exchange-side calls POST /v1/preclearance/verify with the PSA before crediting the deposit. Both sides have the same evidence.
25 bps per attestation. $1 USD-equivalent floor.
No minimum commit. Volume tiers for institutional custodians processing high transit counts. Compares favorably to Chainalysis Reactor at $300K-$2M/year - JIL is pay-per-use and the attestation is court-ready, not just analytical. For full pricing detail and per-custodian commercial terms, see the Fireblocks brief, BitGo brief, Anchorage Digital brief, or schedule a scoping call.
$190 trillion. Trillions parked for uncertainty.
$190+ trillion in annual global cross-border flows (BIS data). Trillions remain parked in nostro/vostro accounts to manage settlement latency.
Billions tied up in idle liquidity buffers.
Reconciliation cycles commonly T+1 to T+3.
Capital inefficiency reduces balance sheet velocity.
Fragmented messaging, custody, and compliance layers create settlement uncertainty.
Deterministic finality. Embedded policy validation.
How JIL transforms custodian-to-custodian transfers.
Reduces reconciliation lag.
Lowers idle liquidity buffers.
Enables clearer capital deployment timing.
Produces verifiable settlement receipts.
Traditional model versus JIL settlement model.
- Multi-hop correspondent chains.
- Liquidity parked for uncertainty.
- Log reconstruction for audit.
- Integrity layer validation.
- Predictable finality.
- Embedded receipt proof.
Close the exposure window. Bind the instruction.
- Instruction ambiguity between counterparties.
- Exposure window between instruction and settlement.
- Counterparty verification delays.
- Identity-bound instruction enforcement.
- Policy hash validation at settlement time.
- Receipt-based reconciliation.
Operational gate. Strategic positioning.
- Reduced exposure window.
- Reduced dispute probability.
- Faster inter-custodian confirmation.
- Enhanced institutional trust positioning.
- Reduced operational legal exposure.
Built to operate. Not demonstrated in a lab.
JIL Sovereign's reference mainnet runs in production today across ten SCN validator jurisdictions on three continents.
Settlement latency is liquidity tax. Pre-settlement attestation collapses the latency and recovers the buffer. JIL Sovereign - Capital markets thesis
Request a proof of concept.
See JIL policy and attestation infrastructure applied to your specific corridor.
Request a briefing
One mailbox for custodian briefings, treasury operations diligence, and corridor scoping. Response within one business day.
Schedule a call
For confidential institutional inquiries. Routed to the partner desk for capital markets corridor diligence.