The Airdrop That Bought Users Who Left the Next Day — A Growth Campaign for a DeFi Protocol
Service:
Web3 Marketing (Airdrop & Growth Campaign Design)
Industry:
Decentralised Finance (DeFi) — Yield / Liquidity Protocol
Engagement Duration:
6 Months
Scope:
On-Chain Incentives · Community · Quests · Retention Mechanics
The Context
Yieldspring, a DeFi protocol, was planning an airdrop — the standard Web3 growth lever — and was about to make the standard Web3 mistake: designing it to maximise the number of users and the total value locked (TVL) it would attract, with no thought to whether any of them would stay. The team had seen airdrops drive huge spikes in users and TVL for other protocols and wanted the same. Their plan was a generous, broadly-targeted airdrop and incentive campaign optimised, implicitly, for the size of the launch spike.
They were about to spend a fortune attracting users who would leave the next day. This is the defining failure of Web3 incentive marketing, repeated endlessly: airdrops and yield incentives attract **mercenary capital** — sophisticated “airdrop farmers” and mercenary liquidity that arrives purely to harvest the incentive and leaves the instant it’s claimed or the yield drops. The result is a spectacular vanity spike — TVL and user numbers rocketing up — followed by an equally spectacular collapse as the mercenaries extract their reward and move to the next farm. The protocol pays enormous token incentives to “acquire” users who were never users, watches its metrics balloon and crater, and ends up roughly where it started, minus a large chunk of token supply now in the hands of people who’ve already sold. The airdrop didn’t grow the protocol; it rented a number and gave away the treasury for it.
The deeper truth is that an airdrop is a *user-acquisition* tool, and like all user acquisition, it’s only worth anything if the users *retain*. A mercenary who farms and dumps has a negative lifetime value — they cost real token incentives and contribute nothing lasting. Yieldspring was about to optimise for exactly the wrong metric (spike size) and attract exactly the wrong users (mercenaries), in a campaign that would look triumphant for a week and hollow forever after.
What They Asked For
The team’s ask reflected the spike mindset: “We’re planning an airdrop to drive users and TVL — help us make it big.” Bigger spike, more incentives, more reach.
We reframed it around retention. A big airdrop optimised for spike size would attract mercenaries who’d farm and dump, leaving the protocol worse off. The real brief was to design an airdrop and growth campaign for retention, not spike — structuring incentives, targeting, and mechanics to attract and keep genuine users (real protocol participants, sticky liquidity) rather than mercenary farmers, and measuring success by retained users and TVL, not by the launch-day vanity peak. Acquire users who stay, not a number that evaporates — because an airdrop that doesn’t retain is just an expensive way to give the treasury to people who’ll dump it.
The engagement fee was approximately $50,000 USD over six months, covering airdrop and incentive design, growth-campaign strategy, retention mechanics, community and quest design, and post-campaign retention analysis.
Success was defined as:
– An airdrop and incentive structure designed to attract genuine, retainable users, not mercenary farmers.
– Retained users and TVL measured weeks and months after the campaign — not just the launch-day spike.
– Sticky liquidity and real protocol participation rather than mercenary capital that dumps and leaves.
– Token incentives spent on acquisition that retains — positive lifetime value, not a giveaway to dumpers.
What We Were Up Against –
The spike is the seductive vanity metric of Web3 growth. A huge launch-day TVL and user number looks like triumph and gets celebrated across the space. Shifting the team’s goal from the spike to the far less glamorous retained number — which is smaller and slower — meant abandoning the metric the whole category worships.
Airdrop farmers are sophisticated and adversarial. Professional farmers are expert at identifying, gaming, and extracting value from airdrops while contributing nothing. Designing incentives and targeting to attract genuine users and deter mercenaries is a genuine adversarial design problem, not a simple giveaway.
Generous-and-broad attracts mercenaries; the alternative is harder. The easy airdrop (generous, broadly targeted) maximises the spike and the mercenary capture. Designing for retention — targeting genuine participants, structuring incentives to reward sticking rather than farming — is more complex and produces a smaller, less impressive-looking launch.
Retention in DeFi is genuinely hard. Even with the right users, keeping liquidity and participation sticky in a yield-chasing environment is difficult. The campaign had to be paired with genuine retention mechanics and real protocol value, not just better targeting — because no airdrop design retains users a protocol gives no reason to stay.
Our Approach — Design for Who Stays, Not for the Spike
We treat an airdrop as a user-acquisition tool judged by retention:
structure incentives and targeting to attract and keep genuine participants and deter mercenaries, and measure the users who stay, not the launch-day peak. The engagement ran in three phases.
Phase One — Retention-First Design & Reframe (Months 1–2, Pre-Campaign)
Before designing the airdrop, we changed the goal from spike to retention and designed against the farmers.
We reframed the campaign’s objective from maximising the launch spike to maximising retained users and TVL — establishing retention-based success metrics (users and liquidity still present weeks and months later) over the vanity peak, and confronting the team with the reality that a big spike of mercenary capital would leave them worse off.
We designed the airdrop and incentive structure for retention: targeting genuine protocol participants over broad mercenary reach, and structuring incentives to reward *sticking and real participation* rather than farm-and-dump extraction — an adversarial design problem aimed at attracting the right users and deterring the professional farmers.
The principle from day one: an airdrop is acquisition, and acquisition only counts if it retains.
Phase Two — Running the Campaign & Retention Mechanics (Months 2–5)
With the retention-first design set, we ran the campaign and paired it with mechanics that gave genuine users reasons to stay.
We executed the airdrop and growth campaign — community work, quests, and incentives designed to attract genuine participants rather than maximise a mercenary spike — and, crucially, paired it with retention mechanics:
structures and reasons for users to keep participating after the incentive, because even well-targeted users won’t stay if there’s nothing to stay for. We resisted the constant pull toward the bigger, broader, more generous campaign that would have produced a more impressive spike and a worse outcome. The result was, deliberately, a less spectacular launch number than a mercenary-optimised airdrop would have shown — and a far healthier base of genuine users and stickier liquidity underneath it. We measured retention from day one, watching not the peak but who remained.
Phase Three — Retention Analysis, Sustainability & Handover (Months 5–6, Post-Campaign)
An airdrop’s real verdict comes after the farmers would have left. Phase Three measured what stayed and made the approach durable.
We measured the campaign on the metric that mattered: **retention** — the users and TVL still present weeks and months after the airdrop, when mercenary capital would long since have dumped and left. We analysed who stayed and why, confirming that the token incentives had been spent on **acquisition that retained** (positive lifetime value) rather than given away to dumpers, and that the protocol had genuine sticky participation rather than a hollowed-out post-spike shell. We consolidated the retention mechanics into the protocol’s ongoing operation, and handed over the **retention-first growth framework** — the design principles, targeting, incentive structures, and retention mechanics — so Yieldspring could run future growth campaigns that acquired users who stay, permanently rejecting the spike-and-dump playbook that drains treasuries across DeFi.
The Results
Six months in — well past the point where a mercenary-optimised airdrop would have collapsed —
Yieldspring had what the spike-chasing playbook never delivers: users and liquidity that actually stayed.
Designed for Retention — The Reframe That Mattered
The airdrop was structured to attract **genuine, retainable users** and deter mercenary farmers — optimised for who *stays*, not for the launch-day spike the category worships
– Success measured by **retained users and TVL weeks and months later**, not the vanity peak that evaporates
Sticky, Not Mercenary
Sticky liquidity and real protocol participation** rather than mercenary capital that dumps and leaves — the protocol healthy past the point where spike-optimised airdrops collapse
– A deliberately **less spectacular launch number** with a far healthier base underneath it — the right trade
Treasury Spent Well — The Economic Point
–
Token incentives spent on **acquisition that retained** (positive lifetime value) rather than given away to farmers who’d already dumped — the difference between growth and an expensive giveaway
– The protocol emerged with genuine users and stickier liquidity, not a hollowed-out post-spike shell
A Framework They Own
–A handed-over retention-first growth framework — design principles, targeting, incentive structures, and retention mechanics — so future campaigns acquire users who stay, rejecting the spike-and-dump playbook
How We Work — Airdrop & Growth Campaign Engagements at Mtrench
Every airdrop and incentive engagement we take on starts by changing the question from “how big can we make the launch spike?” to “how many users will still be here in three months?” If your plan is optimised for the spike, we’ll show you why that spike is mostly mercenary capital that will farm your treasury and dump — leaving you near where you started, minus a chunk of supply.
From there we design the airdrop for retention: targeting genuine participants over broad mercenary reach, structuring incentives to reward sticking rather than farming, deterring professional farmers, and pairing it all with real retention mechanics — because no design keeps users a protocol gives no reason to stay. We measure the users who remain, not the peak that evaporates, and hand you a retention-first growth framework. We’ll be honest that your launch number may look less impressive — and be worth vastly more.
If you’re planning an airdrop optimised for the spike, you’re about to rent a number and give away your treasury — and we’d like to redesign it for retention before you spend.
Proof Over Promises.
Arjun Mehta , Founder
Nexa Protocol — Web3
“The team helped us turn a technically strong Web3 product into a brand people could actually understand. The positioning, website, and launch system made a noticeable difference in how investors and users perceived us.”
Arjun Mehta , Founder
Nexa Protocol — Web3
“The team helped us turn a technically strong Web3 product into a brand people could actually understand. The positioning, website, and launch system made a noticeable difference in how investors and users perceived us.”
Arjun Mehta , Founder
Nexa Protocol — Web3
“The team helped us turn a technically strong Web3 product into a brand people could actually understand. The positioning, website, and launch system made a noticeable difference in how investors and users perceived us.”
Arjun Mehta , Founder
Nexa Protocol — Web3
“The team helped us turn a technically strong Web3 product into a brand people could actually understand. The positioning, website, and launch system made a noticeable difference in how investors and users perceived us.”
Retention over the vanity spike. Sticky liquidity, not mercenary capital. Treasury spent on users worth keeping.