Giveaway On-Chain & Creator Raffles
Prizee Raffle's Raffle engine (API poolMode: task_reward) lets protocols, DAOs, and creators incentivize X actions with guaranteed on-chain giveaways. The UI label is Raffle, not Task Reward.
The Problem with Traditional Web3 Giveaways
Most social giveaways on Twitter/X, Telegram, or Discord suffer from:
- "Fake Giveaways": Organizers announce rewards but never send the tokens.
- Bot Farming: Sybil attacks drain rewards before legitimate community members can participate.
- Manual Distribution Overhead: Sponsoring teams spend hours copy-pasting addresses and manually sending transactions.
Prizee Raffle solves this entirely through On-Chain Escrow + Automated Task Verification.
Supported Verification Tasks
Creators can configure one or more required tasks for participants:
Task links must be X URLs (x.com / twitter.com): profile for follow, /status/{id} for comment/retweet/quote, /i/communities/{id} for community. Create/edit and the API reject other hosts.
| Task Kind | Action Required | Verification Method |
|---|---|---|
x_follow | Follow the linked X profile | Sorsa /check-follow |
x_retweet | Repost the linked post | Sorsa /check-retweet plus retweeter list and timeline fallbacks |
x_comment | Reply on the linked post | Sorsa /check-comment |
x_quote | Quote the linked post with text (not a plain repost) | Sorsa /check-quoted plus timeline/quotes fallbacks |
x_community | Join the linked X Community | Sorsa /check-community-member |
Private X accounts cannot be verified. Indexing can lag 1–2 minutes after the user acts.
Settlement Modes
Creators choose between two distinct settlement models:
1. First-Come, First-Served (FCFS)
- Mechanics: The prize pool is split evenly among the first $N$ verified participants.
- Slot Capacity: When slots reach 100% (e.g. 50 / 50 slots claimed), the campaign locks immediately.
- Payout: Winners are paid immediately upon completing all tasks, or in a single automated batch when the campaign countdown concludes.
- Cryptographic Proof: Verified task completion timestamps stored on-chain.
2. Random Draw (random)
- Mechanics: All users who complete the required tasks before the deadline are entered into a raffle.
- Selection: When the round closes, winners are selected randomly using the on-chain block hash seed.
- Weighted Pools: Higher-tier supporters or users with higher referral scores can receive bonus entries.
Anti-Sybil & Quality Filters
Creators can enforce quality thresholds on eligible accounts:
- Minimum Followers: Disqualifies freshly created bot accounts with 0 followers.
- Minimum Reputation Score: Algorithmic scoring evaluating account age, activity, and authenticity.
- X Blue Verified: Optional toggle requiring verified premium accounts for high-value rewards.
Prize kinds
- USDC: Seed escrow; FCFS pays as slots fill; Random pays at deadline from the block hash. Leftover escrow returns to the creator.
- Custom: Off-chain prize (WL, NFT, merch). No seed. Each winner receives 1 unit of the labeled prize (10 GTD slots → 1 GTD). X, Telegram, and wallet are taken from Profile. Creators see those fields on WINNERS and mark Fulfilled. Prize UI uses a cup icon, not USDC. Win notifications name the prize and link to WINNERS.
Deadline follow-up
- FCFS: Winners are already locked when they finish tasks. At
drawAtthe raffle closes; empty slots stay empty. - Random: At
drawAt, users who finished every required task are drawn with the Arc block hash.
Payout Execution (USDC)
When a USDC raffle concludes:
- Completions and quality gates are checked.
- Escrow pays winner connected wallets (
user.wallet) on Arc. - Each payout has an ArcScan receipt.
- Unfilled FCFS value (or unused random pool) refunds to the creator.