Skip to main content
You cannot screen one user inside a pooled vault. You cannot export one user’s history from a shared ledger. Compliance teams get nothing to hold on to. Blend runs one account per user, so every control attaches per user. Two controls run on every account today: automated sanctions screening and a per-account audit trail.

​
What per-account control changes

Pooled productsBlend
ScreeningThe pool has one address. Users are invisible on-chain.Every user’s account is screened individually.
RecordsOne ledger for everyoneA complete, exportable log per account
Acting on a flagged userTouch the pool, touch everyoneBlock one account. No one else is affected.
Verifying it happenedTrust the operatorOn-chain activity is verifiable by anyone.

​
Sanctions screening

Every account address is screened against OFAC and global sanctions lists. Screening is automated and runs at three points.
WhenWhat gets screened
Before account creationThe user’s wallet address, before a Safe is deployed
On deposit flowsThe depositing address, on every deposit quote
OngoingEvery account, on a recurring basis. Stale results get re-screened.
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.
Your auditors get per-user records. Your regulators get an exportable trail. You get both without building either.

​
Who does what

Blend’s controls cover the account layer. Your compliance program covers your customers.
You (platform)Blend
KYC and AML for your usersSanctions screening on every account
Licensing and customer termsPer-account audit trail
Your regulatory perimeterStructural fund segregation
Deciding who can open an accountBlocking flagged addresses from Blend’s rails
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.
Last modified on July 3, 2026