Home/Docs/Pillars/03 - Proof-of-Compliance Settlement

JIL Proof-of-Compliance Settlement (PoCS)

Attestation-aware settlement rail for stablecoins and CBDCs. Compliance state travels atomically with value. Issuers pay bps per attested transfer. Year-5 $300M-$1B ARR potential.

NDA Confidential Version 2026-04-21
How the 4 pillars relate

Four pillars, one shared substrate, plus Sovereign Stack as a productized deployment

Every pillar captures value from the attestation work the platform produces anyway. This pillar is highlighted in gold. Sovereign Stack is the productized deployment of the whole stack - see /sovereign.

Shared Substrate
fleet-signer attestation engine L1 anchor MPC asset-intelligence YubiKey trust

JIL Proof-of-Compliance Settlement (PoCS) - Pillar 3

Document ID: POCS-PILLAR-001 Version: 1.0 Status: Planning. Ready for executive + issuer-partnership review. Owner: Jeff Mendonca (exec sponsor); Head of Issuer Partnerships (TBH); protocol engineering lead TBD. Shared substrate: see pillars README


1. The thesis

Today, stablecoin and CBDC settlement happens on vanilla payment rails. USDC moves on Ethereum, PYUSD on Solana, digital-euro pilot on ESCB networks. None of them carry compliance state with the settlement. Sanctions screening, Travel Rule, source-of-funds - all of it happens at the edge, after-the-fact, at each transacting institution. Every counterparty re-runs the same checks.

Visa and Mastercard solved this inside their walled gardens decades ago - compliance is coupled to settlement. You can't authorize a Visa transaction and skip the check; the network won't let you. Nobody has replicated this for crypto.

PoCS is the attestation-aware settlement rail. An asset moving through PoCS carries its FWEA verdict + sanctions attestation + source-of-funds proof bound cryptographically into the transfer envelope. The receiving institution trusts the attestation atomically with the value - no re-check needed, no edge-of-network risk, no race condition between "money lands" and "compliance clears."

The business: issuers (Circle, PayPal, Ripple, Paxos, central banks) route through PoCS to get compliance-for-free. JIL charges per attestation (basis points on flow, or flat-fee per transaction). Recurring revenue directly proportional to stablecoin/CBDC volume.


2. Market gap

Stablecoin + CBDC flow today

  • USDC annual transfer volume: $20T (2025, per Circle + on-chain analytics)
  • Tether USDT: ~$45T
  • PYUSD: rapidly scaling, ~$500B annualized
  • USDG, FDUSD, PyUSD, USDP: $2-5T combined
  • Digital euro (projected): $5-10T at full rollout (ECB estimate)
  • Digital Swiss franc, digital HKD, e-CNY: active pilots; projected $3T combined

Total addressable settlement flow: $75T+/year today, $100T+ within 3 years.

The compliance bottleneck

Every issuer today bears four structural costs that compound as volume grows:

  1. Per-counterparty re-check. Institution A sends to B; B re-runs the same sanctions check A already ran.
  2. Time-of-settlement mismatch. Check happens at T=0; settlement at T=5min. If sanctions list updated in that window, outcome is wrong.
  3. Regulatory fragmentation. Each jurisdiction wants its own reporting format. Issuer builds N adapters.
  4. Opaque compliance failures. When a receiving institution blocks a transfer because of their own check, sender has no visibility into why - support ticket hell.

PoCS solves all four:

  1. Attestation travels with value → receivers accept the sender's proof.
  2. Attestation is timestamped + quorum-signed at T=0 and stays valid until it expires (customizable, default 10 min).
  3. Output format is jurisdiction-parameterized - one envelope supports SAR, CTR, MiCA, DORA, FATF Travel Rule simultaneously.
  4. Every block is cryptographically explainable - the verdict record ships with the rejection.

3. Product structure

3.1 PoCS Rail - the base product

What it is: a settlement primitive added to JIL L1 (and, via light-client bridges, to Ethereum/Solana/Tron/Base). When an issuer's stablecoin contract settles through PoCS, the transfer envelope includes an attestation_hash field pointing to a sealed verdict record + a quorum-signed bundle the receiving address can verify atomically.

Technical mechanism: - Issuer's minting contract adds a PoCS hook that calls the JIL attestation engine before transferFrom completes - JIL produces attestation in <200ms (p95) via pre-provisioned attestation cache for known counterparties - Verdict + quorum sigs hashed into a 32-byte attestation_hash field on the transfer - Receiver verifies attestation against the trust bundle before releasing funds downstream

Customer: stablecoin + CBDC issuers.

Sold as: per-transaction basis-point fee, billed monthly against on-chain usage.

Pricing: 0.5-2 basis points per attested transfer. Tiered: lower bps for higher-volume issuers.

3.2 PoCS Flow Sampling - bridge to existing rails

