A points program and an airdrop are not really opposites. A points program is a pre-token scoring system: users earn non-transferable, off-chain points for activity, with the expectation that points will later convert into tokens. A classic airdrop distributes tokens directly to a set of wallets based on criteria the team defines, usually with little or no advance warning. Most points programs end in an airdrop, so the real decision is whether to tell users the rules in advance and run a long, measurable incentive campaign, or to reward past behaviour retroactively in one distribution. The right answer depends on your stage, how much product you have, and how much launch-day sell pressure you can absorb.
This guide compares the two honestly, covers what each does to your token after TGE, and ends with a decision framework you can apply to your own project.
How Each Model Works
Retroactive airdrop
The team takes a snapshot of on-chain activity, defines eligibility rules after the fact, and allocates tokens at or shortly after TGE. Users did not know exactly what would be rewarded, so in principle the behaviour being rewarded was organic. In practice, once a sector expects airdrops, farmers try to anticipate the criteria anyway, and the "surprise" element weakens with each cycle.
Points program
The team publishes (fully or partly) how points are earned: deposits, trading volume, referrals, holding duration, quests. Points accumulate over weeks or months on an off-chain leaderboard. At TGE the team announces a conversion rate from points to tokens, or allocates a fixed pool pro rata to points. Users know they are being rewarded and optimise for it, which is both the strength and the weakness of the model.
Because points are off-chain and carry no stated value, teams keep discretion over the conversion rate, timing and any sybil exclusions until the end. That flexibility is a large part of the appeal, but it also creates a trust problem we cover below.
Points Program vs Airdrop: Side-by-Side Comparison
| Factor | Points program | Retroactive airdrop |
|---|---|---|
| Timing | Runs for months before TGE | One-off at or after TGE |
| What users know | Rules are known, rewards optimised for | Criteria usually unknown in advance |
| Growth effect | Drives activity while it runs | Rewards past activity; little pre-launch growth |
| Data for the team | Continuous: you see what each incentive drives | Only a snapshot |
| Sybil and farming pressure | High and sustained; farmers are the main audience early on | High at snapshot time, lower during the build phase |
| Ability to adjust | Strong: weights can change between seasons | Weak: criteria are set once |
| Community expectations | Builds very high expectations of value | Expectations are vaguer, so disappointment can be less concentrated |
| Operational load | Heavy: leaderboard, anti-sybil, support, season design | Lighter: one eligibility analysis and claim process |
| Risk of activity collapse at TGE | High if the activity was mostly incentive-driven | Moderate; users were not trained to farm a known schedule |
| Fit with token not yet designed | Good: you can emit points before tokenomics is final | Poor: you need final allocation to distribute |
Neither column is "better". Points programs buy growth and information at the cost of expectation management and a mercenary user base. Airdrops are cheaper to run but give you nothing before launch.
What Points Programs Do Well
They let you incentivise before the token exists. You can reward early users while tokenomics, legal structure and exchange plans are still being finalised. Points are a commitment to reward, not a token, so you are not forced into a premature TGE just to have something to distribute.
They produce real data. Over several seasons you learn which behaviours actually stick when incentives drop, which referral sources bring real users, and which actions are pure farming. That information is valuable for designing the final allocation and your post-launch incentives.
They are adjustable. If deposits are concentrating in one whale wallet or a quest is being botted, you can change weights next season. A retroactive airdrop gets one chance to get criteria right.
Where Points Programs Go Wrong
Users optimise for points, not for your product. When the rules are public, the rational strategy is to do the cheapest thing that earns the most points. Wash trading, looping deposits and multi-wallet farming are predictable outcomes, not edge cases. Your headline metrics during the program can therefore be a poor guide to real demand.
Expectations compound. Months of grinding create an implicit promise. If the conversion is announced and users feel the value per point is low, the reaction is usually loud and public, right at the moment you most need positive sentiment. Discretion over conversion is useful, but using it in a way that feels like moving the goalposts damages trust.
Activity falls off a cliff at TGE. Once points convert, the reason many users were there is gone. Deposits and volume that were incentive-driven leave, and recipients who farmed with no intention of holding sell their allocation. This is the same dynamic covered in our guide on token unlocks and managing sell pressure, only concentrated into the first hours of trading.
Operational and legal load. Points programs need anti-sybil analysis, transparent but not exploitable rules, support for disputes, and careful wording. How you describe points matters: language implying a guaranteed future token value can create legal risk in some jurisdictions. Get legal input on the terms before launch, not after.
Where Retroactive Airdrops Fall Short
No growth before launch. An airdrop rewards activity that already happened. If you need users now, an unannounced future airdrop is a weak lever unless your sector already expects one.
Criteria are a single shot. Get eligibility wrong and you either reward farmers or exclude genuine early users, and you cannot fix it with a second season. Our guide on how to design a token airdrop covers criteria design in detail.
Sell pressure still arrives. Airdropped tokens are free to the recipient, and a meaningful share of recipients will sell. A retroactive airdrop does not avoid that; it just spreads it across a less organised group.
The Launch-Day Problem Both Models Share
Whichever model you choose, a large number of wallets receive tokens at zero cost and can sell at TGE. How the market absorbs that flow depends far more on launch structure than on how the tokens were earned. Practical levers:
- Partial unlock at TGE. Release a portion immediately and vest the rest, or reward recipients who stake or lock with a better rate. Keep it simple enough that users understand it.
- Staggered claim windows. Spread claims over time rather than opening every claim in the same block as trading.
- Behaviour-weighted allocation. Give more weight to retention signals (time active, repeat usage after incentive changes) than to raw volume, which is the easiest metric to farm.
- Sybil filtering before the snapshot is announced. Clustering analysis and exclusion lists should be done, published in principle, and closed before conversion rates are revealed.
- Order book depth sized for the distribution. Estimate how much of the airdrop could hit the market on day one and make sure there is enough liquidity, on DEX and CEX, to absorb it without a collapse that becomes the story of your launch.
The last point is where many teams under-plan. A points program can succeed on every growth metric and still produce a chart that looks like a failed launch if the first day's liquidity was sized for normal trading rather than for a mass distribution.
Decision Framework: Which Should You Pick?
Answer these questions honestly.
1. Do you need users before TGE, or do you already have them? If you need to bootstrap usage, deposits or liquidity before launch, a points program is the stronger tool. If you already have an organic user base, a retroactive airdrop can reward them without training them to farm.
2. Is your product sticky without incentives? If you are confident users will stay once rewards stop, a points program's growth is more likely to survive TGE. If your product's main appeal is the reward, a points program will inflate metrics you cannot hold.
3. Do you have capacity to run it? A points program is a months-long operation: seasons, leaderboard infrastructure, anti-sybil work, community management and dispute handling. If your team is small and stretched by audits and exchange preparation, an airdrop is the more realistic choice.
4. How finished is your tokenomics? If allocation and supply are still moving, points let you commit to rewarding users without fixing numbers prematurely. If tokenomics is locked, either model works.
5. How much day-one sell pressure can your launch absorb? Large points programs often end in a large, widely anticipated distribution to users who are ready to sell. If your launch liquidity is modest, plan a smaller allocation, stronger vesting, or both.
Quick verdict
| Your situation | Lean towards |
|---|---|
| Pre-product-market-fit, need activity and data before launch | Points program, with seasons and clear anti-farming rules |
| Established product with organic users | Retroactive airdrop |
| Small team, limited ops bandwidth | Retroactive airdrop |
| DeFi protocol needing TVL ahead of TGE | Points program, weighted towards duration not size |
| Thin expected launch liquidity | Smaller distribution with vesting, whichever model you choose |
A hybrid is also common: a light points program for a defined period, with a portion of the final allocation reserved for retroactive rewards based on behaviour that was not announced. This keeps some of the anti-farming benefit of surprise while still giving you a growth lever.
Checklist Before You Launch Either Model
- Define what success looks like after TGE, not just during the campaign (retention, not peak volume)
- Fix the total token pool for the program before you start, even if the conversion rate is set later
- Write terms that do not promise a token or a value, and have them reviewed by counsel
- Build sybil detection into the data pipeline from day one
- Decide the unlock and claim structure before announcing conversion
- Model day-one sell pressure from the distribution and size liquidity for it
- Plan what keeps users after the reward ends; our post-TGE strategy guide covers the first months after launch
How This Connects to Your Launch
Points programs and airdrops are marketing tools, but their final test happens in the order book. At Fibonacci Capital we see the same pattern repeatedly: the distribution is well designed, and then launch-day liquidity is not sized for the number of free tokens that can be sold in the first hours. Planning the distribution, the unlock schedule and market making together is what keeps a successful campaign from turning into a weak chart.
If you are designing a points program or airdrop ahead of TGE and want to plan liquidity around it, talk to us about pre-TGE launch support.