π€Automated Claims
Token rewards normally sit as claim checks until someone submits a transaction. Automated Claims closes that loop for you: on a schedule you set, Fuul submits the claim transactions for your users and sponsors the gas, so recipients receive tokens without doing anything.
Tokens settle directly to the recipient in each claim check. Fuul never takes custody of your funds at any point in the process.
Three ways tokens reach a wallet
Automated Claims is one of three options. They are not exclusive, and most programs use more than one:
User claims
The end user
The end user
Default. Users who are already onchain-native
Claim on behalf
Your project, ad hoc
Your project
One-off pushes, a campaign wrap-up, VIP users
Automated Claims
Fuul, on a schedule
Fuul, billed back to you
Ongoing programs where you want claiming to disappear as a user step
Claim checks do not distribute automatically unless one of these is in place. A common misconception is that payouts are pushed to wallets by default. They are not: a reward becomes a claim check, and a claim check needs a transaction.
How it works
Your project opts in and Fuul approves it
You set a cadence, plus a day of the week for weekly runs
On each scheduled run, Fuul collects the project's available claim checks, batches them into claim transactions, and submits them onchain
Each run records which users were claimed for, the per-currency amounts distributed, and what the run cost
Automated Claims sits on top of the existing claim pipeline. It does not change how payouts or claim checks are created, only how they get redeemed. See Types of Rewards for how claim checks are generated in the first place.
Configuration
Projects configure this from the Automated Claims Hub, at Activity β Reward Payouts β Automate claims.
Master toggle
Turns automated claiming on or off for the project
Cadence
How often runs happen. Weekly runs also take a day of the week
Native fee cap
Upper bound on native token spend per run, so a single run cannot exceed your budget
The Hub also shows metric cards and a paginated run history, with the claim batches for each run.
Enabling the toggle is not sufficient on its own. A run executes only once the project is both enabled and approved by Fuul. Contact ecosystem@fuul.xyz to get set up.
Costs
Fuul sponsors two things per transaction: the network gas, and the protocol's nativeUserClaimFee. Both are metered per run, converted to USD, and accumulated into a monthly per-project total for billing and reconciliation.
Your native_fee_cap bounds native spend per run. If a run would exceed it, it stops at the cap rather than continuing.
Availability and limitations
Networks
EVM only
Per-currency caps
Not available. The cap applies to native spend per run, not to how much of any given reward currency goes out
Cost reporting
Run cost is shown as a single combined figure. Gas and the protocol fee are not broken out separately in the UI
If your program pays on a chain where no project has run the relayer before, treat it as a first-time enablement rather than a toggle. Confirm timing with the Fuul team before committing a launch date to your users.
Related
How claim checks are created and what the voucher model buys you β Types of Rewards
Keeping the pool funded so runs don't fail β Budgets & Smart Contracts and Rewards Pool Budget Alerts
Building your own claim button instead β Claim Flow Integration
Last updated