- Retrieve the Boost you want to claim from
- Prepare the claim data payload
- Execute the claim transaction
/signatures endpoint to generate the signature payload,
otherwise you will need to build the payload yourself.
The default validator will be always be used by default unless you specify your own validator on boost creation.
- Using the Default Validator
- Using Your Own Validator
In order to claim an incentive from a boost using the default validator, you will need to generate a valid signature payload.
You can do this by calling the boost api This example assumes you have already instantiated a The You can also claim on behalf of another user by using the 
/signatures endpoint and passing in the boostID and txHash.You can also generate a signature by providing a wallet address instead of a transaction hash using the 
/transactions endpoint.
See Fetching Signature by Address for details.BoostCore client and have a valid transaction hash for the action that the claimant completed.Claim Signature API
See additional documentation on how to build a claim signature
Generate the Signature Payload
/signatures endpoint will return an array of signatures, one for each available incentive on the boost.
Each item in the array will contain the following fields:- signature: The signature to be used in the claim transaction
- incentiveId: The id of the incentive being claimed
- claimant: The address of the claimant
ERC20VariableIncentive or ERC20VariableCriteriaIncentive, you will need to pass in the rewardAmount as claimData to the /signatures endpoint.Here’s an example of how you would accomplish that with multiple incentives.Claiming the incentives
Once you have a valid response from the/signatures endpoint, you can loop through the response and claim the incentives.index.ts
claimIncentive must be called by the claimant. This is useful if you have access to the claimants wallet, like in the case of a dapp.
If you are claiming on behalf of another user, you must use claimIncentiveFor.claimIncentiveFor method.