Pre-Clearance Settlement Attestation for Institutional Custodians

The problem we solve

Institutional custodians (Fireblocks, Anchorage, BitGo, Copper, and peers) face a structural problem on every outbound transfer: the receiving address may belong to a sanctioned entity, a mixed-pool service, a stolen-funds laundry, or a customer's own cold-storage wallet. Today the answer is policy-based screening at the orchestration layer, plus optional Chainalysis or TRM Labs annotations after the fact.

JIL Corridor adds a third option: a pre-clearance attestation from jurisdictionally independent signing nodes spread across 13+ jurisdictions. The attestation is cryptographically signed, hashes-only (no PII or transaction payload leaves the custodian), sub-second to obtain, and self-authenticating under FRE 902(13) if produced as evidence.

The flow

1. Custodian initiates outbound: a customer requests a transfer through the custodian's existing orchestration.
2. Custodian calls JIL Corridor /v1/preclearance/validate: POST with transit_id, source_addr, destination_addr, asset, amount_native, sender_id, receiver_id, custodian, exchange, and (Phase 1) transaction_preimage_hash + chain_id + egress_request_uuid for TOCTOU defense. Hashes only -- no PII, no claim payload.
3. JIL queries the independent signing nodes: jurisdictionally independent signing nodes across 13+ jurisdictions check the destination against sanctions, OFAC SDN, FATF travel-rule data, internal blocklists, and previously-attested risk scores.
4. Independent signing nodes sign the attestation: the signing nodes produce a structured PreClearance object: { tx_hash_intent, destination_score, jurisdiction_flags, courtchain_anchor_tx, valid_until }.
5. Custodian decides: proceed, hold for manual review, or block. JIL Corridor never holds funds, never sees the actual transaction; the custodian retains full control.
6. Attestation court-anchored on CourtChain: the signed pre-clearance record is anchored on the CourtChain evidence ledger for audit, dispute-resolution, and self-authenticating evidence purposes.

Economics

5 bps is the floor for pre-clearance attestation alone. Custodians who layer the CourtChain anchoring on top (for self-authenticating evidence) add a per-attestation $0.05 fee. JIL never custodies funds, never holds keys, never stores customer data at rest -- this pricing reflects the pure attestation service.

Defensibility

• Hybrid Snowflake + CourtChain. Risk scoring runs in Snowflake (compliant data plane); cryptographic attestation is anchored on the CourtChain evidence ledger (immutable record). Customers can audit both halves independently.
• 13+ jurisdictions. No single jurisdiction can subpoena the full set of signing nodes. Independent signing nodes live in US (Northeast, Southeast, West), Switzerland, UAE, Singapore, Brazil, Japan, UK, Germany, EU member states. Each jurisdiction has its own legal certification.
• FRE 902(13)/(14) self-authenticating. Each pre-clearance attestation is signed by named independent signing nodes with NIST-FIPS-certified cryptographic signatures. The attestation is admissible in federal court without a custodian of records testifying.
• Post-quantum ready. Hybrid Ed25519 + Dilithium-III signing on every attestation. Outputs verifiable under classical and post-quantum assumptions in parallel.
• No bridge, no custody, no transmission. JIL Corridor is structurally distinct from a settlement bridge. Funds never touch JIL. Keys never touch JIL. Data never touches JIL.

Custodian integration

JIL Corridor exposes a simple REST API and SDK bindings for Python, Go, TypeScript, and Rust. Request the full API contract specification via /connect.

# Python example -- maps to POST /v1/preclearance/validate
import jil_corridor, hashlib, uuid
client = jil_corridor.Client(api_key=os.environ['JIL_CORRIDOR_API_KEY'])
psa = client.validate(
    transit_id=str(uuid.uuid4()),
    source_addr='0x...',
    destination_addr='0x...',
    asset='USDC', amount_native='1000000.0', amount_usd=1_000_000,
    sender_id=customer_id, receiver_id=counterparty_id,
    custodian='your-custodian-slug', exchange='counterparty-exchange-slug',
    # Phase 1 TOCTOU defense -- bind to the exact tx bytes you will broadcast
    transaction_preimage_hash=hashlib.sha256(raw_tx_bytes).hexdigest(),
    chain_id='1', egress_request_uuid=str(uuid.uuid4()),
)
if psa.verdict == 'PASS':
    custodian.execute_transfer(...)
elif psa.verdict == 'FLAG':
    custodian.queue_manual_review(...)
elif psa.verdict == 'FAIL':
    custodian.reject_with_reason(psa.findings)
# Signed attestation always available for audit + evidence:
custodian.log_psa(psa.psa_id, psa.courtchain_anchor_tx, psa.node_signatures)
        

Pilot path

1. Discovery briefing -- 90 min. No data, no NDA. Walk through architecture; confirm jurisdictional fit.
2. Synthetic-traffic dry run -- 3 hours. JIL sends synthetic pre-clearance requests; you instrument latency, signature verification, integration shape.
3. Shadow run on real traffic -- 30 days. JIL Corridor scores 100% of your outbound; you do not change your decisioning. Outputs go to your audit log only.
4. Production rollout -- 90 days. Wire to your decisioning. SLA negotiated. Pricing locked.

The one-line summary

JIL Corridor is the only pillar that runs end-to-end on our tamper-evident evidence ledger. Custody, transmission, and key control stay with you. We sign the attestation.