What per-account control changes
Sanctions screening
Every account address is screened against OFAC and global sanctions lists. Screening is automated and runs at three points.
What a flag does. A flagged address is blocked from Blend-routed operations. Deposits, routing, and rebalancing stop. The flag holds until a person reviews it. Flags never clear automatically. Every screening event is recorded.
What happens if screening goes down. The check fails closed. If the screening service is unreachable, operations are blocked, not waved through.
What a flag can never do. A block gates Blend’s rails. It does not confiscate. Assets stay in the user’s Safe, where Blend structurally cannot seize them. Non-custody is not suspended for flagged accounts. It cannot be suspended for anyone.
For implementation details (screening provider, caching, fail-closed behavior), see the security deep dive.
Per-account audit trail
Every action on every account is logged and exportable. Positions, flows, caps, and exception handling all operate at the account level.- In the portal. Review and export any account’s log from Audit Logs. Filter by account, action, or time range.
- On-chain. Every Safe is a real contract on a public network. Anyone can verify its activity on a block explorer, without asking Blend.
Who does what
Blend’s controls cover the account layer. Your compliance program covers your customers.
This is a strong starting point, not a compliance program. You keep yours. Blend makes the account layer visible, screened, and provable.
Regulatory Alignment
How the structure maps to MiCA, US guidance, and FATF.
Accounts & Custody
Why per-user accounts make these controls possible.
Security
The defense layers protecting every account.
Audits
11 independent audits. Every report public.