Evidence infrastructure
CourtChain™ sealed evidence, not a public chain.
As-built for payment integrity: a customer-gated append-only S3 log. Hybrid Ed25519 + ML-DSA-65, RFC 3161 time, hash-only anchors. A permissioned JIL L1 is as-designed. Independent multi-operator BFT and a 14-of-20 live product claim are not current fact. CMS evidence is not anchored on that L1.
Infrastructure Brief · CourtChain
As-built S3 log. Hybrid PQ. FRE 902 posture.
Sealed Determination Proof Records and CREB/AREB/PIEB/RREB covers hash-anchor here: customer bucket, AES-256-GCM, Object Lock recommended. Hybrid Ed25519 + ML-DSA-65. Not a 14-of-20 public BFT ledger.
Payment integrity uses this log. The permissioned L1 is a separate as-designed substrate. Do not quote 14-of-20 or 13-jurisdiction live BFT as current fact.
Consensus
S3 log
Cryptography
Post-Quantum
L1 BFT
As designed
Status
Permissioned
Section 01 · The thesisWhy a purpose-built chain
Two facts. Do not mix them.
Payment-integrity CourtChain is a customer-gated S3 evidence log. That is as-built. A permissioned JIL L1 is as-designed for settlement/protocol work. Independent 14-of-20 BFT across 13 jurisdictions is not current fact. CMS CREB/AREB/PIEB/RREB packages hash-anchor on the S3 log, not on a public chain.
Post-quantum by default
Hybrid signing that survives the quantum transition
Every record carries both a classical Ed25519 signature and a lattice-based ML-DSA-65 (Dilithium) signature; key exchange uses ML-KEM-768 (Kyber). Both must verify. A harvest-now-decrypt-later adversary gains nothing, and the chain never has to fork to migrate.
Jurisdictionally distributed BFT
Permissioned JIL validators, as designed
As designed: permissioned, attributable validators operated by JIL. Independent multi-operator BFT and a 14-of-20 live product claim are not current fact. See the L1 consensus and custody field guide.
Purpose-built ledger
An attestation schema, not a smart-contract casino
CourtChain's transaction model is a court-evidence schema: subjects, findings, instruments, merkle-anchored bundles, and sovereign jurisdictional replication. Deterministic execution, public read access, and no general-purpose attack surface.
Evidentiary finality
Output that authenticates itself
A sealed record is a Court Ready Evidence Bundle: hash-anchored, signed, independently verifiable at a public endpoint, and admissible under Federal Rule of Evidence 902(14) without a foundation hearing. Deterministic finality in seconds, not probabilistic confirmations.
Section 02 · The stackFour layers, one chain
How CourtChain is built.
CourtChain L1
The sovereign Layer 1 ledger. Append-only attestation transactions, deterministic state, public read access, hybrid post-quantum signatures, and a purpose-built court-evidence schema.
Sovereign Compliance Network
As designed: permissioned JIL-operated validators. 14-of-20 / 13-jurisdiction live BFT is not current fact. See the L1 field guide.
Cross-chain bridge
A multi-signature bridge to Ethereum, 10+ EVM chains, and Solana. Lock-and-mint with timelocks and fraud proofs moves wrapped value (wBTC-JIL, wETH-JIL, wUSDC-JIL) on and off CourtChain.
JIL token
The ERC-20 settlement and metering asset (10B supply) that powers operations, with a multi-vault treasury and validator-incentive economics. See the wallet and bridge for the live crypto surface.
The institutional payment-integrity platform runs entirely on these four layers. If you are evaluating CourtChain as infrastructure, this page is your starting point. If you are evaluating JIL as a fraud, waste, and abuse detection platform, start at the Platform -- same engine, different lens.
Section 03 · The audienceWho builds on this
Built for the people who care how the chain works.
Protocol and infrastructure teams
Sovereign deployment
Run CourtChain in your own jurisdiction, on-prem or on certified regional cloud, and participate in the quorum with signing weight on every cross-border record that touches you.
Institutional investors
A defensible infrastructure moat
Patent portfolio over post-quantum settlement, bridging, and self-authenticating evidence. Filed claims are IP, not a live 14-of-20 network. PI evidence is the S3 log.
Integration and crypto-native builders
Bridge, token, and APIs
A documented cross-chain bridge, wrapper tokens, a public verifier endpoint, and a hybrid post-quantum signing library. Build against the chain or anchor your own evidence to it.
Section 04 · The depthDocs, patents, knowledge base
Everything under the hood, in the open.
CourtChain is documented end to end: the protocol specs, the cross-chain bridge, the developer SDK, the ledger and settlement APIs, the patent portfolio, and a deep technical knowledge base. If you want to understand exactly how the chain works before you build on it or invest in it, start here.
Protocol and APIs
Technical specifications
The CourtChain protocol, the ledger and settlement APIs, the developer SDK, and the integration bridges, specified in detail.
CourtChain protocol spec
CourtChain field guide (S3 evidence log)
Ledger and settlement APIs
All API and bridge docs →
Bridge, patents and research
The cross-chain bridge and the moat
The multi-signature bridge thesis, the post-quantum and validator-bridge patent claims, and the whitepapers behind the architecture.
L1 consensus and custody (as-built vs design)
The 177-claim patent portfolio
Whitepapers →
Knowledge base
The CourtChain technical library
A deep, searchable library across settlement, cryptography, bridges, the validator network, zero-knowledge proofs, tokenized securities, and more, for the engineers and analysts who go deep.
Browse the knowledge base →
The wallet, bridge and JIL token