Chapter 28 · The Nature of Crypto Growth
When the airdrop ends, do users remain?
- Capabilities practiced
- ResearchSystem Thinking
- Hands on
- Find a protocol that has done an airdrop; compare active addresses and trading volume for 30 days before and after.
- AI Lab
- Have AI design an incentive scheme. Describe how a likely airdrop-farming operation could exploit it.
A Real-World Problem
A team reviews quarterly growth. A beautiful curve fills the projector screen.
Week 1: 2,000 daily active addresses, stable. Week 3: an incentive campaign is announced; daily activity reaches 12,000. Week 6: tokens will be awarded for historical interactions; daily activity reaches 80,000 and volume rises thirtyfold. Week 9: snapshot day. A record 110,000 active addresses, with screenshots everywhere in the community. Week 10: the snapshot is over. Daily activity: 1,500.
Lower than before the campaign.
Three explanations emerge, each with supporters:
- “The market is weak; it is the broader environment.”
- “The airdrop was too small to retain people.”
- “The product itself needs rebuilding.”
They share one problem: none is verifiable, and none leads to a concrete next step.
Yet this can be measured. Every transaction, every address's first appearance, and every interaction over those ten weeks is publicly recorded on-chain. Chapter 23 taught you how to obtain this data.
The real question is not why activity fell, but two more specific questions:
First, how many of those 110,000 came to do something they already wanted to do? Second, how much did the incentives cost, and what did they buy?
The second has a precise answer, and line four of the income statement in Chapter 26 is its numerator.
This chapter turns those questions into repeatable procedures.
Thought Experiment
A gym opens in a new neighborhood.
Month one: the owner gives out 5,000 passes for three free months. Lines extend into the street, reception is overwhelmed, and social feeds fill with check-ins. The gym receives 900 visits a day.
Month four: the free period ends. 120 people renew. Daily visits: 140.
Three months of rent, equipment depreciation, and trainer salaries bought 120 members. Total cost divided by 120 is the acquisition cost of one real member. If that exceeds the membership fees one person contributes over three years, the campaign lost money—however lively the photos looked.
Add three details, each corresponding to a real on-chain phenomenon.
Layer one: people come solely for the gift. Registration includes a towel. Someone uses friends' and relatives' IDs to obtain 300 passes and 300 towels, never visiting once. They are not a fraudster; they found a ten-minute opportunity yielding three hundred towels.
Layer two: change the rule to sixty workouts for a gift. The owner expects this to identify enthusiasts. Instead, a new occupation appears: hired students swipe in daily, sit for ten minutes, and leave. Completing the count costs less than the prize, so it will happen.
Layer three: the owner says only that there will be future rewards. Short-term results are impressive: an unknown threshold encourages more visits, and an unknown prize encourages imagining the best outcome.
But a delayed cost follows: on announcement day, most people will be disappointed. Everyone sets their own expectations; reality offers only one result. Afterward, they may stop coming and tell others the gym is not worth visiting.
The beautiful curve is no longer mysterious. It measures the appeal of rewards, not the quality of the gym.
The question that matters throughout is: how many people return voluntarily after the free period ends?
Your Decision
You have a growth budget and four ways to spend it.
What Happens
The four options converge on the chapter's central statement:
Incentives buy first use; retention must come from the product itself.
Split growth into five layers to see where each tool acts:
- Attention
- Distribution
- Liquidity
- Incentives
- Retention
| Layer | Problem addressed | Does money help? | On-chain measure |
|---|---|---|---|
| Attention | Does anyone know it exists? | Yes, immediately | Daily new addresses |
| Distribution | Can someone who knows easily access it? | Yes, through integrations and entry points | Call-source distribution: direct or through other products |
| Liquidity | Is the experience acceptable? | Yes, with diminishing returns | Pool depth and slippage at typical trade sizes |
| Incentives | Is first use worth trying? | Spending by definition | Incentive cost and claiming addresses |
| Retention | Do people return? | No | Return rates 30 / 60 / 90 days after the campaign |
The final row is the table's center of gravity. Money can buy the first four directly, but cannot buy the fifth. A growth plan's value depends on the proportion of arrivals it retains.
This explains why successful growth so often precedes disappearing users: the first four layers were maximized while the fifth remained zero.
One clarification is essential: this chapter does not oppose incentives.
They are necessary and irreplaceable for bootstrapping (a two-sided market with neither side cannot start itself; someone must fund the first side) and ownership distribution (giving tokens to real users rather than only investors and the team).
The question is never simply whether to distribute rewards, but whether people remain afterward, and whether you measure it.
Build a Model
Split Users into Four Layers
The four-layer distinction from Chapter 23 becomes a standard procedure:
| Layer | Definition | How to check | Typical reduction |
|---|---|---|---|
| 1 Active addresses | Addresses interacting within the period | Deduplicate daily | Starting population |
| 2 Independent addresses | Remove contracts and obvious bulk-created addresses | Creation times and funding sources | A large reduction |
| 3 Real paying addresses | At least one paid interaction without incentives | Exclude incentive-related contract calls | Another large reduction |
| 4 Retained addresses | Still active 30 days after the campaign | Windows anchored to its end | This is the answer |
Only all four together answer who the users are. Reporting only layer one effectively reports nothing.
Two Numbers You Must Calculate
First: real acquisition cost.
Cost per retained user = Total incentives valued at distribution-time prices
÷ Addresses still active 90 days after the campaignUse layer four rather than layer one as the denominator. Results often differ by one or two orders of magnitude, and only the former can be compared with lifetime user value.
Second: the retention curve's shape.
Anchor day zero at the campaign's end and plot activity for the following 90 days. There are three shapes:
| Shape | Appearance | Meaning | Next action |
|---|---|---|---|
| Cliff | Returns to the original baseline or lower within days | Participants wanted rewards; the product did not retain them | Fix retention before growing |
| Gradual decline | Falls substantially, then stabilizes above baseline | Some users stayed | Identify them and their shared traits |
| Renewed rise | Brief decline followed by growth | Retained users brought new users | Rare; investigate deeply |
The stable level in the second pattern is the campaign's real output. Subtract the pre-campaign baseline to obtain net growth.
The Arithmetic of Incentive Farming
Use the designer's perspective, or you will never prevent exploitation.
The rule is simple: positive expected reward minus cost means the behavior will happen and scale.
Expected reward = Expected prize value × Probability of receiving it
Cost = Fees + capital tied up + time + address and identity preparationDesigners can change only three variables:
| Variable | Change | Side effect |
|---|---|---|
| Threshold form | Replace having done something with sustained behavior or overnight funds | Higher thresholds exclude genuine newcomers too |
| Distribution timing | Replace a one-off snapshot with repeated, long-term, unannounced distributions | Uncertainty reduces both participation and farming certainty |
| Reward ceiling | Cap rewards per address, or reward quality rather than quantity | Large users object; quality definitions will themselves be studied and copied |
Remember: any clearly describable threshold can be satisfied at scale. Effective design therefore makes scaling uneconomic, rather than simply making thresholds harder—for example, a per-address cap so a thousand addresses do not earn a thousand times as much, or long-term funds that make capital costs grow with address count.
Also, these participants are not enemies. They rationally follow your rules. If your rules reward manufactured volume, that is the outcome you asked for. You get what your rules specify, another formulation of incentive design in Chapter 20.
Verify a Large Community with On-Chain Data
The question left by Chapter 22 now has a procedure. Any claimed community of tens of thousands can be tested with four queries:
| Check | Method | Suspicious result |
|---|---|---|
| Address creation times | First-transaction times of participants | Most appear within days of campaign launch |
| Interaction depth | Transactions and amounts per address | Many stop exactly at the threshold |
| Funding-source clusters | Initial funding sources | Many share one originating address |
| Post-campaign retention | Return rate after 30 days | Near zero |
These queries are straightforward and together take less than an hour. They turn an unverifiable slogan into four citable numbers.
What It Is Called
How many people know something exists.
The first growth layer, and the only one that money alone can buy. Chapter 22 explained how attention can support prices and how quickly it disappears.
For growth, remember: attention determines the funnel's opening width, not its efficiency. Expand it tenfold with unchanged conversion and you expand the same problem tenfold.
Whether someone who knows about the product can conveniently use it.
Crypto offers a route Web2 lacks: passive distribution through composability. Others integrate your protocol and their users become yours, perhaps without your involvement. The third constraint from Chapter 27 becomes a growth asset.
That is why Chapter 29 makes integration one of BD's three outputs: one successful integration can outperform a whole incentive round and survive the campaign's end.
The cost of inducing behavior someone would not otherwise perform.
That last clause matters. If they would do it anyway, the payment is a gift, a common waste invisible in data because those users genuinely arrived.
Accounting follows Incentive Cost in Chapter 26: record both token quantities and value at contemporaneous prices.
Reward receipts recorded off-chain by the project, with unsettled redemption rules.
Three properties work together: deferred cost (issuance costs nothing immediately), changeable rules (weights can change anytime), and uncertainty as an incentive (users act on the best imagined value).
The third is both powerful and dangerous. Redemption day is the real test: earlier data rests on expectations set individually, while reality has only one outcome.
Distributing tokens to addresses under some rule.
Two different purposes are often confused: distributing ownership, making users holders for governance and fairness, and buying growth, exchanging expectations for behavior as marketing.
They require different designs. Ownership rewards depth and persistence and can be defined retrospectively. Growth needs announced rules to guide behavior—and announced rules will be optimized against.
Choosing the objective is the first, and most often skipped, step.
Whether someone returns after first use.
It is this chapter's only metric money cannot buy, and the only one answering whether the product is useful.
Measure it simply: anchor at the end of incentives and inspect active addresses after 30 / 60 / 90 days. Three numbers form a line and reveal the answer without opinions.
Chapter 30 makes this curve the main evidence for PMF.
Hands-on
This applies the workflow from Chapter 23. Complete that lab first if you have not; its queries are needed here.
Choose a protocol with an incentive campaign having a clear snapshot or end date, at least 90 days ago. Without a clear anchor, this lab cannot work.
Set day zero and define scope.
Find the snapshot, campaign end, or token distribution date. Verify official announcements and governance forums; do not copy secondary articles.
Write the definitions:
Day zero: A specific date, UTC
Window: 30 days before and 90 days after
Addresses: Main contract 0x… verified in an explorer; mainnet only
Events: … specific event names
Deduplication: By initiating address; aggregator users count under the aggregator
(include this in uncertainties)Collect two basic curves: daily active addresses and daily volume.
Use 120 days, from 30 days before zero to 90 after.
select
date_trunc('day', block_time) as day,
count(distinct tx_from) as active_addresses,
count(*) as tx_count,
sum(amount_usd) as volume_usd
from <platform event table>
where contract_address = <verified contract address>
and block_time between <day zero - 30 days> and <day zero + 90 days>
group by 1
order by 1Plot them with a vertical line at zero. Inspect the shape before drawing conclusions.
Classify the curve: cliff, gradual decline, or renewed rise.
Calculate three numbers:
Pre-campaign baseline = Average daily active addresses in the preceding 30 days
Campaign peak = Highest daily activity in the window
Stable level = Average daily active addresses on days 61–90 afterward
Net growth = Stable level − Pre-campaign baselineNet growth is the campaign's real output. It can be positive, near zero, or negative if the campaign consumed existing users' future interest.
Split participants into four layers.
-- Layer one: addresses interacting during the campaign
-- Layer two: among them, first transactions predating the campaign (not created for it)
-- Layer three: among them, at least one interaction unrelated to incentives
-- Layer four: among them, interactions continuing 30 days after day zeroPut all four numbers in a table and calculate survival at each layer. The ratio from layer one to layer four is the lab's most important output.
Plot address creation times to test community size.
Find participants' first transactions and plot a weekly histogram.
select
date_trunc('week', first_tx_time) as cohort_week,
count(*) as addresses
from <your address first-transaction-time table>
group by 1
order by 1If most cluster within one or two weeks of launch, the campaign itself caused these addresses to exist, rather than the product.
Also inspect initial funding sources. Many addresses funded from one source clearly indicate bulk creation.
If incentive-spending data is available, calculate real acquisition cost.
Find total incentive spending using the lab in Chapter 26, then:
Layer-one basis: Total incentives ÷ Active addresses during the campaign = ______
Layer-four basis: Total incentives ÷ Addresses active 90 days after zero = ______Write these side by side. Their ratio is the campaign's inflation multiplier: the first is commonly reported externally; the second is the real cost.
Write a three-part conclusion.
Real net growth from this campaign: ______ daily active addresses
Real cost per retained user: ______
Uncertainties, at least three: 1. … 2. … 3. …Do not omit uncertainties: mainnet-only coverage, aggregator attribution, incentives valued at average contemporaneous prices, and inability to distinguish one person's multiple addresses.
This output has two direct uses: first-hand evidence about users for researchers, and a baseline for your next campaign if you work on growth.
AI Lab
Like Chapter 27's PRD task, models design plans well but anticipate exploitation poorly. Training material contains more incentive design documents than retrospective analyses.
The focus is step two: first obtain a target from the model, then attack it yourself.
First, design an eight-week incentive campaign for this protocol:
<What it does, current users, and the behavior to grow>
Include:
1. Target behavior and why it matters
2. Thresholds and weights for individual contributions
3. Distribution form and schedule
4. Total budget and valuation method
5. Post-campaign success metrics
Second, add a section titled “How this plan will be exploited.”
From an incentive-farming team's perspective, give at least five concrete methods:
- Exact actions
- Approximate cost per address
- Difficulty of scaling to one hundred addresses
- Whether the plan blocks it
Third, explain why these people will return after the campaign.
If they will not, say so directly.
Rules:
- Avoid vague instructions such as “strengthen anti-Sybil measures.”
- Explain on-chain execution for every defense.Read the second section before the proposal. Vague statements like “people may use multiple addresses” mean it has not challenged its design. Write the attacks yourself, then revisit the plan.
The core action is marking each attack as blocked, unblocked, or partly blocked against the proposal.
| Your attack | Cost | Blocked by the plan? | Parameter to change |
|---|---|---|---|
Completing this table produces version two. Two rounds of this loop outperform a one-off design.
Four common model errors, ordered by danger:
- Linearly replicable thresholds. N transactions or X deposited scale almost linearly: a hundred addresses cost and earn a hundred times as much, leaving the net return rate unchanged.
- No per-address reward cap. This follows from the first error; a cap can substantially lower scaling returns.
- Layer-one success metrics. Activity rising X-fold during incentives is nearly guaranteed and conveys little information.
- An empty third section. The model skips why users return or gives generic prose. This question is the only test of the entire plan's value.
For an advanced exercise, request two plans for the same protocol: ownership distribution and growth acquisition. Their choices of thresholds, timing, and disclosure will be almost opposite, showing why one plan cannot achieve both goals simultaneously, despite many teams trying.
Verify these points yourself after using AI
- Can one person meet the thresholds cheaply with a hundred addresses?
- Is there a per-address reward ceiling? Without one, multi-address returns add linearly
- Do thresholds require one-off actions or sustained behavior and overnight funds? The former is much cheaper to farm
- Are full calculation rules announced beforehand? Published rules will be optimized against
- Are success metrics based on layer-one or layer-four addresses?
- Are costs calculated, at which prices, and per retained user?
- Most importantly, does it explain why users stay afterward? This section is almost always empty
- Are its anti-Sybil measures executable on-chain, or merely slogans?
Real-World Case
A protocol announces token rewards for historical interactions. Addresses and volume rise dozens of times within weeks. The day after the snapshot, activity returns to baseline, then falls lower within a week.
Four-layer analysis reveals a stable pattern: layer one is large; layer four approaches zero. Layer two, addresses predating the campaign, is usually small; most were created for it.
Falling below the previous baseline deserves special attention. Existing users may have performed several months' future operations early, while others leave disappointed by the result.
Costs therefore include consumed existing demand, not just tokens distributed. This rarely appears in reviews but can be measured by comparing the same older addresses' interaction frequency before and after.
The industry shifted widely from one-off airdrops to long-term points: deferred costs, adjustable rules, sustained guidance, and avoidance of immediate post-snapshot disappearance.
Two effects emerged. One was real improvement: sustained rewards made quick farming less attractive, improving retention over a single snapshot.
The other was cost redistribution: points accumulate liabilities settled at redemption. Many projects face a dilemma: full redemption is unaffordable, discounted redemption harms credibility.
The lesson is more basic than whether points are good: the test occurs at redemption, not during the campaign. Wait until then and examine the following thirty days' retention.
Many participants share a striking pattern: creation within hours, initial funding from one source, exactly the required interactions, and mechanically regular timing.
All are visible on-chain and verified with three queries: creation-time distribution, funding clusters, and interaction depth.
The economics matter: this is rational behavior under published rules rather than cheating. If N actions earn rewards, making N actions with a thousand addresses is optimal.
Respond by changing rules rather than condemning participants: cap rewards per address, require long-term funds, and score quality rather than counts. Each reduces returns from scaling, the intended goal.
Not every campaign ends in a cliff. Some protocols lose 80% of activity after incentives, then stabilize clearly above their original baseline.
These deserve study because retained addresses are the only genuine sample. They often interacted before the campaign, exceeded minimum interaction depth substantially, and kept funds in the protocol longer.
They needed the product already; incentives simply brought them sooner.
Use this directly: align future thresholds with their behavior. This beats generic anti-Sybil rules because it defines good users rather than identifying bad actors.
Change One Variable
Farming certainty disappears: unknown thresholds cannot be hit precisely. In theory, more rewards reach genuine users.
But behavioral guidance also disappears. Half the value of incentives is inducing new behavior; undisclosed rules remove it, leaving retrospective dividends.
People act on imagined rules and tend to overinvest. Unknown thresholds encourage more actions; unknown rewards encourage the best imagined outcome. Announcement day settles those expectations toward disappointment.
The trade-off is guiding behavior versus selecting real users, matching the airdrop's two purposes and their opposite designs. Trying for both often delivers neither.
Short-term public metrics look worse: flat activity, flat volume, and a quiet community. Weekly reporting makes this hard to sustain beyond two months.
Two improvements emerge slowly. First-use conversion rises as users formerly blocked by gas or repeated signatures finish their first interaction. The retention baseline rises because everyone's experience improves.
These gains do not end on a particular date.
Usually the choice is sequence rather than either-or: make layer five capable of retaining people before buying arrivals in the first four. Reverse the order and arrivals escape through the funnel's holes, producing the cliff.
This is the irreplaceable use of incentives and deserves separate attention.
Without either side, the market cannot start: no liquidity providers means no depth; no depth means no users; no users means providers earn nothing. The loop cannot start itself and needs external force.
Subsidies advance the market's bootstrapping cost until it sustains itself. Judge spending by whether the subsidized side begins earning independently as subsidies decline.
Plan the decline from day one and track genuine unsubsidized income as a share of that side's total income. A rising ratio means the market is taking over; a flat one means subsidies replace demand, not merely startup costs.
All figures shrink, sometimes tenfold. That is useful.
The definition excludes reward-seeking addresses, queries and free actions that do not prove demand, and automatic contract calls that are not human decisions.
The remaining number answers whether anyone genuinely needs the product. It is also Chapter 30's main evidence for PMF.
Prepare for one consequence: earlier growth reports will look poor. But you will know your real baseline for the first time, and growth from it does not disappear at a snapshot.
Takeaway Questions
This question now has four layers: active addresses → independent addresses → unincentivized paying addresses → addresses active thirty days after the campaign.
Only all four make the answer valid. Reporting only layer one effectively reports nothing, yet most industry growth reports do exactly that.
With incentives: all token holders pay through dilution.
Chapter 26 explained accounting. Add what did this spending buy? Calculate acquisition cost with retained addresses and compare lifetime value. Without that comparison, campaign success was never defined.
The designer's version asks: what do the rules encourage people to do, regardless of what you intended?
Take the farmer's position and calculate expected reward minus cost. If positive, the behavior will occur and scale. You get what the rules specify.
This is the central question with a standard measurement: anchor at incentive expiry, calculate retention at 30, 60, and 90 days, and plot it.
The line answers without opinions. Few course actions demonstrate on-chain data as first-hand evidence more clearly, for your project or anyone else's.
Chapter Check
Money accelerates attention, distribution, liquidity, and incentives directly, but not retention.
Returning depends on the first experience, not reward size. Rewards affect whether someone tries once.
The plan's value depends on the fifth layer retaining arrivals from the other four. If it is zero, better acquisition makes a steeper cliff.
This explains growth success followed by disappearing users. The final funnel layer was never built.
This is not opposition to incentives. Bootstrapping two-sided markets and distributing ownership are irreplaceable uses. Ask whether anyone remains afterward, and measure it.
Four queries, taking less than an hour together:
- Creation-time distribution: participants' first transactions clustered after launch suggest campaign-created addresses.
- Interaction depth: many stopping exactly at the threshold is a clear signal.
- Funding clusters: many receiving initial funds from one source suggests bulk creation.
- Post-campaign retention: how many remain active after thirty days?
These turn a slogan into four citable facts. This applies Chapter 23's method—provide first-hand data rather than disputing conclusions.
Cost per retained user = Total incentives ÷ Addresses active 90 days after campaign endUse layer four. Most campaign addresses seek rewards and leave—dividing by them measures the price of one click rather than one user.
The results often differ by one or two orders of magnitude.
In practice, calculate both and display them together, with their ratio. It indicates spending wasted on addresses that will not remain.
Only the second can be compared with lifetime value to determine whether the campaign made or lost money.
Calculate from the farmer's perspective:
Expected reward = Expected prize value × Probability of receiving it
Cost = Fees + capital tied up + time + address preparationIf the difference is positive, it will happen. Then ask: do a hundred addresses earn a hundred times as much as one? If so, it scales, and lower overhead may improve returns further.
Designers can change threshold form (sustained behavior and overnight funds), distribution timing (long-term and unannounced), and reward ceilings (per-address caps and quality scoring).
Any explicit threshold can be met at scale. Effective design makes scaling uneconomic. Caps and long-held funds are the strongest two tools because rewards cease growing linearly with addresses.
There is no standard answer. Check:
- Did you verify zero through official announcements or secondary articles?
- Did you plot activity or volume? Did you plot both, and do their shapes match?
- Did you calculate stable level minus baseline? Is net growth positive?
- How far did you split addresses? Did you reach layer four?
- Did you plot creation times, and how concentrated are they?
- Did you calculate both acquisition costs? How many times do they differ?
- How many uncertainties did you list?
Most cases show a cliff or steep decline, commonly with zero or negative net growth. Do not immediately conclude the protocol is useless—the campaign failed to produce retention; that does not mean the product lacks value.
The worthwhile next step is isolating retained addresses in a gradual decline. Their shared behavior reveals who benefits better than any theory.
Key idea
Incentives can buy first use; retention must come from the product itself.