// for dao treasuries
Know who's actually requesting the grant.
Score grant applicants, builder retros, contributor rewards. Make sure your treasury is funding real contributors — not entities running 30 wallets to extract a 30× share.
Which detection methods matter here
Funding clustering
Catches contributor wallets funded from the same source as past grant applicants — strong fraud signal.
Cross-chain entity linking
Sybil grant applicants often apply under different names on different chains; we link them.
Behavioral fingerprint
Wallets with no organic contribution history but freshly-applied grant patterns get scored as suspicious.
Public appeal flow
Grant applicants you flag get a fair, 48h public appeal window — protects you legally + reputationally.
// mini case study
DAO treasury audit: 12 sybil applicants in 100
An L2-aligned DAO ran their last 100 grant recipients through SybilShield. 12 scored ≥70: same funder, no prior contribution history, applied via 3 different pseudonyms. Treasury saved an estimated $340k over 6 months. Public appeal flow reversed 1 false positive (real contributor with funky funding history).
See more case studies →Suggested plan
Growth
$2,500/mo
Quarterly grant batches and contributor retros fit easily. Includes evidence export for community publication.