Winners and delivery

The announcement

Winners are announced in #raffle-winners automatically: mentions, a rendered winner card and a link to the raffle page. Wallet collections announce the number of qualified wallets instead. The raffle page also lists the winners.

Winner rewards: public, private, invite codes

Raffles can carry three optional reward fields, set on the create form (or later in Settings):

• Public info for winners is posted with the announcement and shown on the raffle page. Mint details, claim windows, next steps.
• Private info for winners is shown only to winners: on the raffle page after they sign in, and via the View my reward button under the Discord announcement, which replies ephemerally (only the clicker sees it). Use it for claim links, invite servers or contract instructions.
• Invite codes, one per line: each winner is assigned one code at the draw, revealed the same two private ways. Codes stick through rerolls; a code that was assigned to a replaced winner is treated as seen and never issued again. If there are fewer codes than winners, the extra winners get the private info only.

Private info and codes are stored encrypted; nothing private is ever posted to a channel.

If verification can't run

A draw never announces winners it couldn't verify. When the X reads behind retweet, like or follow tasks can't complete (engagement credit ran out, or the data provider is down), the draw pauses: entries stay closed, nobody is disqualified, and the raffle shows a "draw paused" badge with the reason. It retries automatically every few minutes; "Draw now" retries instantly after a top-up. If you'd rather not wait, Draw anyway runs the draw without X verification, as an explicit choice.

The sheet your partner wants

Winners on the raffle card opens a column picker with one row per winner. Tick the columns your partner asked for, then either:

• Copy puts the rows on your clipboard as tab-separated text, so they paste straight into Google Sheets, Excel or Notion as proper columns. No downloading two files and stitching them together.
• CSV downloads the same selection as a file.

Available columns: Discord name, Discord ID, X handle, wallet address, wallet source, other wallets, and email (offered only when the raffle has an email requirement). Your selection is remembered in the browser, so the next raffle exports in the same shape in two clicks.

The wallet address is the one snapshotted at entry on the raffle's chain, which is exactly the list a partner project needs for their allowlist. Wallet source says where it came from: linked (picked from the entrant's signature-verified wallets) or self-declared (typed in at entry). Other wallets lists the entrant's remaining signature-verified wallets, in case the partner wants alternatives. Email is filled when the raffle has an email requirement (auto-filled from the entrant's profile or typed in at entry). X handles come from the connected accounts that were verified during the draw.

Mint reminders

The moment you set (or move) a raffle's mint date, Fealty announces it in #mint-calendar and creates a Discord server event for it, so any member can tap Interested and get Discord's own notification when the mint starts. The date can be set at creation or added later, whatever the raffle's status.

As mint time approaches, winners are pinged in #mint-calendar at the times you pick on the raffle: any of 24h, 12h, 6h, 3h, 1h and 15m before, plus at mint time (default: 24h, 1h and at mint). Every post carries buttons for the server event, the raffle page and an add-to-calendar link. Moving the mint date re-arms the reminders for the new time.

Private raffles stay off the public calendar: no announcement and no server event, only the winner pings.

Server events are capped by Discord at 100 upcoming per server and each one expires on its own an hour after its mint, so the list never piles up. If you'd rather not have them, turn them off in Settings under Announcements: no new events are created, while existing ones keep their subscribers until their mint passes. Everything else keeps working either way.