Discord Raffle Bot for NFT & Web3 Communities

Why nft & web3 servers use raffle differently

In an NFT community, a raffle usually decides something with resale value, which makes eligibility and auditability the whole design. Entries have to be checkable against a holder role and a verified action, the snapshot has to be stated before the announcement, and the winner list has to be public. Anything less becomes a dispute the same day.

What it costs to run at nft & web3 scale

Two servers, one public and one holder-gated, can run parallel draws with different eligibility from one system. The cost is the allocation: reserving 70% of allowlist spots for holder-gated draws and 30% for public campaigns is a common split, and publishing the split up front removes most of the argument.

How to configure it for a nft & web3 server

State the snapshot time in the announcement, require the verified action, and gate the holder draw on wallet-linked roles. Publish winners in the channel where entries were taken so the audit trail sits next to the rule.

The mistake nft & web3 servers make with raffle

Allowlist raffles generate accusations of insider allocation more than any other mechanic. The defence is arithmetic published before the draw: spot count, total entries, per-member cap, and the draw method. Announcing only the winners is what turns a fair draw into a week of moderation.

FAQ