Incentive Distribution
Incentive distribution platforms evaluated on whether an outsider can recompute a disputed allocation, who holds the budget and can still edit the list after publication, what has already gone wrong on the machinery, and what is written down about sybil defence.
17providers tracked
8ranked (methodology v2026.11.1)
12 November 2026Ranking snapshot
28 October 2026oldest read · due 12 DecIndependent. Evidence-based.We rank with a published method and sourced evidence. No one can pay to rank.How it works
Set your country and amount to see your costs ·
Your setup
What your country changes
Pick a country to see which incentive distribution platforms serve it. Nothing is hidden — any that does not is listed with that reason.- 🇺🇸 United States
- 🇨🇦 Canada
- 🇲🇽 Mexico
- 🇬🇧 United Kingdom
- 🇩🇪 Germany
- 🇫🇷 France
- 🇮🇹 Italy
- 🇪🇸 Spain
- 🇳🇱 Netherlands
- 🇨🇭 Switzerland
- 🇸🇪 Sweden
- 🇳🇴 Norway
This affects provider availability.
Requirements (0)
Preferences (0)
Preferences re-weight Fit for you, which needs your country.
More filters
Funding & access
8 providers match your requirements
Out of 8 ranked providers. 0 excluded.
What this ranks
Ranked here: incentive distribution platforms that run a token or points programme for the budget-holder who signs for it, judged on whether anyone outside the vendor can recompute an allocation.Not ranked here: components and streaming primitives that only move tokens the buyer has already decided to move, personhood providers, detection-only sybil scoring and products that pivoted away.8 of the 17 assessed are ranked; 9 were turned away by name. Who, and whyRequirements narrow the list; they never change a published ChainChoice Score. How the ranking works
Merkl (Angle Labs)
How Merkl (Angle Labs) was chosen
Leads this ranking on If someone disputes their number, can anyone outside the vendor recompute it?Offchain reward engine
81 / 100 out of 100published score, #1 of all 8 worldwide
Evidence
High
4/4 criteria scored, with 4 dated sources quoted.Recomputable allocationBudget control after publicationIncident and operator record
Why it leads
- Merkl (Angle Labs) is 3 points ahead of Sablier Airdrops (Merkle Lockups), mainly because it scores higher on its recomputable allocation and its incident and operator record.
- Best in this ranking on recomputable allocation and incident and operator record
- Ahead of Sablier Airdrops (Merkle Lockups) on recomputable allocation (+5.6 points) and incident and operator record (+1.4 points)
Tradeoff
Budget control after publication: 2 points below the best in this ranking
Share
#ProviderPriceCompare
2
A pure claim rail
78 / 100 out of 100
3
Onchain incentive protocol from Boost Studios...
71 / 100 out of 100
4
Solana-only distribution rail
70 / 100 out of 100
5
HE
A free, self-service onchain distribution rail...
69 / 100 out of 100
6
GA
The volume incumbent
59 / 100 out of 100
7
LA
No-code Activation builder
57 / 100 out of 100
8
Quest and leaderboard engine
51 / 100 out of 100
Compare providers (0)
See key differences in features, fees, security and more.
Budget control after publication
Who is holding my budget, who can still change the list, and what comes back to me?
28% of the published criteria weight. Scored 0–10 from the published evidence; the order below is by this criterion, then the published ranking.
| Provider | Budget control after publication (0–10) | ChainChoice Score |
|---|---|---|
| Sablier Airdrops (Merkle Lockups) | 10 | 78 |
| Merkl (Angle Labs) | 8 | 81 |
| Boost (Rabbithole) | 8 | 71 |
| Hedgey | 8 | 69 |
| Streamflow | 7 | 70 |
| Galxe Quest / Business+ | 5 | 59 |
| Layer3 | 5 | 57 |
| Zealy | 4 | 51 |
Incident and operator record
What has already gone wrong on this machinery, and who is actually running it today?
22% of the published criteria weight. Scored 0–10 from the published evidence; the order below is by this criterion, then the published ranking.
| Provider | Incident and operator record (0–10) | ChainChoice Score |
|---|---|---|
| Merkl (Angle Labs) | 8 | 81 |
| Sablier Airdrops (Merkle Lockups) | 7 | 78 |
| Galxe Quest / Business+ | 7 | 59 |
| Streamflow | 6 | 70 |
| Layer3 | 6 | 57 |
| Boost (Rabbithole) | 5 | 71 |
| Zealy | 5 | 51 |
| Hedgey | 4 | 69 |
Recomputable allocation
If someone disputes their number, can anyone outside the vendor recompute it?
30% of the published criteria weight. Scored 0–10 from the published evidence; the order below is by this criterion, then the published ranking.
| Provider | Recomputable allocation (0–10) | ChainChoice Score |
|---|---|---|
| Merkl (Angle Labs) | 9 | 81 |
| Sablier Airdrops (Merkle Lockups) | 6 | 78 |
| Boost (Rabbithole) | 6 | 71 |
| Streamflow | 6 | 70 |
| Hedgey | 6 | 69 |
| Galxe Quest / Business+ | 2 | 59 |
| Layer3 | 2 | 57 |
| Zealy | 1 | 51 |
Sybil defence in writing
What exactly stops a farm from eating this budget, and what happens when it flags the wrong person?
20% of the published criteria weight. Scored 0–10 from the published evidence; the order below is by this criterion, then the published ranking.
| Provider | Sybil defence in writing (0–10) | ChainChoice Score |
|---|---|---|
| Merkl (Angle Labs) | 8 | 81 |
| Sablier Airdrops (Merkle Lockups) | 8 | 78 |
| Boost (Rabbithole) | 8 | 71 |
| Streamflow | 7 | 70 |
| Hedgey | 7 | 69 |
| Galxe Quest / Business+ | 6 | 59 |
| Layer3 | 6 | 57 |
| Zealy | 5 | 51 |
All 4 published criteria
Every ranked row’s score on each criterion, in the published order. Choose a column to order by it.
| Provider | ChainChoice Score | |||||
|---|---|---|---|---|---|---|
| 1 | Merkl (Angle Labs) | 9 | 8 | 8 | 8 | 81 |
| 2 | Sablier Airdrops (Merkle Lockups) | 6 | 10 | 7 | 8 | 78 |
| 3 | Boost (Rabbithole) | 6 | 8 | 5 | 8 | 71 |
| 4 | Streamflow | 6 | 7 | 6 | 7 | 70 |
| 5 | Hedgey | 6 | 8 | 4 | 7 | 69 |
| 6 | Galxe Quest / Business+ | 2 | 5 | 7 | 6 | 59 |
| 7 | Layer3 | 2 | 5 | 6 | 6 | 57 |
| 8 | Zealy | 1 | 4 | 5 | 5 | 51 |
How this ranking works
How firm the #1 is, the per-criterion arithmetic behind each score, who pays ChainChoice, and which incentive distribution were assessed and left out.
FirmThis verdict holds under every one-point re-read
See the arithmetic
Every published criterion was moved up and down by one point and the ranking re-run. The same product came first each time. The published rankings file
Why this score4 published criteria · leads 3 of 4
Published criterionWtScore, and the best hereGap/10 out of 10Pts
If someone disputes their number, can anyone outside the vendor recompute it?7.2·98.6
Who is holding my budget, who can still change the list, and what comes back to me?6.7−287.2
What has already gone wrong on this machinery, and who is actually running it today?5.3·85.6
What exactly stops a farm from eating this budget, and what happens when it flags the wrong person?4.8·85.1
Σ methodology points26.6/32
Each bar is the score on that criterion’s own 0–10 scale, never rescaled to the pool. The dark line is the best any product here reached on that axis. Wt is the most the criterion can add to the 86-point weighted total. Pts is weight × score × 32; the sum is the methodology score, and each weighted point behind the leader costs 2.6 on the displayed score. how these are weighted
Why it ranks first
Why Merkl (Angle Labs) leads this category right now
Offchain reward engine that publishes a per-recipient reward file for every merkle root it pushes to a named Distributor contract, opens a 1-2 hour onchain dispute window before rewards become claimable, and takes its 3% out of the deposited budget rather than on top of it. Strongest on “If someone disputes their number, can anyone outside the vendor recompute it?” (9/10): Merkl publishes each reward file on its status page "so anyone can audit past distributions" and documents "a security window of 1-2 hours following each reward update during which anyone can contest reward allocations made by the Merkl engine". The production engine is closed source. Weakest on “Who is holding my budget, who can still change the list, and what comes back to me?” (8/10): Merkl's campaign-management page states that a campaign manager can "reallocate unclaimed rewards from any recipient address to another address at your discretion" and that the window "ranges from 1 day to 1 year post-campaign". The power is stated in plain language, with no contract-level role reference. Published price: READ ON https://docs.merkl.xyz/distribute-with-merkl/fee-model (fetched 2026-11-10, HTTP 200): "Merkl's fees are deducted from the campaign budget when the campaign starts.
Best for
Recomputable allocation — 9/10
Main tradeoff
The friendly docs page and the Terms PDF do not say the same thing about your leftover budget. docs.merkl.xyz/distribute-with-merkl/fee-model tells you 'Campaign creators on Merkl can freely reallocate all unclaimed rewards once their campaign ends'; Art. 4 of merkl-terms.pdf (last revised 13 May 2026) says that if you have not reallocated within a year, 'Angle Labs reserves the right, at its sole discretion, to recover such unclaimed rewards in whole or in part and to reallocate, redistribute, or otherwise apply them as Angle Labs sees fit, including by reallocating them to other Merkl Campaigns, to other Recipients, to operational reserves', and 'The Incentivizor expressly waives any right to claim, recover, or be reimbursed'. Pair that with Art. 3.3 — Merkl may 'pause, suspend, modify, refuse, terminate' a live campaign at sole discretion 'with or without prior notice' — Art. 5.4, which routes every aggrieved recipient's miscalculation claim to you with an indemnity running back to Angle Labs, and Art. 6, which caps Angle Labs' liability at three months of your fees. A budget-holder who read only the docs will not have priced any of that; the one operational chore that prevents the worst of it is a calendar reminder to reallocate unclaimed rewards inside twelve months.
Verify before signup
READ ON https://
Recommendation summary
What should decide this category
If someone disputes their allocation, can anyone outside the vendor recompute it?
Between funding and claiming, who holds the budget, and who can still change the list?
What has already gone wrong on this machinery, and does the vendor say so on a page it controls?
Quick picks
Strong options in this category
Start with the lead choice first, then use the shortlist only if you still need a challenger or stronger fit for a specific setup.
Best overall
Merkl (Angle Labs)
Offchain reward engine that publishes a per-recipient reward file for every merkle root it pushes to a named Distributor contract, opens a 1-2 hour onchain dispute window before rewards become claimable, and takes its 3% out of the deposited budget rather than on top of it.
Offchain reward engine that publishes a per-recipient reward file for every merkle root it pushes to a named Distributor contract, opens a 1-2 hour onchain dispute window before rewards become claimable, and takes its 3% out of the deposited budget rather than on top of it. Strongest on “If someone disputes their number, can anyone outside the vendor recompute it?” (9/10): Merkl publishes each reward file on its status page "so anyone can audit past distributions" and documents "a security window of 1-2 hours following each reward update during which anyone can contest reward allocations made by the Merkl engine". The production engine is closed source. Weakest on “Who is holding my budget, who can still change the list, and what comes back to me?” (8/10): Merkl's campaign-management page states that a campaign manager can "reallocate unclaimed rewards from any recipient address to another address at your discretion" and that the window "ranges from 1 day to 1 year post-campaign". The power is stated in plain language, with no contract-level role reference. Published price: READ ON https://docs.merkl.xyz/distribute-with-merkl/fee-model (fetched 2026-11-10, HTTP 200): "Merkl's fees are deducted from the campaign budget when the campaign starts.
Best for: Recomputable allocation — 9/10
If someone disputes their number, can anyone outside the vendor recompute it? · weight 30%9/10Who is holding my budget, who can still change the list, and what comes back to me? · weight 28%8/10What has already gone wrong on this machinery, and who is actually running it today? · weight 22%8/10What exactly stops a farm from eating this budget, and what happens when it flags the wrong person? · weight 20%8/10
Quick pick
Sablier Airdrops (Merkle Lockups)
A pure claim rail: the budget-holder uploads a CSV of [address, amount] pairs, Sablier builds a merkle tree, pins the full recipient list to IPFS and deploys an immutable-root campaign contract the buyer alone administers — it computes no allocation and publishes nothing about sybil defence, and as of 2026-07-13 Sablier Labs has stopped active development and funds maintenance only through June 2028.
A pure claim rail: the budget-holder uploads a CSV of [address, amount] pairs, Sablier builds a merkle tree, pins the full recipient list to IPFS and deploys an immutable-root campaign contract the buyer alone administers — it computes no allocation and publishes nothing about sybil defence, and as of 2026-07-13 Sablier Labs has stopped active development and funds maintenance only through June 2028. Strongest on “Who is holding my budget, who can still change the list, and what comes back to me?” (10/10): Sablier's airdrop docs state: "If a recipient doesn't claim their airdrop, it's not created, and you remain in full control over their allocation." The grace period "ends 7 days after the first claim is made", and the campaign admin can "clawback the forfeited tokens after the campaign expires". Weakest on “If someone disputes their number, can anyone outside the vendor recompute it?” (6/10): Sablier "stores only the tree's root hash in the deployed Airstream contract, while the complete tree and recipient list reside in IPFS". A recipient can check a proof against the root; the list itself is the buyer's own file, drawn up off chain. Published price: From https://sablier.com/pricing (fetched 2026-11-10, HTTP 200): "You only pay when something happens onchain." Withdraw from stream: "the submitting wallet pays about $0.99 in the chain's native token (for example, ETH)" (recipient $0.99, sender Free).
Best for: Budget control after publication — 10/10
If someone disputes their number, can anyone outside the vendor recompute it? · weight 30%6/10Who is holding my budget, who can still change the list, and what comes back to me? · weight 28%10/10What has already gone wrong on this machinery, and who is actually running it today? · weight 22%7/10What exactly stops a farm from eating this budget, and what happens when it flags the wrong person? · weight 20%8/10
Quick pick
Boost (Rabbithole)
Onchain incentive protocol from Boost Studios Inc (formerly RabbitHole) where the budget sits in a named ManagedBudget contract the buyer owns and eligibility is set as inspectable, buyer-configured filters and onchain allowlists — but no reward file, no dispute window, no appeal path and no security page are published anywhere in its 104-page documentation corpus.
Onchain incentive protocol from Boost Studios Inc (formerly RabbitHole) where the budget sits in a named ManagedBudget contract the buyer owns and eligibility is set as inspectable, buyer-configured filters and onchain allowlists — but no reward file, no dispute window, no appeal path and no security page are published anywhere in its 104-page documentation corpus. Strongest on “Who is holding my budget, who can still change the list, and what comes back to me?” (8/10): Boost's campaign lifecycle page states that once a campaign launches "the rules are locked", that anything unclaimed "becomes recoverable by the creator through the same withdraw flow", and that "Creators (or the protocol admin in emergencies) can end a campaign before its scheduled `endTime`". Weakest on “What has already gone wrong on this machinery, and who is actually running it today?” (5/10): Boost's docs say "Funds are held in audited smart contracts" and name the `ManagedBudgetWithFeesV2` budget contract. The documentation index lists no security page, no audit report and no incident page, so the record is neither shown clean nor shown otherwise. Published price: From https://docs.boost.xyz/v2/documentation/support/faqs.md, 'What does it cost?' (fetched 2026-11-10, HTTP 200): "Boost charges a 10% protocol fee on rewards distributed through One-Time Actions.
Best for: Budget control after publication — 8/10
If someone disputes their number, can anyone outside the vendor recompute it? · weight 30%6/10Who is holding my budget, who can still change the list, and what comes back to me? · weight 28%8/10What has already gone wrong on this machinery, and who is actually running it today? · weight 22%5/10What exactly stops a farm from eating this budget, and what happens when it flags the wrong person? · weight 20%8/10
Quick pick
Streamflow
Solana-only distribution rail that takes the buyer's own CSV, publishes a merkle root on chain via an open-sourced SDK and IDL, and hands the campaign creator per-recipient cancellation, clawback and admin transfer — with the semantics documented in a package README rather than in the help centre a budget-holder would read.
Solana-only distribution rail that takes the buyer's own CSV, publishes a merkle root on chain via an open-sourced SDK and IDL, and hands the campaign creator per-recipient cancellation, clawback and admin transfer — with the semantics documented in a package README rather than in the help centre a budget-holder would read. Strongest on “Who is holding my budget, who can still change the list, and what comes back to me?” (7/10): Streamflow's distributor SDK states the clawback rules: "only Sender can clawback funds before Airdrop has ended" and "anyone can clawback funds a day after Airdrop has ended - funds will still go to the original Sender". Whether the sender can close single claims is a campaign setting. Weakest on “If someone disputes their number, can anyone outside the vendor recompute it?” (6/10): Streamflow's SDK README shows a merkle root and a per-claimant proof ("Merkle Proof used to verify claim") and says "all the data is stored on-chain". The tree comes from Streamflow's public API or the buyer's own build; the inputs behind the list are not published. Published price: From https://docs.streamflow.finance/en/articles/9675153-individual-vs-business-costs-of-using-streamflow (fetched 2026-11-10, HTTP 200): "All features (vesting, token locks, airdrops and staking pools) are available to everyone, with no limits, at the fees…
Best for: Budget control after publication — 7/10
If someone disputes their number, can anyone outside the vendor recompute it? · weight 30%6/10Who is holding my budget, who can still change the list, and what comes back to me? · weight 28%7/10What has already gone wrong on this machinery, and who is actually running it today? · weight 22%6/10What exactly stops a farm from eating this budget, and what happens when it flags the wrong person? · weight 20%7/10
Considered and not ranked
9 products we looked at and left out
A shortlist is only honest if it says who it turned away. Each of these was assessed against the same published criteria as the ranked table and excluded for a stated reason — not overlooked.
We assessed 17 products here and rank 8 — 47% of what we looked at. That share is of the products we assessed, not of the category: how many exist is not something we can count, so we do not claim a number for it.
Absinthe Labs· No longer operatingRoyco (and its Sonar incentive-market product)TurtleDisperseSuperfluidTrueFi pointsRabbithole as a separate pool entryGalxe Passport, Human Passport, World ID and other personhood providers· Ranked elsewhereTrusta Labs, Nansen sybil scoring and other detection-only vendors
What this ranking does not assess
- Liveness failure: the operator stops, censors you or loses data.
- Exit failure: you cannot get out at par, on time, or with what is yours.
These can still cost you money here; the ranking does not measure them, so a high place says nothing about them. Which criterion scores each family, and why the others do not apply, is in /data/risk-coverage.json.
How this ranking is built
Ranked on four questions
- If someone disputes their number, can anyone outside the vendor recompute it? · 30%
- Who is holding my budget, who can still change the list, and what comes back to me? · 28%
- What has already gone wrong on this machinery, and who is actually running it today? · 22%
- What exactly stops a farm from eating this budget, and what happens when it flags the wrong person? · 20%
Data checked Nov 2026 · Independent rankings · We show our work
How this page is reviewed
Reviewed means every product ranked on this page was read against its sources on or after that date; every ranked category is re-read at least every 45 days. Models research, extract and parse. A deterministic engine ranks. Every quote passes an adversarial refute pass.
Accountable for this review: Mathias Siemonsmeier, Founder.
How we review · Review calendar · Corrections log · How we make money
Direct answer
What is the best incentive distribution platform in 2026?
Merkl (Angle Labs) ranks #1 overall for incentive distribution on ChainChoice. Offchain reward engine that publishes a per-recipient reward file for every merkle root it pushes to a named Distributor contract, opens a 1-2 hour onchain dispute window before rewards become claimable, and takes its 3% out of the deposited budget rather than on top of it. It holds that rank under an affiliate-blind methodology scored across 4 published, weighted criteria — the code that ranks providers physically cannot read affiliate payouts (CI-enforced), so a payout can't move a rank. The verdict re-computes on every fee change, incident, or regulatory action; the full reasoning and the audit receipt are under Methodology.
How you can lose money here, and what the ranking scores
- Contract failure: the code holding the funds is exploited.Scored by What has already gone wrong on this machinery, and who is actually running it today? · 22% (Merkl (Angle Labs) 8/10, Sablier Airdrops (Merkle Lockups) 7/10, Boost (Rabbithole) 5/10)
- Custody failure: whoever holds the assets loses or withholds them.Scored by Who is holding my budget, who can still change the list, and what comes back to me? · 28% (Merkl (Angle Labs) 8/10, Sablier Airdrops (Merkle Lockups) 10/10, Boost (Rabbithole) 8/10)
- Information failure: the number is wrong or bought, or your data leaks.Scored by If someone disputes their number, can anyone outside the vendor recompute it? · 30% (Merkl (Angle Labs) 9/10, Sablier Airdrops (Merkle Lockups) 6/10, Boost (Rabbithole) 6/10)Scored by What exactly stops a farm from eating this budget, and what happens when it flags the wrong person? · 20% (Merkl (Angle Labs) 8/10, Sablier Airdrops (Merkle Lockups) 8/10, Boost (Rabbithole) 8/10)
Not assessed by this ranking: Liveness failure, Exit failure. A high place says nothing about these; the Methodology tab says what each means.
FAQs
3 questions readers ask before choosing incentive distribution.
Frequently asked
Questions people ask before choosing incentives
Is this not just an airdrop tool?
Sending tokens is the easy half and every product here does it. What separates them is what happens when the list is wrong: whether an outsider can recompute a disputed allocation, who is holding the budget between funding and claiming, who can still edit the list after publication, and what stops a farm from eating it. Eight of the nine publish no contest path at all. The single appeal route that exists is an unbounded support ticket that the same terms then disclaim.
Every vendor advertises sybil protection. How do you separate them?
By what is written down and parameterised, not by the adjective. Six of the nine market a named defence, and none of the nine publish a removal count or a sybil report for a real campaign — so nobody in this pool can show you what their filter actually did. The products that score well are the ones where eligibility is criteria you set and can export afterwards, because that is a filter you can defend line by line to a recipient who is angry. A claim to minimise false positives with no number attached earns nothing here.
How much should past incidents matter when picking one?
More than the pool would like. All nine carry a dated discontinuity within the last 32 months — a rebrand, a pivot, an exploit or a change of ownership — so a clean-looking record usually means an untested one. Two have a published, quantified loss of user funds, and the larger of the two is roughly 167 times the size of the other yet appears on none of that vendor's live surfaces. Self-disclosure with a number scores above silence, which is the opposite of how the category markets itself.
Free advisor·No signup needed
Still unsure? Get your best incentives pick
Answer a few quick questions and get one clear recommendation based on how you actually plan to use crypto — then review the evidence before deciding.
No signup·Free first pass · Private·No spam · No account
Not financial advice · Independent · Always do your own research
Best picks
Best incentive distribution in 2026
Weighted on recomputable allocation (30), budget control after publication (28), incident and operator record (22), and sybil defence in writing (20). The heaviest is whether someone outside the vendor can re-derive a disputed number: eight of the nine publish no contest path at all, and the one appeal route that exists is an unbounded support ticket the same terms then disclaim. The sybil finding is starker — six of nine market a named defence and none publish a removal count or a sybil report for a real campaign. Advertised integrations are not scored anywhere.
Best overall
Merkl (Angle Labs)
Offchain reward engine that publishes a per-recipient reward file for every merkle root it pushes to a named Distributor contract, opens a 1-2 hour onchain dispute window before rewards become claimable, and takes its 3% out of the deposited budget rather than on top of it.
Data checked Nov 2026
Offchain reward engine that publishes a per-recipient reward file for every merkle root it pushes to a named Distributor contract, opens a 1-2 hour onchain dispute window before rewards become claimable, and takes its 3% out of the deposited budget rather than on top of it. Strongest on “If someone disputes their number, can anyone outside the vendor recompute it?” (9/10): Merkl publishes each reward file on its status page "so anyone can audit past distributions" and documents "a security window of 1-2 hours following each reward update during which anyone can contest reward allocations made by the Merkl engine". The production engine is closed source. Weakest on “Who is holding my budget, who can still change the list, and what comes back to me?” (8/10): Merkl's campaign-management page states that a campaign manager can "reallocate unclaimed rewards from any recipient address to another address at your discretion" and that the window "ranges from 1 day to 1 year post-campaign". The power is stated in plain language, with no contract-level role reference. Published price: READ ON https://docs.merkl.xyz/distribute-with-merkl/fee-model (fetched 2026-11-10, HTTP 200): "Merkl's fees are deducted from the campaign budget when the campaign starts.
Best for: Recomputable allocation — 9/10
Browse this network
MS
Written and reviewed by Mathias Siemonsmeier, Founder
Not financial advice · For informational purposes only · Always do your own research