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 | Any post works. From one of your project X accounts: one batch likers read with the author's authorization. From anyone else: checked winner-first through each winner's own connected X, with redraws for failures |
| Joined a Telegram channel | At entry AND at draw | Free membership checks against your Telegram channel or group; winners are re-checked at the draw and leavers are redrawn |
Telegram join tasks
Telegram does not expose channel member lists publicly, so verification runs through a bot:
- You add the Fealty Telegram bot to your channel or group before creating the task. For channels the bot must be an admin (only admins can look up channel members); for groups a plain membership is enough. The task is validated when you create the raffle, with a clear error if the bot is missing.
- Entrants link their Telegram account once, from their Account page (an explicit "Log in with Telegram" click; Fealty stores only the Telegram id and username, no tokens, no message access).
- Fealty checks membership when they enter and re-checks winners at the draw. The checks are free: no engagement credit involved.
Reference the chat by public @username. Private chats work too: use the numeric -100… id and paste the invite link so entrants get a Join button.
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.
How like tasks are verified
X reveals a post's like list only to the post's author, and everyone's own likes only to themselves — no data source, paid or otherwise, can see them. So like tasks work the way the whole industry's do: the Like button is the proof. Pressing it on the raffle page (or in the Discord entry confirmation) records the click and then opens X's like screen; at the draw, entrants without a recorded click are disqualified from the like task. A like made straight on X without the button cannot be seen and does not count — the raffle page and the Discord announcement both say so. This costs no engagement credit at all.
Raffles created before the Like button existed still finalize under the old read-based verification, so nobody is disqualified for not pressing a button that wasn't there.
Add an email requirement and every entry snapshots an email address for the host: auto-filled from the entrant's profile when Fealty knows it (Discord sign-in supplies one), typed in otherwise (both on the web page and via a modal on the Discord Enter button). It lands in the winners export's email column (offered in the column picker only on raffles with this requirement). The address is stored on the entry only; it never overwrites the account's profile email.
Mint wallet
Give the raffle a chain (say Solana) and entrants supply a wallet of that family at entry: either one of their signature-verified linked wallets, or a pasted address (validated for the chain, no wallet connection required). The choice is snapshotted as their mint wallet and that address is what the winners export delivers to your partner. Pasted addresses are marked self-declared in the export and the entries table; they never count toward NFT-hold requirements or holder roles, which always verify against linked wallets only.