What it is: for issuers not ready to commit their core contract to PoCS, a sampling mode where a % of transfers (1-100%) get attestation post-hoc and the attestation hash is stored in a sidecar ledger. Lets issuers A/B test PoCS-attested vs unattested flow compliance posture.

Customer: any issuer; entry point product.

Sold as: per-attestation flat fee.

Pricing: $0.10-$1.00 per attestation.

3.3 PoCS Routing Receipts - counterparty proof

What it is: a sealed receipt sent to both sender and receiver after every PoCS transfer. Same format as CourtChain Record. Cryptographically proves compliance state at settlement time; can be surfaced in dispute resolution, audit, or litigation.

Customer: institutions on both sides of a PoCS transfer.

Sold as: included in base PoCS fee; premium variant with extended retention/cold-storage.

Pricing: included; premium +$0.25/receipt.

3.4 PoCS Sovereign Bridge - CBDC interop

What it is: the PoCS attestation layer wrapped for central-bank deployment. Each participating CBDC operates its own attestation engine + trust bundle but the envelope format is interoperable, letting (e.g.) digital euro and digital Swiss franc settle atomically with attestation passthrough.

Customer: central banks.

Sold as: per-country license + multi-year contract.

Pricing: $5M-$25M per-country upfront + annual ops.


4. Target customers

Tier 1 - lighthouse customers (Year 1-2)

Issuer Annual flow Why them first
Circle (USDC) $20T regulatory-forward; paranoid about sanctions exposure post-2024 Treasury actions
Paxos (USDG, USDP, PYUSD) $3T combined NYDFS-regulated; compliance is their brand
Ripple (RLUSD) $100B and growing aggressive institutional positioning
PayPal (PYUSD) $500B exists precisely because they want compliance-first crypto

Tier 2 - Year 2-4

  • Tether (USDT) - hardest to sign; massive upside if they do
  • Binance (BUSD successor)
  • HSBC HDC pilot
  • BBVA digital asset custody

Tier 3 - Central banks (Year 3+)

  • ECB (digital euro)
  • MAS (Purpose-Bound Money / Project Guardian)
  • FINMA (wholesale CBDC)
  • BOE (digital pound)
  • MAS + HKMA (Project Ensemble)
  • HKMA (e-HKD)

5. Service architecture

PoCS is the first pillar that requires protocol-level work on JIL L1, not just a service layer. That's intentional - the attestation-value binding has to be atomic, and atomicity at the protocol layer means the value cannot move without the attestation being valid.

services/pocs/
├── src/
│   ├── index.ts                    # Express + Kafka bootstrap
│   ├── types.ts
│   │
│   ├── hooks/
│   │   ├── solidity/
│   │   │   ├── PoCS.sol            # reference issuer hook (transferFrom wrapper)
│   │   │   ├── PoCSBridge.sol      # cross-chain attestation bridge
│   │   │   └── PoCSRouter.sol      # fee + routing
│   │   ├── solana/
│   │   │   └── pocs_program.rs     # Solana equivalent (Anchor)
│   │   └── jil-l1/
│   │       └── pocs_precompile.rs  # native L1 precompile for issuers on JIL L1
│   │
│   ├── attestation-cache/          # pre-computed attestations for hot counterparties
│   │   ├── warm-cache.ts           # <200ms p95 target
│   │   ├── eviction-policy.ts
│   │   └── refresh.ts
│   │
│   ├── relay/                      # cross-chain attestation relay
│   │   ├── listener-eth.ts
│   │   ├── listener-sol.ts
│   │   ├── listener-base.ts
│   │   └── attestation-writer.ts   # posts attestation hashes back to source chain
│   │
│   ├── billing/
│   │   ├── bps-meter.ts            # basis-point per-transaction metering
│   │   ├── tier-lookup.ts          # volume-based tier resolution
│   │   └── issuer-invoicing.ts
│   │
│   └── routing-receipt/            # CourtChain-compatible per-transfer receipt
│       ├── composer.ts
│       └── delivery.ts
│
└── migrations/
    ├── 001_init.sql                # pocs.issuers, pocs.transfers, pocs.attestations
    └── 002_billing.sql             # pocs.tier_rates, pocs.monthly_invoices

L1 protocol changes (jil5600-core)

  • New transaction type: AttestedTransfer - includes attestation_hash, quorum_sigs[], expires_at
  • Sovereign Compliance Network (SCN) Validator rule: reject any AttestedTransfer where attestation signature fails quorum OR expires_at < block timestamp
  • Explorer surface: per-transfer attestation badge + link to /verify/:id

Integration points

Upstream What PoCS consumes
fraud-attestation-engine pre-cache verdicts for high-volume issuer counterparties
fleet-signer quorum signatures
asset-intelligence counterparty risk scoring for attestation
jil5600-core settlement primitive
courtchain routing receipts reuse same sealed-record format

6. Pricing model

Base fee: 0.5-2.0 basis points on settled value.

