N3 · Crypto Growth & Operations
Replace successful-campaign claims with reproducible retention curves. Explain what your spending bought after incentives stop.
This track serves content, community, growth, and operations practitioners.
It starts from Chapter 28: incentives buy first use; the product earns retention. This is a measurable onchain structure, rather than moral advice. Apply it to every campaign.
Who This Track Serves
You ran a campaign with impressive numbers, then it ended. Peak screenshots remain in chat, but nobody discusses it a month later. You cannot explain what remained or what to change next time.
You create content and communities without attribution. Views are visible; the path from reading to using is not. Reports contain views and member counts only.
You own campaign budgets without measuring real acquisition costs. Spending is known; retained users are not. No retrospective calculates their ratio.
Farming operations repeatedly defeat your thresholds. Every requirement is satisfied at scale. Complete prevention is unlikely; the useful response changes the payoff structure.
Do not expect a collection of effective growth tricks. Tactics change every six months; measurement methods endure. This track teaches the latter.
Prerequisites
Complete seven Part A chapters. Chapters 23 and 28 are the two pillars.
| Required chapter | Role here | Consequence of omission |
|---|---|---|
| Chapter 20 · Tokenomics | Who bears incentive dilution | Treat token rewards as free |
| Chapter 21 · Cycles | Narrative, leverage, liquidity feedback | Claim market tailwinds as achievements |
| Chapter 22 · Meme Value | Attention, identity, community | Equate community with headcount |
| Chapter 23 · Onchain Data | Data and six measurement questions | Depend on default dashboard metrics |
| Chapter 26 · Protocol Revenue | Record incentives in income statements | Cannot calculate campaign costs |
| Chapter 27 · Crypto Product | First-use friction | Blame product gaps on user quality |
| Chapter 28 · Crypto Growth | Backbone: five-layer funnel, four user layers, three retention shapes, farming arithmetic | No framework for later work |
Why these seven? Cost accounting uses 20 and 26; measurement 23 and 28; retention capacity 27; environment 21; community 22.
Complete Chapter 28's Lab comparing active addresses and volume thirty days before and after an airdrop. Doing it changes what you see in identical campaign data.
What You Will Learn
Nine topics form four groups. Order follows campaign life: explanation, people, activity, then remaining users.
- Narrative and content
- Community and relationships
- Campaign design
- Retention and retrospectives
| Group | Topics | Problem addressed | Connecting chapters |
|---|---|---|---|
| Narrative and content | Narrative, Content, Social, Meme | Why now, why you, and memorable communication | 21, 22 |
| Community and relationships | Community, KOL | Speakers, listeners, and merely present members | 22 |
| Campaign design | Campaign, Onchain Growth | Requirements, budgets, and exploitation | 20, 28 |
| Retention and retrospectives | Retention | Who remains and what money bought | 23, 28, 30 |
Three Ideas to Reconsider
Narrative explains why now. Effective narratives identify a changing condition, a newly viable approach, and a testable near-term consequence. Missing one reduces them to adjectives. Chapter 21's feedback structure helps judge whether your narrative stands independently or merely follows the market.
Community is measured in behavior rather than people. Chapter 22's method becomes four queries in Chapter 28: address creation, interaction depth, funding clusters, and post-campaign retention. Replace community-size claims with four citable numbers within an hour. Start with your own community.
Campaign design changes payoffs rather than threshold height. Remember: any clearly described threshold can be satisfied at scale. Make one hundred addresses yield less than one hundred times one address: per-address caps, long-term capital commitment, and quality-based rather than count-based scoring reduce scaling profitability.
Measure behavior during windows when incentives have no effect.
This filters every track conclusion. Chapter 30 explains that every Web2 demand signal—users, retention, organic growth, and conversion—has a subsidized version here.
Use time-based separation, taking incentive termination as day zero, and behavior-based separation, counting non-incentivized paid interactions. Use both for robust conclusions.
Expect earlier reports to look worse. You will also discover your genuine baseline for the first time.
A product function or route that never receives rewards, providing an uncontaminated sample.
In Chapter 30's points example, stronger teams observed what each cohort did outside points, rather than points distributed.
This inexpensive decision must precede launch: before incentives cover everything. Afterward, a clean control group cannot be recovered.
Final Deliverable
A complete retrospective of a real campaign: costs, retention curves, and performance after incentives stop.
It must be real. Analyze your own campaign or reconstruct another externally—the latter proves capability especially well because only public onchain data is available.
Distinguish this from the Capstone Project. Its fourteen-part project study proves breadth and structure. This focuses deeply on one business question: was the spending worthwhile, and which parameter changes next time?
Five acceptance criteria:
Verify day zero from primary sources and define the observation window.
Use official announcements or governance records for snapshots, termination, or distribution. A recommended window is thirty days before to ninety days after. A one-day error invalidates subsequent curves.
Record two costs and two acquisition-cost versions.
State tokens distributed and fiat conversion with the chosen price. Show acquisition costs using campaign-active addresses and addresses still active ninety days later. Their ratio measures expenditure on users who did not remain.
Plot, classify, and calculate net retention growth.
Mark day zero and plot daily active addresses and volume before and after. Classify cliff, gradual decline, or uplift. Subtract the prior baseline from stabilized activity. Report negative net growth honestly: it can reveal borrowing from existing demand.
Break participation into four layers and show address creation dates.
Report active addresses, independent addresses, non-incentivized paying addresses, and post-zero active addresses, with layer-by-layer retention ratios. Add a creation-date histogram. Reporting only the first layer provides no useful assessment.
Explain exploitation and the next parameter change in separate sections.
Give at least three specific exploitation methods with per-address cost, scaling difficulty, and whether controls worked. Change only one parameter next time, explaining why and side effects. That turns a record into a reusable method.
Include at least three uncertainties: mainnet-only coverage, aggregator attribution, incentives valued at period-average prices, or inability to identify multiple addresses belonging to one person.
Assess Your Readiness
Ready: a number using fourth-layer addresses, alongside first-layer cost and their ratio.
Not ready: total budget or activity multipliers only. Incentive campaigns make both look impressive without explaining value.
The two costs often differ by one or two orders of magnitude. Only retained-user cost compares meaningfully with lifetime value and campaign profitability.
Ready: know and have run the four queries—creation dates, depth, funding clusters, and retention.
They collectively take less than an hour and turn unverifiable promotion into citable evidence.
Run them on your own community first. Studying others can become performance; studying yourself is work.
Ready: answer immediately and identify caps, capital duration, or quality scoring when returns scale linearly.
Not ready: “We added anti-Sybil measures,” without executable controls, as Chapter 28's AI checklist warns.
Participants rationally follow your rules. Effective responses make scaling unprofitable rather than merely raising thresholds.
Ready: deliberately measured a genuinely unincentivized window or permanent control area.
Two common failures: incentives never stopped, or nobody measured the break while preparing the next campaign.
This is the only growth number you cannot buy, and the one that tests whether the product is useful.
No standard answer; check:
- Did you verify day zero against official announcements, and can they find it?
- Are data definitions sufficient to reproduce the magnitude?
- Do address and volume curves differ, and are differences explained?
- Are all four layers understandable?
- Does exploitation include specific methods and costs, rather than vague multiple-address warnings?
- Does any conclusion reflect unfavorably on you?
- Did you report negative net growth?
Cliffs or steep declines with near-zero or negative net growth are common. They indicate failed campaign retention rather than necessarily a worthless product. For gradual declines, study remaining addresses separately; their shared traits reveal whom the product serves better than theory.
Common Mistakes
Mistake one: treating peaks as results.
The largest retrospective chart covers the campaign and cuts off afterward.
Incentives can always buy first use when expected rewards exceed participation costs. Calling the campaign successful provides little information.
Use the peak for cost accounting; base conclusions on days 30, 60, and 90 after day zero. Make the first retrospective chart show the post-zero period.
Mistake two: treating farmers as enemies.
“Sybil attacks” or “poor-quality users” become explanations, followed by harder requirements.
This turns economics into morality. Positive expected return minus cost guarantees participation and scaling. Harder thresholds often raise costs without changing linear returns per address.
Change the payoff structure: caps reduce scaled rewards; lasting capital requirements increase costs with address count. The purpose is lower scaled profitability.
Mistake three: content as announcement forwarding.
Calendars contain releases, partnerships, and campaigns with decent shares but no lasting citations.
Distribution is not content. Useful content explains an overlooked mechanism, supplies new data, or asks a new question. Retelling announcements does none.
Use Chapter 23's data methods for original charts and Chapter 25's thirteen cells for analysis. Such work lasts months; announcements last hours.
Mistake four: incentives as the only growth tool.
Budgets contain rewards while first-use friction never receives priority.
The first four funnel layers—attention, distribution, liquidity, incentives—can be accelerated directly with money. Retention cannot. Overall value depends on how many acquired users it retains.
Restore integrations and entry points (Chapter 29's lasting step-shaped growth), liquidity depth when it genuinely limits first-use quality, and first-use friction improvements whose benefits persist despite slow attribution.
Next Steps
Do two Labs: Chapter 28's airdrop comparison and Chapter 23's data exercise. The latter is prerequisite to the former.
Strengthen the Capstone Project's onchain data section. Independent measurement distinguishes growth professionals more than creativity alone.
Maintain Staying Current. Growth tactics belong to its event layer; build mechanisms instead. Mapping each tactic to the five-layer funnel reveals how little is truly new.
Compatible tracks:
| Combination | Why it fits |
|---|---|
| N2 · Crypto Product | Product owns retention, growth acquisition. A shared funnel prevents blame-shifting |
| N4 · Crypto BD & Ecosystem | Integrations and wallet entry points generate lasting growth through BD |
| N1 · Crypto Research & Investment | Data, definitions, and uncertainty in retrospectives are research methods |
For independent queries, tables, and pipelines without platform-defined metrics, extend into T3 · Onchain Data Engineer.