Screening before the
transaction is signed.
Since the Tornado Cash designations, interfaces that facilitate transactions carry sanctions exposure of their own. ChainEvidence screens the destination address before the wallet prompt appears — without adding an account wall.
Exposure at the interface
Sanctions exposure
Enforcement practice since Tornado Cash makes clear that frontends facilitating transactions with designated addresses face regulatory risk of their own.
The permissionless constraint
Controls that demand sign-ups or KYC walls contradict how these platforms work. Screening has to happen inline, without changing the user's flow.
Small engineering teams
Integrations that take months and a dedicated team are not viable for platforms run by a handful of engineers. The control has to be light to adopt and light to keep.
Risk posture is a policy choice
Whether to warn, block designated addresses only, or block high-risk flows too is a decision for your policy — the tooling should express it, not dictate it.
Inline screening for your frontend
One script tag
A single script tag in your frontend — no build changes and no backend integration. Works with React, Vue, Svelte, or plain HTML.
Pre-transaction screening
Outgoing transactions are intercepted and the destination address is screened against sanctions lists and risk intelligence before the wallet prompt appears.
Three enforcement modes
Warn, block-sanctioned, or strict — you choose the posture. Sanctioned addresses can be blocked outright while risky ones show a dismissible warning.
Usage-based access
Pay per check with a prepaid balance and client-side caching — suited to frontends. Platform plans add monitoring, audit trail, and reporting when you need records.
One tag in the frontend
<script
src="https://chainevidence.net/api/v1/sdk.js"
data-key="YOUR_API_KEY"
data-mode="block-sanctioned"
></script>What the user sees when a destination is screened:
The transaction proceeds normally. No modal, no delay.
A warning is shown with the reason. The user can review and proceed or cancel.
In blocking modes, the transaction is stopped before it reaches the wallet.
From evaluation to production
Evaluate in the sandbox
Engineers validate coverage, latency, and verdict semantics against the live API the same day — no procurement required to begin.
Pilot on monthly terms
Run production traffic under month-to-month terms while internal review and procurement complete.
Move to an enterprise agreement
Negotiated volume, a contractual SLA, self-hosted or EU-resident deployment, and a data processing agreement for vendor due diligence.
Screen at the interface.
Add pre-transaction screening with one script tag, then bring monitoring and audit records in when your obligations grow.