Running a raffle

Creating

On Raffles, start with Collab: pick your own collection as the host and search the registry for the partner; if the partner is not listed yet, paste its contract address and Fealty looks it up on every supported chain, shows you what it found, and adds it to the registry once you confirm it is the right one. The pair fills in the title, the artwork, the mint-wallet chain and the requirements your last raffles usually asked for (skip it for a plain giveaway). Then check the type, title and description (Use your own banner replaces the collections' artwork), the number of winners and the info they get, and when it runs. Starts: Right away, or Schedule a time; until then a scheduled raffle is listed as Upcoming (on Explore, the raffle directory and your community page, with its page open so members can get ready, but nobody can enter), then it opens by itself and goes out to Discord at that moment if you chose to post it (Open now on its page opens it early, and its start stays editable under Settings). Ends: 1h, 6h, 12h, 24h (the default), 2 days or 1 week, counted from the moment it opens, an exact date with Pick a date, or No end to draw it yourself. The mint date is optional; with one set, pick when winners get their mint reminders. Build the requirement rows, and under More options choose who can see it, an optional points ticket cost, and previous raffles whose winners can't enter again. Post it to Discord when it's created (or when it opens, for a scheduled raffle) posts it to your saved raffle channel (Change picks another channel or ping). Save as draft keeps it to your team: nothing is public, nothing is checked yet, and half-done rows (a like task still waiting for the partner's post link) stay as typed. It shows as Draft in your raffle list and opens back in this form, where Publish raffle (or Schedule raffle) runs every check and takes it live; a preset length like 24h counts from that moment. If creating a raffle fails a check, the form is kept as a draft and reopens with the problem, so nothing you typed is lost. Duplicate on any raffle reuses it as a template: it opens this form pre-filled, so the title (which fixes the page URL) and the requirements are still editable before the copy is created. Dates and invite codes don't carry over: a copy starts on 24h.

Sharing

/raffle-post raffle_id:<id or slug> (the slug is the name part of the raffle page URL) posts it to the current channel with an Enter button and a link to the raffle page (the dashboard's Post to Discord button does the same into your saved raffle channel in one click; the arrow next to it posts to another channel or with another ping, and Save this choice makes that the new default. With no saved channel, the button asks where to post first). The announcement pings @everyone by default, exactly like quests; Settings switches that to @here or off per server. Winner announcements never add an extra ping. Share the raffle page on X with the built-in share button.

The draw

When the end time passes, the draw runs by itself: exclusions apply, holdings are re-checked for raffles whose odds depend on them (see Entries and odds), retweet tasks and project-account like tasks are batch-verified, winners are picked (weighted, FCFS order, or everyone for wallet collections), follow tasks and other-account like tasks are checked winner-first with automatic redraws, and the results post to #raffle-winners with mentions and a winner card.

Need it sooner? Draw now on the dashboard or /raffle-draw in Discord runs the same pipeline immediately.

Rerolling

Reroll on a finalized raffle redraws winners from the qualified pool: verification results are kept, follow checks run against the new winners, and the fresh list is announced. Use it when a winner is disqualified after the fact.

Archiving and deleting

Archive (on a drawn or cancelled raffle) hides it from every member-facing surface: the community Raffles page, the hub and the mint calendar; the raffle page stops resolving for members. Managers still see everything, and Unarchive brings it back. Nothing is lost either way: entries, winners and exclusion lists stay intact, and other raffles' "previous winners not eligible" rules keep working.

Delete is permanent and only available while a raffle has zero entries, which is what makes it safe: test runs and misconfigured drafts can go, but anything entered carries ticket-point, winner and exclusion history and must be archived instead. Deleting also removes the posted Discord announcement and any scheduled mint event.