Example ARR math: - Circle routes 10% of USDC volume through PoCS: $2T × 1 bp = $200M ARR from one customer - PYUSD routes 25% through PoCS: $500B × 1.5 bp = $75M ARR - Paxos USDG routes 100% through PoCS: $1T × 1 bp = $100M ARR

These are big-money-per-basis-point dynamics. Even single-digit-percent adoption by one Tier 1 issuer is a $20M+ ARR product. Two signs us at $50M+ ARR territory.

Realistic path: - Year 1: one lighthouse + Flow Sampling at 5 issuers = $5-10M ARR - Year 2: 2 Tier 1 issuers + 3 Tier 2 = $30-50M ARR - Year 3: CBDC pilot + 3 Tier 1 = $75-150M ARR - Year 5: $300M-$1B ARR


7. Phased build

Phase 1 - Flow Sampling MVP (Months 0-4)

Ship: - services/pocs/ skeleton - Post-hoc attestation engine for sampled transfers (no on-chain hook required) - Basic issuer dashboard: "what % of your flow passes FWEA?" - First customer - target: Paxos (already compliance-forward, NYDFS relationship)

Team: 1 engineer + 0.5 partnership lead. Cost: ~$100K loaded. Milestone: Paxos running weekly reports off Flow Sampling.

Phase 2 - On-chain Solidity hook (Months 4-10)

Ship: - PoCS.sol reference implementation audited by OpenZeppelin or Trail of Bits - Attestation cache hitting <200ms p95 - Ethereum mainnet deployment of PoCS hook - Circle or PayPal pilot - 0.5% of flow routed through PoCS

Team: +1 protocol engineer, +1 security engineer, +audit budget. Cost: ~$800K loaded + $250K audit. Milestone: first atomic PoCS transfer on Ethereum mainnet.

Phase 3 - Multi-chain + base attestation (Months 10-18)

Ship: - Solana + Base deployments - Cross-chain attestation relay - JIL L1 native precompile - Paxos or Circle scales to 25%+ of flow - First PYUSD integration

Team: +1 protocol engineer per chain. Cost: ~$1.5M loaded. Milestone: $10M+ ARR run rate from PoCS alone.

Phase 4 - CBDC pilot (Months 18-30)

Ship: - Central-bank-tailored deployment (FINMA + MAS targets) - Sovereign Bridge feature for cross-CBDC atomicity - EU MiCA + DORA conformance documentation

Team: +1 CBDC partnerships lead + regulatory counsel. Cost: ~$2M loaded. Milestone: first CBDC MOU.


8. Risks

Risk Mitigation
Issuers resist adding hooks that can block transfers Start with Flow Sampling (post-hoc, no blocking). Prove value. Then upgrade to atomic mode for customers who want the stronger primitive
Attestation latency breaks settlement UX <200ms p95 via aggressive pre-caching. Attestations for repeat-counterparty pairs are pre-computed
Smart-contract bugs in PoCS.sol OpenZeppelin + Trail of Bits audits before mainnet. Formal verification of critical paths
Liability when PoCS attests and the attestation is wrong Clear terms - attestation is a snapshot of signal set at time T; downstream compliance liability stays with the issuer. We're the evidence provider, not the guarantor
Competitors build look-alikes Patent potential on attestation-bound settlement primitive (Claim 54 draft?). Post-quantum binding is our technical moat
Central banks want on-premises Sovereign Stack pillar handles this - PoCS ships as a module in that stack

9. Strategic value

PoCS is the highest-ARR-potential pillar. Basis points on trillions is how Visa and Mastercard became what they are.

But more importantly: PoCS is the insurance policy on every other pillar. Once stablecoin issuers route through PoCS, every downstream institution that receives their asset gets a JIL attestation for free. Network effect: the more issuers adopt PoCS, the more receivers need JIL, the more the compliance gravity pulls toward us.

Year 1 PoCS ARR is modest ($5-10M). Year 5 PoCS ARR is the majority of the company. This is the bet that takes JIL from compliance-services-company to settlement-infrastructure-company.

Pricing estimates · Pillar 3 · Proof-of-Compliance Settlement

Pricing & revenue profile

All figures below are illustrative estimates. Final pricing is scoped per engagement; contact sales for a firm quote.

Setup
$25K-$75K
One-time · 2-6 week deployment
API integration, policy-engine config, MSA + DPA, sandbox then cutover.
Per-event
35-90 bps
$1 floor per event · Volume-tiered
Priced by corridor, capability, volume. Custodian comparables: 50-200 bps.
Year-1 ARR (est.)
$5M-$10M
Modest launch · Scales with issuer adoption
First design-partner banks + 2-3 stablecoin issuers routed through PoCS.
Year-5 trajectory
Settlement-scale
Basis points on trillions
Network effect: every issuer adoption pulls downstream institutions into JIL by gravity. This is the bet that takes JIL from compliance-services to settlement-infrastructure.
See full pricing → Try the demo