Getting started
Signals basics
Getting started
Signals offers quests and campaigns that help projects grow their communities, while giving users a way to earn rewards by supporting the projects they care about.
Primary routes
Signals has two main workflows: participating in quests and creating quests.
Participant documentation
Participant
Covers quest participation, task completion, reward claims, and participant support flows.
Open sectionCreator documentation
Creator
Covers quest setup, deployment, funding, review, finalization, and claim operations.
Open sectionPrerequisites
Both workflows rely on the same small set of prerequisites.
An Ethereum-compatible wallet
A wallet is required to connect to the app and sign actions when required.
Arbitrum One
Signals runs on Arbitrum One. The site prompts a network switch when needed.
An X account
X is used as the primary quest identity check and for X-based task verification.
A short setup window
Initial setup is brief. Subsequent participation or launch cycles are shorter once the required accounts are linked.
Participant flow
1
Quest page
The quest page displays the project, reward pool, deadline, and task set.
2
Join step
Initial participation includes any required account connection and a wallet signature.
3
Task completion
Each task opens the target platform and verifies after return to Signals.
4
Review phase
After the quest deadline, the project reviews the eligible participant set.
5
Claim phase
Selected participants claim rewards from the quest page through a single transaction.
Creator flow
1
Configuration
Quest creation begins in the dashboard with the quest configuration form.
2
Core fields
Name, logo, dates, reward token, and total reward pool define the baseline quest structure.
3
Task setup
Tasks are added from the supported providers and any required channel setup is completed at this stage.
4
Deployment and funding
Deployment publishes the quest and funding activates it for participant access.
5
Review and finalization
Completed submissions are reviewed and the final reward set is published at the end of the quest.
Core terms
The following terms appear repeatedly across the documentation set.
Quest
A reward-backed task set created by a project.
Task
A required action in a quest, such as following on X, joining Telegram, joining Discord, posting with mentions, or visiting a website.
Creator / owner
The wallet that launches, funds, reviews, and finalizes a quest.
Participant
A wallet completing the quest task set.
Reward pool
The USDC, USDT, or WETH amount funded for a quest.
Finalize
The end-of-quest step that confirms the approved reward list.
Claim
The participant action that receives an approved reward from the quest page.
Arbitrum One
The network used for quest deployment, funding, finalization, and claims.
One more click
Continue in the relevant workflow section: participate or create.