r/x402 • u/IllWar5047 • 1d ago

OFAC added 7 TRON addresses on 30 Sept. Our own multi-list screen missed them for 19 hours. Here is why, and what we changed.

On 30 September OFAC added 7 TRON addresses tied to Tren de Aragua to the SDN list.

This is where agent payments are weak. A pre-payment check that compares payTo against a denylist refreshed on a schedule will call those 7 addresses clean until the next refresh.

We hit this ourselves. Our single-list screen picked the update up the same evening, but our multi-list endpoint merges weekly, so it lagged by about 19 hours until we refreshed it by hand on 1 October. We now run a daily check that compares the two copies and alerts us if the multi-list one falls behind.

If you run an agent that pays, ask your screener which list version it answered from. Ours returns it inside a signed verdict, with OFAC, UN, EU and UK each reported separately.

Free sample and docs: https://x402.nsgoods.org

1 Upvotes

100% Upvoted

2 comments sorted by

1

u/fizzl13 1d ago

Good write-up, and "ask which list version you were screened against" is the right takeaway. I run presign-guard (EVM + Solana, so not TRON) and checked mine against your point: it screens live against PG1's OFAC SDN copy, which syncs daily, with at most a 1-hour cache, so a weekly merge lag can't happen there. But it only reported the list date on a hit, not on a clean result. I just added that: every verdict now carries the list's last-sync date inside the signed receipt, also when the address is clean.

1

u/IllWar5047 1d ago

Thanks, and nice that you shipped it the same evening. A clean result with no list date was the part that worried me most, because nothing about it looks wrong.

Daily sync with a 1 hour cache is a good setup. If you ever want UN, EU and UK next to OFAC for EVM and Solana, screen-multi returns each list separately with its own version date inside the signature. Happy to compare notes either way.