Agent pays a DAO with a sanctioned member

What happens when an agent pays a DAO that includes a sanctioned member, the 50 Percent Rule risk, and the control.

TL;DR

TL;DR: Paying a DAO can violate sanctions if a blocked person owns or controls it, especially under the 50 Percent Rule. Screen the DAO and its controlling members before funds move.

What happens

An agent is instructed to pay a DAO treasury or a contributor. The DAO itself looks neutral, but a blocked person sits among its members or controls enough of it to trigger the 50 Percent Rule, which blocks entities 50% or more owned by a blocked person. The payment goes to the DAO, but the blocked member is the reason it is unlawful, and the surface address does not reveal who is behind it.

The risk

OFAC enforces under strict liability, so intent is not required, and civil penalties start at $356,000 per violation. A DAO's decentralized structure does not remove the rule; if a blocked person owns or controls it, the payment is a transaction with a blocked party even when the agent only sees the DAO's address.

The control

Screen beyond the surface address. agentmail's kya_verify attaches know-your-counterparty evidence to the DAO, risk_score weighs ownership and control risk, and sanctions_check screens the address against 947 OFAC-listed crypto wallets in one call under 100 ms. Clean returns ALLOW, flagged returns BLOCK, and the SCREEN, SCORE, STOP, STAMP protocol halts a flagged payment at the STOP gate. That documented decision is what an enforcement review credits.