GateCoverage — the coverage matrix

What it does

GateCoverage is the part of every screening that says what was actually checked. Sanctions matching runs against OFAC, UK OFSI and the EU consolidated list, re-synced at least every 6 hours and content-hashed so every decision records exactly which snapshot it saw. Stablecoin issuer freezes are read live from the Tether and Circle contracts on seven networks. Transaction integrity checks that a hash exists, succeeded, is confirmed and carries a canonical USDT/USDC transfer — and resolves the real sender.

Each of those checks — and the others: processor evidence, wallet ownership, customer behaviour, travel rule, actor attribution, source-of-funds exposure — reports its own status on the response and in the receipt. "No known match" is not "clean", and a dimension we cannot cover says NOT_AVAILABLE or MISSING instead of pretending. Wallet ownership, for instance, is COMPLETE only behind a real proof — an EIP-191 signature or a micro-transfer of an exact amount from the wallet — and PARTIAL behind a mere declaration.

Ten networks are covered for sanctions screening (Ethereum, Base, Arbitrum, Polygon, Avalanche, Optimism, BSC, Tron, Bitcoin, Solana); on-chain verification runs on the EVM chains today.

Why a broker needs it

When a supervisor asks "did you screen this deposit?", a single score cannot answer the follow-up: against which lists, on which date, and what about the parts you could not check. A per-dimension matrix stored with the decision turns "we checked" into something specific and defensible.

It is also how third-party reliance stays honest. Your processor's "approved" is recorded as a status; only an evidence reference makes processorEvidence COMPLETE and lifts the assurance tier. Without one, the gap is visible in your own record rather than inherited as somebody else's confidence.

How it works

Every screening returns three separate things: assessment (what the data says — ADVERSE_SIGNAL, NO_ADVERSE_SIGNAL, INCONCLUSIVE or PROVIDER_ERROR), coverage (which checks ran, per dimension: COMPLETE, PARTIAL, MISSING, STALE or NOT_AVAILABLE) and decision (what your policy concluded from both). The matrix is embedded in the signed Decision Receipt and printed on every evidence pack.

The policy's mandatory-coverage rule reads the matrix: if a mandatory dimension is MISSING or STALE — the RPC did not answer, the newest OFAC snapshot is older than your limit — the decision is TECHNICAL_HOLD, never a silent pass. The assurance tier (PUBLIC_BASELINE, PROCESSOR_ATTESTED, COMMERCIAL_ENRICHED, DUAL_SOURCE_ASSURED) is computed from the same matrix.

Try it without an account: Free wallet sanctions check · USDT blacklist check · USDC blacklist check.

What it does not do

GateCoverage does not rate risk and does not clear anyone. Sanctions lists cover a small fraction of illicit addresses, so NO_ADVERSE_SIGNAL means only that nothing adverse was found on the sources that ran. Commercial attribution (mixer exposure, cluster labels) is a dimension that stays MISSING until a provider fills it — we do not fabricate it from public data.

API

{
  "assessment": "NO_ADVERSE_SIGNAL",   // not "clean" — nothing found on the sources that ran
  "coverage": {
    "sanctions": "COMPLETE", "issuerFreeze": "COMPLETE", "transactionIntegrity": "COMPLETE",
    "processorEvidence": "MISSING", "walletOwnership": "MISSING", "customerBehaviour": "MISSING",
    "travelRule": "MISSING", "actorAttribution": "NOT_AVAILABLE", "sourceOfFundsExposure": "NOT_AVAILABLE"
  },
  "assuranceTier": "PUBLIC_BASELINE",
  "decision": "REVIEW"
}

Full reference: /docs#semantics · OpenAPI 3.1

Related modules