Mission layers
| Layer | Rhythm | What it is meant to do |
|---|---|---|
| Daily | 24 hours | Build habit loops around briefings, discovery, and wallet check-ins |
| Weekly | 7 days | Push deeper research, Base scans, and portfolio maintenance |
| Seasonal | 4 to 8 weeks | Run larger campaigns tied to the /earn system and token distribution |
| Ecosystem | Event-driven | Support partner launches, protocol quests, and community activations |
What missions can reward
- RP movement and leaderboard position
- Reputation tiers and early-access status
- Eligibility signals for seasonal claims
- Premium feature boosts or higher-priority agent actions
- Partner rewards tied to Base ecosystem activity
What counts as meaningful participation
- Starting and finishing real research loops with Risa
- Connecting a wallet and revisiting the same thesis over time
- Completing on-chain tasks on Base
- Inviting high-quality users who stay active
- Sharing useful feedback, bug reports, or ecosystem insights
Guardrails
Quality over spam
The system should favor repeatable, useful actions over shallow click farming.Product plus on-chain together
A good mission system should not depend only on tweets or only on swaps. The strongest signal comes from combining in-product behavior with verifiable Base activity.Anti-sybil by design
Low-effort loops should carry less weight than actions that create cost, time, or context continuity.How this connects to the rest of the stack
- AI agents provide the task-specific depth
- RISA on Base provides the token layer
- RISA airdrop provides the live /earn and referral logic
The mission engine is meant to reward people who use Risa well, not just people who farm whichever task looks easiest.