Key Takeaways
Testnet traction does not predict mainnet adoption. Testnet users are experimenting with fake money, not committing real capital. Most testnet activity is noise.
What matters on testnet is one thing: can your target user complete the core action end-to-end without help? Raw user counts and transaction volumes do not matter.
You are ready for mainnet when onboarding works, analytics are instrumented, liquidity is seeded, and docs are live. If growth has to guess what is breaking, you are not ready.
Testnet goes well. The team sees wallet connects, transactions, community activity. The launch date is set. Then mainnet goes live and the users do not come. The ones who do show up bounce. TVL sits flat. The team starts debugging UX issues it thought were sorted weeks ago.
This is the most common launch failure in DeFi. It is not a marketing problem or a product problem in isolation. It is a handoff problem. Testnet and mainnet are different environments, and the move between them requires a different kind of readiness than most teams prepare for.
This checklist exists for the teams who want to close that gap before it costs them their launch window.
15% DeFi landing page to wallet connect rate is 85% drop off before a transaction is ever attempted (Blockchain-Ads 2026) | 32% DeFi first transaction rate after wallet connect (Blockchain-Ads User Acquisition Trends Report 2026) | Same day Time Ammalgam had Formo dashboards running before their dual-chain mainnet launch (Formo case study) |
Why Testnet Traction Rarely Converts to Mainnet Growth
Understanding the gap before you try to close it.
Definition Testnet is a simulation environment where users interact with your protocol using tokens that carry no real value. Mainnet is the live deployment where users commit real capital, pay real gas, and bear real risk. These are fundamentally different user motivations, and the same interface that works on testnet can fail on mainnet for reasons testnet will never surface. |
Testnet attracts three types of participants. The first is bounty hunters and airdrop farmers, who complete flows to qualify for potential rewards. The second is developers and testers, who are checking integrations and catching bugs. The third is a small number of genuine early adopters who are evaluating the protocol seriously.
Only the third group matters for mainnet. And testnet activity gives you almost no way to tell them apart from the first two.
Ammalgam, preparing for their dual-chain mainnet launch on Sonic and Ethereum, ran into this exact problem. As their founder described it:
"On the testnet, we saw activity but lacked clarity on the user base. We couldn't reliably distinguish between meaningful users and noise, identify power users, or build 'dream user' personas based on real behaviour."
Formo's Wallet Intelligence let them identify which wallets were experienced LPs and active DeFi participants before launch, not after. Read the Ammalgam case study.
The second reason testnet traction does not convert is that mainnet introduces friction testnet never tests. Real gas costs. Real confirmation times under network load. Real risk of losing funds to a UI error. Flows that feel smooth on testnet frequently break down when these forces are real.
What Should Be Validated on Testnet (and What Does Not Matter)
One goal: can your target user complete the core action without help?
Validate on testnet | Matter less on testnet |
Core user flow from wallet connect to completed action Drop-off points in the transaction sequence Error states: what happens when a transaction fails Mobile wallet compatibility (MetaMask, Phantom, Rainbow, etc.) Time to first transaction for a cold user with no briefing Whether the success state is clear and gives a reason to return | Raw transaction volume Total wallet count TVL on testnet Social engagement around testnet announcements Completion rates from bounty hunters or airdrop farmers |
The only testnet metric that predicts mainnet performance is whether a genuine target user, someone who matches your ICP and is evaluating the protocol on its own merits, can complete the core action end-to-end without being helped. Everything else is noise. |
Run this test with five to ten people who match your ICP before you move to mainnet. Give them no instructions. Observe where they get stuck. Those friction points will be ten times worse when real money is on the line.
Pre-Mainnet Growth Readiness Checklist
Four areas. Every box needs to be checked before distribution begins.
This checklist covers the four areas that most commonly break on mainnet because they were not ready before distribution fired.
Product Usability
☐ | A cold user matching your ICP can complete the core action without instructions or hand-holding. |
☐ | Error states are handled: failed transactions show a clear message and a recoverable next step. |
☐ | Mobile wallet flows (MetaMask Mobile, Phantom, Rainbow, WalletConnect) have been tested on real devices. |
☐ | The success state after a first transaction is clear and gives the user a specific reason to return. |
☐ | You have watched at least five ICP-matching users attempt the flow and noted every moment of hesitation. |
Analytics Setup
☐ | Formo's Product Analytics SDK is installed and tracking pageviews, wallet connects, and transaction events before any public traffic arrives. |
☐ | Drop-off points in the onboarding funnel are visible in your dashboard from day one of mainnet. |
☐ | Formo's Wallet Intelligence is active so you can see the onchain profile of your early mainnet users: their DeFi history, capital profile, and which protocols they use. |
☐ | Onchain attribution is configured so you can trace which acquisition channels lead to wallet connects and first transactions. |
☐ | A Day-7 retention cohort is defined and will be the first metric you review in week two. |
Wallet Flows
☐ | Multi-wallet support is tested: at minimum MetaMask, WalletConnect, and the most common mobile wallet for your target chain. |
☐ | Transaction confirmation flows work correctly under real network congestion (not just local testnet). |
☐ | Gas estimation is accurate and surfaced to users before they sign, not after. |
☐ | Signature requests show a readable description of what the user is approving, not a raw hex string. |
☐ | Cross-chain bridging flows (if applicable) are tested end-to-end including slippage, failure states, and refund paths. |
Messaging
☐ | Your positioning page answers the question "is this for me?" in the first ten seconds for your ICP. |
☐ | You can describe what the protocol does in one sentence without the words "decentralised," "permissionless," or "capital efficient." |
☐ | Onboarding copy matches what the product actually does, not what it was planned to do six months ago. |
☐ | Trust signals are live: audit reports linked, team publicly attributable, security documentation accessible. |
☐ | The core action a first-time user should take on day one is stated explicitly, not implied. |
Mainnet Launch Checklist
Three areas: liquidity, docs and trust, distribution timing.
This is the launch window checklist. These items need to be complete before you invite any public attention to the app.
Liquidity Readiness
☐ | Seed liquidity is sufficient for a user to complete the core action without prohibitive slippage or empty pools. |
☐ | Protocol-owned liquidity (POL) is seeded as a floor before community incentives open, so launch does not depend entirely on mercenary LPs. |
☐ | Incentive structure is live only after analytics confirm at least some organic usage is occurring without it. |
☐ | Liquidity depth and TVL are visible in Formo's Product Analytics dashboard from day one so you can see if capital is leaving before it becomes a public signal. |
☐ | You have a written plan for what happens to liquidity in week two if incentives attract capital but not genuine users. |
Docs and Trust Signals
☐ | Audit report(s) are publicly linked from the protocol homepage, not buried in a GitHub repository. |
☐ | A risk disclosure or "how this works" explainer is live for users who want to understand what they are doing before transacting. |
☐ | A public bug bounty or responsible disclosure process is active and linked. |
☐ | A support channel (Discord, Telegram, or equivalent) is staffed and responding within one hour during the launch window. |
☐ | The team is publicly attributable: LinkedIn or Twitter profiles linked, no anonymous-only teams for a protocol asking users to commit real capital. |
Distribution Timing
☐ | Distribution does not fire until onboarding analytics are live and at least one day of baseline data exists. |
☐ | Your highest-leverage distribution channel fires first (your own community and protocol partners), not broad media. |
☐ | Token Gated Forms or wallet-verified waitlists have been used to qualify the pre-launch audience by onchain activity. See Formo's token gating. |
☐ | A soft launch to your pre-qualified community runs for at least 48 hours before any broader push, giving you real data on drop-off before you scale traffic. |
☐ | You have a defined threshold for "distribution paused": if onboarding drop-off exceeds 40%, traffic pauses and UX is fixed before the next push. |
Post-Launch 14-Day Checklist
The first fourteen days after mainnet are the most important growth period you will have. Most teams spend them debugging. The teams that grow spend them measuring.
Days 1 to 3: Stabilise
☐ | Onboarding funnel drop-off is reviewed within 24 hours of launch. If any step loses more than 30% of users, it is prioritised above all other work. |
☐ | Support channel is actively monitored. Every user complaint in the first 48 hours is a product signal, not a support ticket. |
☐ | Wallet Intelligence is used to profile the first 50 mainnet users: are they experienced DeFi participants or casual browsers? This tells you whether your distribution channels are finding the right people. |
☐ | Gas and transaction failure rates are checked. Anything above 5% failure rate on a standard flow requires immediate investigation. |
Days 4 to 7: Measure
☐ | Day-7 retention cohort is defined and being tracked. This is your primary launch health metric. |
☐ | Attribution data is reviewed: which acquisition channels are bringing users who actually complete the core action versus users who bounce after wallet connect? |
☐ | Formo's onchain attribution is used to compare channel quality by transaction completion rate, not just click volume. |
☐ | The top three friction points in the onboarding flow are documented with specific drop-off percentages, not vague impressions. |
☐ | You have spoken directly with at least three users who completed the core action and three who did not. |
Days 8 to 14: Iterate
☐ | At least one UX fix based on real drop-off data has been shipped. If nothing has shipped, something is wrong with the process. |
☐ | Liquidity behaviour is reviewed: is capital staying or rotating out after the first incentive window? Use Formo to compare retention by wallet cohort. |
☐ | The distribution plan for week three is updated based on which channels produced genuine users, not which channels produced the most traffic. |
☐ | A written post-mortem of launch week has been shared internally: what broke, what worked, what would be done differently. |
☐ | Day-14 retention is checked and compared to Day-7. If retention is improving, the protocol has a product loop. If it is flat or declining, the incentive structure needs redesign. |
Common Handoff Failures Between Product and Growth Teams
The testnet-to-mainnet transition requires product and growth to hand off cleanly. These are the four failures that account for most wasted launch windows.
Failure | What happens | How to prevent it |
Distribution fires before product flows are stable | Launch traffic hits a broken or confusing onboarding flow. Users bounce. The team spends the launch window debugging instead of growing. | Growth does not announce a public launch date until product signs off on the onboarding checklist. |
Analytics missing when real users arrive | The team has no visibility into where users drop off, which channels are working, or what the Day-7 retention looks like. Decisions are made on impressions. | Formo's Product Analytics are installed and tested before the first user arrives. Start for free. |
Messaging does not match the product | Users arrive expecting something different from what the protocol does. They feel misled, not just confused. Trust is harder to rebuild than it is to protect. | Growth and product review all public-facing copy together one week before launch. Every claim is checked against what the product actually does today, not what is planned. |
Liquidity launches without genuine usage | Incentives attract mercenary capital before there is organic demand. When incentives normalise, capital leaves and TVL drops, which reads as a failed launch even if the product is sound. | Seed liquidity first. Open incentives only after analytics show organic wallet connects and completions are occurring without them. |
How to Decide When You Are Actually Ready to Launch
The question teams ask is "when is the right time to go to mainnet?" The answer is almost never about a date. It is about whether four conditions are true simultaneously.
You are ready to launch when... | You are not ready when... |
A cold ICP-matching user can complete the core action without help Formo's Product Analytics are live and tracking drop-off from the first session Seed liquidity is sufficient for the core action without prohibitive slippage Audit reports, docs, and a support channel are publicly live Your team has reviewed real user behaviour on testnet, not just transaction counts | Growth is guessing what is breaking because there are no analytics Onboarding fails for a user who does not know the protocol already The launch date is set before onboarding has been tested with real users Incentives are live before any organic usage has been confirmed Messaging on the site describes planned features, not current ones |
A four to six week delay before mainnet almost always costs less than a failed launch. A failed launch costs you your first-mover window, your earliest community, and the attention of the journalists and KOLs who will not cover you again for the same story. |
The Bottom Line
Testnet traction is not mainnet readiness. The two environments attract different users, test different things, and fail in different ways. The gap between them is not a technical gap. It is a readiness gap.
Close the gap by making three things true before any public attention arrives: onboarding works without hand-holding, analytics are live so you can see what is breaking in real time, and liquidity is seeded before you invite the users who will judge whether it is there.
The first two weeks after mainnet are your most valuable and most fragile growth window. The teams that use them well have data. The teams that waste them are debugging in the dark.
Stop flying blind on your DeFi launch. Formo's Product Analytics, Wallet Intelligence, and onchain attribution give you full visibility from testnet through mainnet in a single dashboard. Same-day setup. No dedicated data team required. What you get with Formo:
|
More in This Series
Exploring DeFi growth strategy? Read the other articles in this series:
DeFi Testnet to Mainnet Launch Current article | |
FAQs
Why did our testnet users disappear on mainnet?
Testnet users disappear because they were experimenting with fake money, not committing real capital. Many are bounty hunters or airdrop farmers completing flows for potential rewards. Mainnet introduces real gas costs, real risk, and real trust requirements. Testnet traction rarely predicts mainnet adoption because the user motivations are fundamentally different.
What actually matters to validate on testnet?
What matters on testnet is one thing: whether a genuine target user can complete the core flow without getting stuck. You should validate wallet flows, transaction steps, and basic UX clarity under realistic conditions. Raw user counts and TVL on testnet do not matter. If users cannot finish the main action on testnet without help, mainnet will fail harder. Use Formo's Product Analytics to track drop-off on testnet before you launch.
How do I know if we are actually ready to go to mainnet?
You are ready for mainnet when a cold user matching your ICP can complete the core action end-to-end without instructions, analytics are live to show where users drop off, seed liquidity is sufficient for the core action, and docs and trust signals are publicly live. If growth has to guess what is breaking, you are not ready. See Formo's DeFi onboarding funnel guide for the specific metrics to check.
What are the most common handoff failures between product and growth?
The most common failure is growth launching distribution before product flows are stable. The second is missing analytics when real users arrive, leaving the team with no visibility into what is breaking. Teams also frequently ship messaging that does not match what the product currently does. These three gaps turn launch traffic into wasted attention and are preventable with a shared pre-launch checklist.
What usually breaks in the first two weeks after mainnet launch?
Onboarding, wallet flows, and user support break most often. Small UX issues that were tolerable on testnet become significant drop-off points once real money is involved. Docs and trust signals are often incomplete. Gas estimation errors and failed transaction states surface under real network conditions. The first two weeks reliably expose problems that testnet, with its forgiving environment and bounty-motivated users, never revealed.
How do I separate genuine testnet users from bounty hunters and bots?
Use Formo's Wallet Intelligence to enrich each testnet wallet address with its onchain history. Genuine DeFi participants have meaningful activity across protocols, real capital in their wallets, and usage patterns that match your ICP. Bounty hunters and bots typically have thin onchain histories with activity concentrated around airdrop events. Ammalgam used exactly this approach before their dual-chain mainnet launch. Read the case study.
