Start with a Conversation
Most campaigns kick off with a single message. Reach out to the Boost team with:- The protocol or asset you want to incentivize
- The goal — deeper liquidity, more holders, longer holds, retention boost, etc.
- Rough budget and timeline
- Any constraints — chains involved, eligibility rules, partner relationships
What We’ll Set Up Together
1. Indexer onboarding
If the protocol or asset you want to reward isn’t already supported, we extend our indexer to track it. This is the main reason early campaigns aren’t self-serve — our system needs to know how to read your contract events and how to measure each user’s position. You’ll bring:- Contract addresses
- Chain(s) to index
- Token standards involved (ERC20, ERC1155, etc.)
- How position size should be measured (token balance, USD value, LP share, etc.)
2. Campaign design
The shape of the campaign — who earns, how much, for how long. We’ll work through these decisions together:| Decision | What it controls |
|---|---|
| Targets | Which positions count toward rewards |
| Eligibility | Who can earn — open, allowlist, or verification-gated |
| Modes | Stackable rules that shape reward math (caps, tiers, snapshots, fixed APY) |
| Reward token | What you’re paying out |
| Total budget | The reward pool size |
| Duration | Start and end times |
Think through your design first
Read up on campaign modes to see what the reward math can do. You’ll come into the conversation with a clearer picture of what’s possible.
3. Deployment
Once the design is locked, we deploy:- The campaign config is hashed and committed
- The on-chain campaign contract is created from your funded budget
- Indexing begins; accruals start at the campaign’s start time
startTime.
After Launch
- End early if priorities shift — already-accrued rewards remain claimable
- Watch it run on rabbithole.gg, where TVL, participants, and live leaderboard stats are surfaced