OFAC screening for DAOs explained

How a decentralized autonomous organization should screen treasury payouts so a blocked party never receives funds.

TL;DR

TL;DR: A DAO that pays a sanctioned wallet or entity violates OFAC even when the vote was token-holder approved. Screen every treasury recipient against the SDN List before the payout executes.

The DAO treasury is a real money rail

DAOs hold treasuries and send funds through multisig wallets or governance-approved proposals. The moment value leaves the treasury, it behaves like any other payment: the sender is responsible for who receives it. A governance vote does not remove that obligation, because OFAC is a strict liability regime and intent is not required.

Who is responsible when no one is in charge

Decentralization does not erase enforcement exposure. The 50 Percent Rule matters here: an entity that is 50 percent or more owned by a blocked person is itself blocked, so a treasury that pays a service provider partly controlled by a blocked party can still be in violation. Civil penalties start at $356,000 per violation.

A practical control for DAO payouts

Insert screening into the payout path. agentmail exposes a screening API that a DAO tool or multisig script can call before releasing funds: one HTTP call under 100 ms returns clean (ALLOW) or flagged (BLOCK), using 947 OFAC-listed crypto wallets and 19,218 SDN names synced hourly. Flagged payouts are held for review rather than sent.