Quests
A Quest is a set of one or more tasks designed to foster interaction between users and a project. It is created by a Requester, who allocates a reward budget to drive engagement, and it is similar to a marketing or user acquisition campaign in traditional business models.
Tasks can include a variety of actions depending on the Questβs goal:
Social media interactions such as: Like, Follow, Retweet, Share, Comment, or Join a community or channel.
On-platform activities including: Registering, Logging in, Depositing, Buying, or Selling through a connected API.
Proof-based submissions where users need to: Submit a File, Enter an Answer, or Provide a URL as evidence of task completion.
Real-world actions like: Checking in at an event, Buying a ticket, or completing other offline tasks tied to specific campaigns.
Quest Status
Each Quest on the DAC platform can be in one of the following states:
Draft β Still being prepared or edited before going live.
Scheduled β Rewards have been deposited, and the Quest is queued to start.
Ongoing β The Quest is live; users can join and complete tasks.
Ended β The Quest is completed, and rewards have been distributed.
π§© Quest Type
A Quest can be configured in one of the following formats:
π Leaderboard β Top participants based on points win rewards.
β‘ First Come, First Served (FCFS) β Rewards go to users who complete the Quest first.
Create a Quest
Before launching a quest, make sure you meet the following requirements:
π Prerequisites:
To proceed, make sure youβve become a MetaCitizen and are logged in with your MetaMask wallet.
You must own at least one Community on DAC
π Important Notes
Personal Communities
Must be KYC-verified to create Custom Quests.
Organization Communities
Must be Verified to create both Custom Quests and Checkpoint Quests.
π οΈ Step 1: Setup
In the Quest interface, click βCreate Questβ to begin. On the Create a Quest page, fill out the required information:
Title: Up to 150 characters.
Avatar & Thumbnail: Upload visual assets to represent the Quest.
Avatar: Shown on the homepage.
Thumbnail: Serves as the Questβs cover image.
Tags: Add up to 5 tags to help users find your Quest.
Description: Briefly explain the purpose and benefits of your Quest.
Schedule: Set start and end dates (can be edited up to 3 times).
Preview Section:
Displays Thumbnail, Quest Details, List of Tasks, and End Time.
You can drag and drop to adjust the order of the tasks.
Live updates as you modify the Quest content.
Once completed, click βNextβ to proceed.
π§ͺ Step 2: Tasks
DAC offers three flexible task templates: Social, Custom, and Checkpoint, along with an All tab that lets you choose from any task type. You can configure tasks by selecting the corresponding tab for each template.
π± Setting Up a Social Task
DAC supports three social platforms:
X (formerly Twitter)
Telegram
Discord
And an extra custom way to any platform:
Visit Link
Steps to configure a Social Task:
Select βSocialβ as the task type.
Choose the specific task platform (X, Telegram, or Discord) or manual set any platform (Visit Link)
Click βAddβ to include the task.
Enter the necessary details:
X Task: Provide the target X account or post URL.
Telegram Task: Input the Telegram group link.
Discord Task: Enter the Discord server URL.
For βGet Roleβ tasks, provide the Role ID to assign.
Visit Link: Enter a valid link starting with http:// or https://
Double-check all fields and move to the next step.
π§° Setting Up a Custom Task
Steps to configure a Custom Task:
Select Task Custom from the Navigation tab, or click on "API" under the All section to start the setup.
Click βAddβ to create a new task.
Provide the following details:
Task Name: Clear and concise. Example: "Register an account on MetaHub."
Short Description: Instructions for how Hunters should complete it. Example: "Sign up on the MetaHub platform and verify your account."
Jump URL: Where users will perform the task (e.g., your website). Example:
https://yourplatform.com/register
API Endpoint: Enter the URL of the API Endpoint that DAC will use to send task verification requests. Example:
https://yourapi.com/api/verify-registered
API Key: Enter the API Key (Optional) to authenticate requests securely. This key will be added to the request header as
x-api-key
.Verification Methods: Choose identity types to include in the verification request:
Wallet Address
Google
Telegram Username
Discord Username
Final Step:
Double-check all fields and test your API endpoint. If the endpoint is not valid, you wonβt be able to continue.
Once completed, click "Next" to continue.
Note: Communities that are not KYC/Verified cannot select Custom tasks.
π‘οΈ Step 3: Qualifications
In this step, youβll define the eligibility criteria and anti-bot protection for your Quest.
π Detection Level (BMAS Anti-Fraud Protection)
Use the slider to set your preferred Bot Detection Level.
Setting it to 100% ensures that only verified users who meet BMAS conditions can participate, dramatically reducing the risk of bot activity or fraud.
π― Participation Qualifications:
Choose the conditions for participating in the Quest, which include:
All Users: Allow any Hunter to participate, regardless of status or activity level.
New Users: Limit participation to unranked Hunters only β ideal for onboarding campaigns.
Minimum Rank: Only Hunters who have achieved a minimum rank (as specified by the Requester) are eligible to participate.
NFT: Only Hunters who hold the required NFTs are permitted to join.
π Step 4: Rewards
π― Reward Type Selection
You must choose the type of reward Hunters will receive. DAC supports three reward types:
πͺ 1. Token
Distribute fungible tokens (e.g., BNB, MATIC, or custom ERC-20 tokens).
Automatically sent to winning Hunters through DACβs smart contract.
Supported networks: BSC and Polygon.
πΌοΈ 2. NFT
Reward participants with non-fungible tokens (NFTs).
NFTs must be uploaded or linked via contract address during setup.
Automatically distributed to winners via smart contract after quest completion.
π 3. Whitelist Slot
Winners receive a spot in a whitelist, often for future NFT mints, token sales, or exclusive events.
Manually managed by the Requester β DAC will not handle automatic distribution.
Once the quest ends, Requesters must export winner data and distribute whitelist slots themselves.
π Chain Selection
Choose the blockchain network for reward distribution:
BSC (Binance Smart Chain)
Polygon (POL)
If your reward type is NFT or Token, you must either input the contract address manually or select from a list of popular tokens, including stablecoins.
π Reward Distribution Methods
DAC supports two primary distribution methods:
β‘ FCFS (First Come, First Served):
Rewards go to the fastest Hunters who complete the quest.
π Leaderboard:
Rewards are given based on the total points earned by each Hunter.
βοΈ Reward Configuration Options
Depending on the chosen method, you can set up rewards using the following options:
β‘ FCFS (First Come, First Served):
Equal Distribution
Description: Every winning Hunter receives the same number of tokens.
Configuration:
Total Winner: Total number of Hunters to receive rewards (default is 10).
Amount of Tokens for Each Winner on Top: The number of Tokens each winning Hunter receives.
Customize Reward Distribution (Tiered)
Description: Rewards are divided into tiers, with different token amounts for each tier.
Configuration:
Total Winner: Total number of Hunters to receive rewards (default is 10).
Top Winners: Specify the positions to receive rewards (starting from the highest, e.g., Top 1; tiers must be consecutive).
Reward for Each Winner: Tokens are awarded for each tier.
Note: You can add or remove tiers as needed.
π Leaderboard:
Leaderboard rewards are based on Hunter points. You have 3 options:
Top
Equal Distribution
Description: Each top-ranking Hunter receives the same number of tokens.
Configuration:
Total Winner: Total number of Hunters to receive rewards (default is 10).
Amount of Tokens for Each Winner on Top: The number of Tokens each top Hunter receives.
Customize Reward Distribution (Tiered)
Description: Rewards are divided into tiers with varying token amounts.
Configuration:
Total Winner: Total number of Hunters to receive rewards (default is 10).
Top Winners: Specify the consecutive top positions for rewards (starting from the highest).
Reward for Each Winner: Tokens are awarded per tier.
Note: Tiers can be adjusted as needed.
Random
Description: Rewards are distributed randomly to Hunters, regardless of ranking.
Configuration:
Total Winner: Total number of Hunters to receive rewards (default is 10).
Amount of Tokens for Each Winner on Random: Tokens each randomly selected Hunter receives.
Top and Random (Combined)
Description: Combines rewards for top-ranking Hunters with random rewards.
Configuration:
Total Winners: Total number of Hunters to receive rewards (default is 10).
For the Top Portion: Choose one of the following:
Equal Distribution:
Number of Winners Determined Based on Leaderboard Rankings: Number of top Hunters to reward.
Amount of Tokens for Each Winner on Top: The number of Tokens each top Hunter receives.
Customize Reward Distribution:
Top Winners: Specify consecutive top positions to receive rewards.
Reward for Each Winner: Tokens for each tier.
Note: Tiers can be added or removed as needed.
For the Random Portion:
Number of Winners Determined by Random: Number of Hunters to receive rewards randomly.
Amount of Tokens for Each Winner by Random: Tokens each randomly selected Hunter receives.
Note: The total number of rewarded Hunters from the Top and Random portions must equal the Total Winners configured.
π’ Total Reward
The system calculates and displays the total number of tokens required to fund the reward pool.
Once you have completed these steps, click Finish to finalize.
βοΈ Edit Quest
The ability to edit a Quest on DAC depends on its current status. Below are the editing rules and restrictions based on each stage of the quest lifecycle:
π Draft
You have full control over the Quest.
All information is editable, and you can also delete the Quest if needed.
π Scheduled
You can edit all quest content except for Step 4 (Rewards).
β Editable:
Setup: Title, Description, Tags, Avatar, Schedule, etc.
Tasks, Qualifications, and other details
π« Not Editable:
Step 4: Rewards (Chain, Token, Distribution, etc.)
Once the quest is scheduled, the reward configuration is locked to maintain consistency and fairness.
π Ongoing
In-progress quests can be updated up to three times.
β Editable:
Setup: Title, Description, Tags, Avatar, and End Date
Qualifications: All criteria can be adjusted
π« Not Editable:
Tasks and reward structures (Step 2 and Step 4)
β Completed
Quests marked as Completed are fully locked, meaning no further edits can be made β except for the Submit Proof task.
For quests that include a Submit Proof task:
Requesters can still review, approve, or reject submissions from Hunters after the quest ends.
Requesters have a 5-day review window to finalize decisions.
After 5 days, any pending submissions that have not been explicitly approved or rejected will be automatically rejected by the DAC system.
This ensures a fair and timely resolution for all participants while giving Requesters adequate time to review proof-based tasks.
π οΈ How to Edit a Quest
To modify a quest:
Navigate to your Quest list.
Click on the Quest you want to update.
In the Quest Details page, click βEditβ and begin making your changes (based on the allowed status rules above).
To edit a Quest, simply click on the Quest you wish to modify, then click on Edit in the Quest Details and start making your desired changes.
Last updated