I keep seeing crypto teams rebuild the same OFAC poller — so I built it once

Hey IH,

Background: every crypto company that touches the US has to screen wallet addresses against the OFAC sanctions list (the "SDN list"). The data is free and public. But almost everyone ends up hand-rolling the same boring pipeline on top of it:

- a cron that pulls the SDN list

- a diff to catch when a watched address gets added or removed

- multi-channel delivery (webhook / email / Telegram) with retries when it fails

And the failure mode is the worst kind: the poller dies quietly, nobody notices, and the first sign something broke is an auditor's question.

So I built that layer once and turned it into a product: OFAC Alert (https://ofacalert.com). Hourly refresh, HMAC-signed webhooks, delivery-status history so a silent miss can't hide, batch screening, and a REST API. Free tier monitors one address with no signup gate; $99/mo when you outgrow it.

What it isn't: not a Chainalysis/TRM/Elliptic replacement — no risk scoring, no clustering, no $15k contract. Just the reliable monitoring-and-delivery plumbing for the free data.

Where I'm honestly at: launched a few days ago. A handful of visitors so far (fun detail — a couple came from ChatGPT citing the site), zero signups yet. The product works end to end; the hard part now is 100% distribution.

What I'd love from you:

1. If you've worked at a crypto/fintech shop — was sanctions monitoring a hand-rolled script, a paid vendor, or "we'll deal with it later"?

2. For a niche B2B compliance tool like this, where would you actually go to find the first 10 users? (HN auto-flagged my new account; cold email is slow.)

3. Anything in the positioning that makes you go "nah, I wouldn't"?

Roast it — I'd rather hear the hard feedback now than later.