Documentation
What Rafflor does, how a draw works, and what every figure on these pages is read from.
These pages explain the product and the protocol behind it. They are not an integration guide, and the figures in them are read from the deployed contracts rather than written down.
- How it works — a raffle from locked prize to claimed prize, in five steps.
- Fees & limits — what it costs, how a ticket price is derived, and the limits the vault enforces.
- Draws & refunds — how a winner is selected, how settlement and claiming work, and what happens if a draw cannot complete.
- Supported prizes — which assets can be raffled and what a listing does and does not mean.
- Contracts — the deployed addresses, the parameters read from them, and what nobody can change.
- Technical details — the protocol below the product layer, for readers who want to check it.
The short version
A creator locks a prize. People buy tickets in USDC. Entries end at the deadline or when the last ticket sells, anyone can close the raffle, and a winner is drawn from publicly verifiable randomness that did not exist when entries ended. The creator receives the ticket proceeds less the protocol fee, the protocol takes that fee plus a creation fee, and the winner receives the prize.
There is no admin over winners, escrows or randomness. One address can pause the creation of new raffles and can reach nothing else.
[unavailable] above rather than as a number from memory:
- treasuryAddress — TREASURY_ADDRESS is not configured
- explorer — no block explorer is configured for this chain