Campaign details
Give the campaign a specific name and a description that explains the community, the reward, and the requested participation. Avoid promises that the campaign configuration does not support.
A draft is private to its creator. Review it before locking the configuration. Draft updates replace the editable configuration; a full replacement also regenerates task IDs.
Choose one reward asset
The pool contains one reward asset. For ERC-20 tokens, convert the displayed token amount using that contract’s decimals. The form accepts exact base units rather than floating-point amounts.
| Asset | Configuration |
|---|---|
| ERC-20 | Token contract and total integer quantity in base units. |
| ERC-721 | Collection contract and a unique inventory of up to 100 token IDs. |
| ERC-1155 | Token contract, one token ID, and its total integer quantity. |
Write clear tasks
A campaign supports one to twenty tasks, with at least one required task. Supported types include X repost, like, comment, tag, Discord join, and custom tasks.
Each task has a target HTTPS URL and instructions. Tell participants what evidence to provide. X tasks must link to X or Twitter, and Discord tasks must link to Discord.
Set the schedule
Dates must be future and strictly ordered. The claim deadline must allow at least 24 hours after the review deadline. Local dates entered in the form are saved as UTC.
| Deadline | Purpose |
|---|---|
| Start | The scheduled beginning of participation. |
| Entry cutoff | Registration and evidence submission close. |
| Review deadline | Review, eligibility locking, and finalization must finish. |
| Claim deadline | Recipients must complete their claims. |
Lock the configuration
Locking commits the reward asset, quantities, tasks, rules, and deadlines. These settings cannot be edited afterward.
Check the refund recipient, capacity, winner count, and every token ID before locking. Deploy and fund the escrow before the scheduled start.