ChainScan gives institutions one platform to scan wallets and tokens, run KYT on every transaction, and operate compliant wallet infrastructure — across every major chain.
Block the risky transaction before it signs — not alert you after it's gone.
Sanctions, mixers, honeypots and velocity, screened across every chain.
Monitoring and controls that satisfy VQF, MiCA CASP and EU AML.
You stay the custodian; ChainScan is the compliant layer in front.
Subscribe to the layer you need — from a read-only scan API to a policy gate in front of your own custody. They share one engine, one API, and one set of chains.
Every service reads from the same screening, scoring and policy core. Set a rule once and it applies everywhere; a risk seen once is known everywhere.
Allow, hold, or block any transaction intent in milliseconds — advisory, or enforced inside your Fireblocks co-signer.
Gate every outgoing transfer through policy before it signs. You keep custody; ChainScan keeps you compliant.
Approvals, honeypots, mint and blacklist traps, upgradeable proxies — computed from the chain.
Continuous KYT: sanctions, mixers, velocity and structuring, with alerts and webhooks.
Keep autonomous agents inside their mandate — session-key scope, spend caps, expiry and live screening.
ChainScan is the software; you stay the custodian of record, compliant under VQF, MiCA CASP and EU AML.
ChainScan assumes the attacker is already inside and holds a valid signing path — and stops the unauthorized transaction anyway.
A wallet, app or agent requests a transfer.
Recipient, token, amount and velocity checked against sanctions, mixers and your policy.
In a separate trust domain the signer can't override.
Only an allowed or approved transaction reaches Fireblocks to be signed.
ChainScan links to your existing custody and screens across every chain you settle on — no rip-and-replace.
$6.3B drained in about 20 minutes — with valid signatures, not stolen keys. Key security couldn't see it. An independent, deny-by-default authorization layer would have.
Three controls had already failed. ChainScan is the fourth — and it holds.
You hold your own keys and remain the custodian of record under your own licence. ChainScan is the compliance and authorization layer in front of your custody — every transfer screened and policy-checked.
The allow/block decision runs in an isolated trust domain, so a compromised server can't forge an approval — the exact gap the $6.3B attack exploited.
Per-chain velocity limits and automatic halts cap the damage when every upstream control has already failed.
Your assets and keys stay in your institution's Fireblocks-grade MPC and secure enclaves. ChainScan adds the compliant authorization layer on top.
We work with every customer directly — scoping the deployment, the policies and the integration to your stack. Tell us how you move funds and we'll show you where ChainScan fits.
A deny-by-default gate in front of your existing Fireblocks or MPC custody.
Sanctions, mixer and velocity controls that satisfy your AML obligations.
ChainScan is the software; you stay the custodian of record — VQF, MiCA CASP, EU AML.
Session-key scope, spend caps and live screening inside the agent loop.
ChainScan comes from a team that has spent decades in payments and fintech infrastructure — acquiring, card programmes, EMI and custody. We kept seeing the same failure: the keys were safe, but the wrong transaction still got signed. So we built the control we wanted in front of our own funds — a layer that stops the transfer nobody meant to send.
We work with every customer directly. Moving other people's money is personal, and so is the way we onboard you.
— The ChainScan team · payments & fintech infrastructure
Bring a transaction flow and we'll show you exactly where ChainScan stops it.