Five deployment milestones
Contract, token and NFT deployment tasks gave participants a practical route through the chain’s tooling.
Customer story · Web3 / Layer 1 testnets
60,000 accounts completed a five-step builder track
An EVM network turned its public testnet into a path from learning to building. Claimr connected developer quests, custom on-chain checks and submitted work. About 60,000 accounts had accepted completions for all five deployment tasks - 58% of task-active accounts.
The program at a glance
Learn, build, return
- Explore the network
Follow the docs, tooling and explorer quests
- Complete the builder track
Progress through five contract deployment tasks
- Keep testing
Use the faucet, qualify for streaks and share feedback
Reported campaign outcomes
From learning the tools to completing the track
Results count recorded task checks and accepted submissions. They show progress through the campaign, without independently verifying unique developers, original code or ownership of every deployment.
- Completed the five-contract track
- ~60,000
Accounts with accepted completions for all five deployment tasks, across the configured builder track.
- Active testnet participants
- ~104,000
Accounts with at least one completed campaign task, out of about 128,000 signups.
- Faucet task completions
- ~756,000
Repeat-inclusive completion events from the custom on-chain faucet check, across about 47,000 accounts.
- Repository-link task completions
- ~100,000
Completed submission records from about 20,000 accounts; not a count of distinct repositories or original codebases.
- Feedback task completions
- ~63,000
Completed written-feedback task records from about 62,000 accounts.
- Recorded activity 30+ days later
- 39%
Among accounts with at least 30 days of observation after their first completed task. Measures later task activity, not exact-day retention.
Anonymous EVM testnet · 2024 program · Full exported cohort
The challenge
Give testnet participants a reason to build
The chain needed people to learn its tooling, try its contract and token tooling, and report what they found. A signup or wallet connection could not show that progress. The testnet needed a clear path through increasingly useful tasks, with a way to record both on-chain checks and submitted work.
Claimr’s role
A campaign platform connected to the testnet
Claimr provided the achievement and quest structure, points, recurring tasks and submission workflow. Custom tasks connected the campaign to the client’s chain for faucet, transfer and contract checks, while the operator’s team could review submitted addresses, transaction links and content in the same program.
The Claimr setup
A curriculum with reasons to keep testing
The roughly four-month program combined developer milestones, recurring faucet activity, community achievements and feedback.
Daily claims and weekly streaks
The custom faucet task checked daily participation. A separate weekly task rewarded a seven-claim streak.
Checks built for the chain
Chain-specific tasks covered faucet receipts, transfers and contract code. Submission tasks covered work that needed a different completion method.
Documentation before deployment
Explorer quests introduced the whitepaper, GitHub, developer portal and block explorers alongside the build tasks.
Feedback and contributions
Written feedback, repository links, tutorials, videos and other content gave the team evidence beyond the on-chain checks.
Continuity from an earlier season
A collectible holding check linked eligibility in the testnet to an earlier campaign asset.
The developer journey
Most active participants completed all five deployment tasks
About 76,500 accounts completed at least one deployment task. Of approximately 104,000 task-active accounts, about 60,000 completed all five deployment tasks. Contract, token and NFT milestones introduced the chain’s tooling through a practical journey.
The first task used a contract-code check; later deployment tasks accepted submitted addresses through a review workflow. These counts do not independently establish who deployed each contract or whether contracts were unique across accounts.
Of active participants completed the five-task track
Counts accepted completions across all five configured deployment milestones.
Completed both proxy and upgrade submissions
These accounts completed the proxy-address task and the implementation-replacement transaction task, giving the program a measurable advanced step.
A reason to return
756,000 faucet completions across 47,000 participants
The daily faucet task connected campaign progress to a check on the client’s testnet. About one quarter of faucet participants recorded claims on at least 30 different dates. A separate weekly task recognized seven consecutive daily claims.
The headline counts about 756,000 completion-history events. The chart deduplicates those to participant dates; neither measure is an independent recount of unique on-chain transactions.
Qualified for the weekly faucet streak
The weekly streak task was configured for seven consecutive daily claims.
Had faucet checks on 30 or more dates
These dates could be spread across the campaign. They do not need to form a consecutive streak.
Participation over time
39% recorded activity at least a month after their first task
Among the roughly 54,300 accounts with at least 30 days of observation, about 21,100 completed a task at least 30 days after their first. That is 39% of the eligible group, or about 20% of all task-active accounts when later arrivals are included.
Activity means a recorded task completion. The 39% measure counts activity any time at least 30 days after the first task, not exactly on day 30. Observation ends at the export’s last recorded completion; total follow-up still varies.
Work the team could review
Bring code submissions and product feedback into the same program
Participants could share repository links alongside their deployment work and submit written feedback on the testnet. About 20,000 accounts contributed 100,000 completed repository-link tasks; about 62,000 accounts contributed 63,000 feedback task completions.
| Contribution | Completed records | Distinct accounts | Completion method |
|---|---|---|---|
| Repository-link tasks | ~100,000 | ~20,000 | A mix of automatic acceptance and review workflows |
| Written-feedback task | ~63,000 | ~62,000 | Submission configured for review |
Completed records can include repeat submissions. Repository totals do not establish distinct repositories, original code or review of every link. Feedback counts do not measure the number of unique issues discovered.
Before the main testnet
An earlier season became part of the next journey
A smaller warm-up campaign brought about 4,400 accounts into Claimr as a hub for external quests. It recorded around 11,000 screenshot-proof completions and 980 NFT mint participants.
Completed the warm-up NFT mint task
The earlier season gave participants a collectible that could carry into the next program.
Passed the NFT holding check in the testnet
The testnet checked the same NFT contract for a participation bonus. Ownership at that time does not prove the account earned the NFT in the earlier season.
What to build on
Make the next milestone more useful to the chain
Connect deployments to the submitting wallet
Where chain data allows it, verify the deployer and detect reused contract addresses. Code existing at an address answers a narrower question.
Extend the advanced track
Use the five-task completion as a starting point for proxy upgrades, integrations or an original application. Measure each next milestone separately.
Track useful feedback and later participation
Review feedback quality, group repeated issues and compare participants with a common follow-up window. Those measures can inform the next testnet round.
Methodology
How to read the results
View sources and measurement details
The supplied story was reconciled with campaign configurations and participant exports. Rounded results measure accepted campaign activity, with completion methods and observation windows stated alongside the figures.
- Scope and accounts
- The main export covers a roughly four-month testnet program in 2024 and later signup records. About 104,000 of approximately 128,000 accounts completed a task. These are campaign accounts, not independently verified unique developers.
- Builder-track completion
- About 60,000 accounts had accepted completions for all five configured deployment tasks, or 58% of task-active accounts. Optional repository and other supporting tasks are not required for this metric. Contract checks and accepted address submissions do not independently establish deployment ownership, unique contracts or original code.
- Faucet activity
- The approximately 756,000 faucet total counts repeat-inclusive completion-history events across about 47,000 accounts. Distinct activity dates count once per account per UTC date. These are recorded task checks, not an independent count of unique on-chain transactions.
- Activity after 30 days
- Of about 54,300 accounts with at least 30 days of observation after their first completed task, 39% completed another task at least 30 days later. Observation ends at the export’s final recorded completion; total follow-up varies. This is any-time-after-threshold activity, not exact-day D30 retention, sessions or a causal lift.
- Submitted work
- Repository and feedback figures count completed submission records, which may include repeats. Repository tasks used both automatic acceptance and review workflows; configuration alone does not confirm individual review. Totals do not establish distinct repositories, original code or unique product issues.
- Campaign continuity
- A holding check referenced a collectible from an earlier season. Passing that check does not prove that the account participated in the earlier campaign, because the asset could be transferred. No unique-person returner rate is claimed.
Give your next testnet a builder journey
Connect the tasks people should complete, the checks that prove progress and the feedback your team needs next.