Skip to main content
The Boost V2 Docs are under active development and will be subject to changes.

Deploying a Boost

This guide walks you through the steps to deploy a boost: selecting your action, choosing a budget and token, configuring rewards, and launching your campaign.

Step 1: Select Your Action

Before configuring rewards, choose which action to incentivize.
1

Choose an Approved Action

Select from your approved actions. Only actions that have passed review can be used for boosts.If you don’t have an approved action yet, you’ll need to set one up first.
2

Verify the Action Details

Review the action configuration to make sure it targets the right activity:
  • Contract and event being monitored
  • Who receives rewards (the claimant)
  • Any filters applied to qualifying transactions

Step 2: Choose Your Budget

Select the budget account that will fund this boost and set your spend limit.

Selecting a Budget Account

Choose from budget accounts where you have Admin or Manager access. Make sure the account:
  • Is on the chain where you want to run the campaign
  • Has sufficient token balance for your planned rewards

Understanding Protocol Fees

Boost charges a 10% protocol fee on all rewards distributed. This fee is automatically added to your spend limit when you deploy.
When you set a spend limit, the protocol fee is calculated on top:
You SetProtocol Fee (10%)Total Required
1,000 tokens100 tokens1,100 tokens
5,000 tokens500 tokens5,500 tokens
10,000 tokens1,000 tokens11,000 tokens
Example: If you want to distribute 1,000 USDC in rewards, you’ll need 1,100 USDC in your budget account (1,000 for rewards + 100 for fees).
The fee is only charged on rewards that are actually claimed. If you end a campaign early and withdraw unused funds, you only pay fees on what was distributed.

Step 3: Select Your Reward Token

Choose which token to distribute as rewards.

Token Whitelist

Only whitelisted tokens can be used for boost rewards. This protects users from receiving spam tokens or malicious contracts.
The token whitelist includes popular, verified tokens on each supported chain. If you don’t see your token:
  1. Check what’s available in the token dropdown when deploying
  2. Request a new token by contacting the Boost team on Discord
When requesting a token, provide:
  • Token contract address
  • Chain (Base, Optimism, etc.)
  • Token name and symbol
  • Brief description of why you need it
Token requests are typically reviewed within 24-48 hours. Plan ahead if you need a specific token for your campaign.

Step 4: Configure Rewards

Choose how much to reward participants. Boost supports two reward types:
Everyone who qualifies receives the same token amount.You configure:
  • Reward Amount: Number of tokens per claim (e.g., 10 USDC per mint)
  • Spend Limit: Maximum tokens to distribute before the boost ends
Example:
  • Reward: 50 tokens per action
  • Spend limit: 5,000 tokens
  • Result: Up to 100 people can claim (5,000 ÷ 50)
Best for: Simple campaigns where all participants should be treated equally.

Choosing the Right Reward Amount

Consider these factors when setting rewards:
  • Action difficulty: Harder or higher-commitment actions warrant larger rewards
  • Target audience: New users may need more incentive than existing users
  • Competition: Check what similar campaigns are offering
  • Your budget: Start conservative and top up if the campaign performs well

Step 5: Configure Allowlists (Optional)

Allowlists restrict who can claim rewards to a specific set of addresses.

When to Use Allowlists

Use Allowlists When

  • Targeting a specific community or holder group
  • Running exclusive campaigns for partners
  • Preventing bot/sybil farming
  • Rewarding existing users only

Skip Allowlists When

  • You want maximum reach and participation
  • Running open acquisition campaigns
  • The action itself is restrictive enough
  • You want organic discovery

Allowlist Tradeoffs

ApproachProsCons
With AllowlistTargeted distribution, reduced farming risk, predictable audienceLimited reach, requires maintaining address list, may miss organic users
Without AllowlistMaximum participation, organic growth, simpler setupHigher farming risk, less predictable costs, may attract non-target users

Setting Up an Allowlist

1

Prepare Your Address List

Create a list of wallet addresses that should be eligible. Common sources:
  • NFT holders (snapshot of a collection)
  • Token holders above a threshold
  • Previous campaign participants
  • Partner community members
2

Upload the List

Upload your address list when configuring the boost. The system will validate the addresses.
3

Verify Coverage

Check that your allowlist covers your intended audience. You can update the list later if needed.
Start without an allowlist to gauge organic interest, then add one if you see farming behavior.

Step 6: Review and Deploy

Before launching, verify your configuration:
1

Check the Activity Preview

The preview shows recent transactions that would qualify for rewards. Verify:
  • The right transactions are being captured
  • Claimant addresses look correct
  • Reward amounts match your expectations
2

Review Total Costs

Confirm your total budget including the 10% protocol fee:
ItemAmount
Spend LimitYour configured amount
Protocol Fee (10%)Added automatically
Total RequiredMust be in your budget account
3

Deploy

Click “Deploy Boost” and approve the transaction. On supported chains (Base, Optimism, Celo, World Chain), the transaction is sponsored—no gas needed.

After Deployment

Once live, your boost will:
  • Start accepting claims immediately
  • Show up in your dashboard for monitoring
  • Distribute rewards as users complete the action

Managing Boosts

Monitor performance, top up budget, or end campaigns.

Quick Reference

SettingFixed RewardsVariable Rewards
RewardToken amount per claimPercentage of tx value
CapN/A (fixed amount)Max reward per claim
Best forEqual treatmentScaling with activity
PredictabilityHighMedium

Troubleshooting

You need to create and get an action approved before deploying a boost. See Setting up an Action.
Remember to account for the 10% protocol fee. If your spend limit is 1,000 tokens, you need 1,100 tokens in your budget.
Only whitelisted tokens are available. Request your token on Discord with the contract address and chain.
This could mean your action parameters are too restrictive, or no matching transactions have occurred recently. This doesn’t prevent deployment—new qualifying transactions will be captured once you’re live.
Start without one unless you have a specific audience in mind. You can always create a new boost with an allowlist if you see unwanted behavior.