0 to 10k: Web3 Community Building
Overview
In the depths of the bear market, launching a decentralized derivatives protocol required an authentic, builder-led community rather than mercenary airdrop hunters. Token prices were down, “community” had become a euphemism for a Discord full of wallets waiting for a snapshot, and paid influencer bursts decayed in a week.
The protocol needed people who would run the testnet, file bugs, explain the product in their own language, and still be around when the market was boring. Growth was a marketing problem with an engineering texture: roles, bounties, and channels had to match how the product actually worked.
This write-up is the playbook we used, not a claim that every DeFi launch should copy the numbers.
Playbook
Proof-of-contribution roles. Invite contests and “react to this message” roles produce a census of emoji, not a community. We replaced them with technical bounties and testnet debugging roles. You got a role because you submitted a useful report, ran a node, or completed a structured quest that touched the product. Mods could still grant exceptions; they could not grant status for showing up.
Weekly alpha AMAs. Not Twitter Spaces as a content calendar. Interactive sessions with core protocol developers, on a schedule, with questions collected in-forum so the same five voices did not dominate. Recordings existed for APAC timezones. The point was to make the people who write the contracts visible, and to make “alpha” mean information density, not a hint about a listing.
APAC ambassador squad. A derivatives user in Seoul does not live in an English announcements channel. We localized operations into Mandarin, Korean, and Vietnamese sub-channels with ambassadors who could actually speak the product, not only the slogans. Ambassadors were paid like work, with a scope: translation, regional AMAs, and surface area for support — not engagement farming.
Moderation as product. Bear-market Discords rot into scam DMs, fake airdrops, and support theatre. Slow mode, verified DM policies, and a public list of what the team will never ask you were part of the growth system. Retention is impossible if the first private message a new member gets is a phishing link.
What we did not do
We did not buy a 50k member dump. We did not run a points meta whose only equilibrium is sybils. We did not pretend a testnet user and a Twitter raider are the same cohort. Paid acquisition, when it existed, pointed at the testnet and the docs, not at a vanity online count.
Results
Organic community scale reached 10,000+ active verified members with a 35% weekly retention rate throughout the testnet phase. “Verified” meant a path that was harder than a captcha: a role tied to contribution or a human check, not an email. Weekly retention in a bear market is the number that mattered; 10k empty seats would have been a press screenshot.
The residue is the operating system: contribution roles, a developer-facing AMA cadence, and regional channels with real owners. That is community as infrastructure for a protocol, not as a marketing overlay you turn off after TGE.