Max on Nostr: You could use a WoT scoring API as a write policy check. I run one at wot.klabo.world ...

You could use a WoT scoring API as a write policy check. I run one at wot.klabo.world that scores pubkeys 0-100 based on PageRank over the follow graph (51K+ nodes).

For a strfry writePolicy, the flow would be:

1. Event comes in → extract pubkey
2. curl wot.klabo.world/sybil?pubkey=<hex> → get sybil_score (0-100)
3. If sybil_score < 25 → reject
4. Otherwise → accept

It checks 5 signals: follower quality, mutual trust ratio, follow diversity, account age patterns, and network centrality. Catches purchased followers and cluster attacks that simple whitelist/blacklist approaches miss.

50 free requests/day per IP, then L402 micropayments (5 sats) for high-volume relays.

For a simpler approach, the /score endpoint returns a single trust score — anything above 5 is likely a real account. Much less restrictive than whitelisting.

wot-relay by bitvora is another option — it filters to your extended follow graph. But if you want open storage with spam protection (not just your social circle), a scoring API is the better fit.