Entry requirements
Every requirement type, what gets verified and when.
Add up to ten requirement rows; entrants must satisfy all of them. Role rows are the exception: they merge into a single "any of these roles" group.
| Requirement | Verified | How |
|---|---|---|
| Holds NFTs | At entry | Live holdings read across the entrant's linked wallets (staked NFTs count) |
| Has Discord role | At entry | Any of the listed roles qualifies; each can carry an entry multiplier |
| Joined this Discord | At entry | Membership check, so outsiders must join your server first |
| Follows on X | At draw | Checked winner-first against the live follow graph; failures are redrawn |
| Retweets a post | At draw | One read of the post's retweeters disqualifies non-retweeters before the draw |
| Likes a post | At draw | Batch likers read with the author's authorization; the post must be from one of your project X accounts |
Why X tasks verify at the draw
Someone can follow to enter and unfollow a minute later, so the check that matters is the one at closing time. Verifying then also keeps costs sane: follow checks run only against provisional winners (with automatic redraws for failures) instead of every entrant. Any X task on the raffle requires entrants to have their X account connected; the checklist shows this before they enter.
Mint wallet
Give the raffle a chain (say Solana) and entrants must have a wallet of that family linked; they pick which one at entry and it's snapshotted as their mint wallet. That address is what the winners CSV delivers to your partner.