web3.newbeta
by
← Protocols
Boost.xyz
Identity / Names·EVM · Multi-chain

Boost.xyz

[ Docs ][ llms.txt ][ llms-full.txt ][ github.com/boostxyz/boost-protocol ]
01Description

Permissionless onchain incentive protocol. Sponsors fund Boosts (smart contracts) that pay rewards when users complete verifiable onchain actions.

02Best for
  • 01onchain incentive campaigns
  • 02swap/mint/stake reward bounties
  • 03growth-engine bootstrapping
  • 04no-code reward escrows
  • 05sponsor-funded user acquisition
03Install
  • pnpm add @boostxyz/sdk viem
04Environment variables
VariableScopeDescription
NEXT_PUBLIC_BOOST_CHAIN_IDClientTarget chain for Boost contracts (Base 8453, Optimism 10, Arbitrum 42161).
BOOST_DEPLOYER_PRIVATE_KEYServerServer-side signer used to deploy Boosts and fund budgets (never expose).
BOOST_API_KEYServerOptional Boost API key for indexed reads of campaigns/claims.
05Prompt snippet
Use Boost.xyz to launch onchain incentives. Install `@boostxyz/sdk` (TypeScript, viem-based) and instantiate `BoostCore` and `BoostRegistry` clients pointing at the chain's deployed contracts. Create a Boost with `boostCore.createBoost({ budget, action, validator, allowList, incentives, ... })` where `action` = a `EventAction` referencing the contract+event signature you want to reward, and `validator` = `SignerValidator` (offchain signed) or onchain validator. Fund the `ManagedBudget` with ERC20/ETH, then users claim via `boostCore.claimIncentive(boostId, incentiveId, claimant, claimData)`. For reads, hit the Boost API at `https://api.boost.xyz` with `BOOST_API_KEY`.
06Gotchas
  • ⚑Protocol is in active development — pin SDK and contract addresses; breaking changes ship between minor versions.
  • ⚑Each Boost is its own smart contract — deployment costs gas; batch incentives instead of creating many micro-Boosts.
  • ⚑`SignerValidator` requires you to custody an offchain signer key; loss of that key bricks claims for the Boost.
  • ⚑AllowList and per-claimant caps are enforced onchain — misconfigured caps can lock unclaimed budget; plan a `clawback` admin path.
  • ⚑Sybil resistance is your responsibility — combine with Galxe Passport, Gitcoin Passport, or Worldcoin proofs in your validator.
  • ⚑Chain coverage is currently Base, Optimism, Arbitrum, and select EVM L2s — verify deployment addresses before targeting a new chain.
07Alternatives
GalxeLayer3ZealyQuestNGuild.xyz