Deny lists
Every payment this product evaluates is checked against 148 addresses across three lists before it can be allowed. Each list, who publishes it, when this copy was retrieved, and what the check does and does not mean is below. The figures are generated from the code that runs, so they cannot drift from what is shipped.
What is checked
OFAC SDN — Digital Currency Address, ETH
| Publisher | US Department of the Treasury, Office of Foreign Assets Control |
|---|---|
| Source | SDN.XML — the "Digital Currency Address - ETH" entries |
| Addresses in this build | 123 |
| Retrieved | 2026-11-16 (2 days old) — inside the 45-day window |
| Refresh | A sync job rewrites the generated file from SDN.XML; the weekly release check fails when it is older than 45 days. |
| Effect | Hard deny. A payment to one of these addresses is refused with the reason sanctioned address (OFAC SDN). It is not a review, and no policy setting overrides it. |
Known drainers (curated)
23 addresses compiled from 10 sources, each entry carrying the advisory or dataset it came from. The curation policy and extension process live in the repository; the sources below are the record of where each address originated.
Effect: hard deny with the reason known drainer. Separate from the sanctions check because the fact is different — a sanctioned address may make paying you the problem, a drainer takes the funds — and the refusal names which one applied.
Non-receivable sinks
2 addresses where funds cannot be recovered: the canonical burn address and the zero address. Same verdict, truthful reason — paying one destroys the money rather than losing it to a thief.
Provenance and freshness
- Generated, not typed. The addresses live in generated source files that a sync job rewrites from the publisher's own feed. Nobody hand-edits the list, and the counts above are read from those files at build time.
- Dated. Each list carries the date its copy was retrieved. The sanctions list has a 45-day staleness window, and the release check fails when it is exceeded — a build that cannot prove its list is recent does not ship.
- Reviewed into the repository. Source URL, retrieval date and the publisher's own naming are kept with the entries, so a disputed block can be traced to the advisory that caused it.
- Delisting works the same way. When a publisher removes an address, the next sync removes it here and the block stops — the lists are replaced wholesale, not appended to.
What this does not do
Being specific about the limits is the point of the page. A tool that blocks addresses is trusted on the accuracy of its lists, and overstating that accuracy is how the trust gets lost.
- Exact address match only. A payment is compared to a list entry after lowercasing. No fuzzy matching, no clustering, no look-alike detection — an address one character away is a different address, because it is one.
- No hops, no exposure analysis. We do not trace where funds came from or went. An address that received tainted funds but is not itself listed will not be blocked.
- EVM addresses only. The sanctions data used here is the ETH entry set. Other chains and non-EVM address formats are not covered by this check.
- Lists are incomplete by nature. A drainer not yet in any published advisory is not in this list. Absence of a match is not evidence that a counterparty is safe.
- Not a compliance product. This is not screening, onboarding, identity verification or legal advice, and using it does not make anyone compliant with any regime. It is one exact-match check against public data, with the provenance above so you can judge it yourself.
Data as of 2026-11-19. To verify any figure here, read packages/preflight/src/sanctioned-addresses.ts and known-drainers.ts — the counts are generated from them. Glossary · ← back to PayStage