How it works
Understanding the platform
How quests work on Signals.
A plain-language overview of what a quest is, how the flow works from start to finish, and the task types the product supports.
What a Signals quest is
A quest is a short set of tasks attached to a funded reward pool. A project creates the quest, participants complete the tasks, and the project decides who receives rewards when the quest ends.
Structured around tasks
Each quest is a small list of actions such as following on X, joining Telegram, joining Discord, posting with mentions, or visiting a website.
Backed by a reward pool
The project funds the quest before it runs, then rewards are claimed from that pool after the project finalizes the approved result.
Completed over time
Participants join, work through the task list, wait for the quest to end, and then claim only if they were selected for rewards.
How a quest works, end to end
1
A project launches
They set the tasks, dates, and how much the reward pool is worth. They fund the pool from their wallet. The contract is deployed on Arbitrum and the pool becomes visible to everyone.
2
The community participates
Each task uses the relevant provider flow. Participants complete the action, return to Signals, and the quest page updates when verification succeeds.
3
Winners get paid
The project reviews completions, finalizes the approved result, and participants claim from the quest page if included.
Supported task types
Every quest is a list of tasks. The task type determines the required provider connection and the verification prompt shown on the quest page.
X
Used when a quest includes X-based actions
How it works
X tasks use the linked X account and are checked against the rule configured by the quest creator.
Typical use
Supported examples include follow, like, repost, and post with mentions.
Verification note
For post with mentions, the submitted post must include the required text and the required number of mentions.
Telegram
Used when a quest includes Telegram community tasks
How it works
Telegram tasks require joining the configured group or channel and then returning to the quest page.
Typical use
Supported examples include group join and channel join.
Verification note
Signals checks the linked Telegram account against the configured group or channel.
Discord
Used when a quest includes Discord server or role checks
How it works
Discord tasks can check server membership or a required role after the participant returns to the quest page.
Typical use
Supported examples include server join and role ownership.
Verification note
The Discord account is connected to the quest identity before membership or role state is checked.
Website
Used for external links and simple off-platform destinations
How it works
Website tasks open an external destination from the quest page.
Typical use
Supported examples include opening a project page, product page, or community link.
Verification note
Website tasks are lighter than account-based tasks and are best used as part of a broader task set.
A few things worth knowing about the platform
Arbitrum One
Signals runs on Arbitrum One, an Ethereum layer-2 network. Gas costs a few cents per action. Rewards are distributed on Arbitrum. Participants and creators both need a small amount of ETH on Arbitrum for gas. The platform handles the network switching automatically.
Smart contracts hold the rewards
Every quest deploys its own reward contract on Arbitrum. The creator funds the reward pool before participation and finalizes the approved result after review.
Ready to try it?
Browse live quests to see the participant flow, or open the creator guide to launch a quest.