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://
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.
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.
Show the arithmetic
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
Ranked on 4 published criteria weighted 30/28/22/20, which set goal alignment — 30 of the 86 points. The rest: regional access 20 (constant here), evidence depth 18 (constant here), ease of use 10 (constant here), institutional trust 8 (constant here). Profile match is shown in breakdowns but carries no weight.
- 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)
What matters most before choosing in this category
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.
The #1 overall and the scoring weights
How this category is reviewed
Ranked on four questions: If someone disputes their number, can anyone outside the vendor recompute it? Who is holding my budget, who can still change the list, and what comes back to me? What has already gone wrong on this machinery, and who is actually running it today? What exactly stops a farm from eating this budget, and what happens when it flags the wrong person?