Case Study Insights
Strive launched their Testnet quest on Wall and here are some of the insightful things which were incorporated in their quest
- 1.Education - The stage 1 quest was an educational quest which used the quiz and MCQ feature to educate users about the project and their testnet program
- 2.Quest descriptions with tutorials - Simple tutorial videos and task description was added for the user to navigate Strive's platform and fasten the product learning curve
quest description and video tutorials
- 3.Eligibility to do previous quests - Testnet quest was open for only those who had completed previous quests. This way the user coming to testnet quest had already learnt few things about the project and had also joined their community.
- 4.Whitelisting through quest itself - Doing this allowed any fresh user, who has discovered Strive for the first time, to qualify for the testnet program as part of the quest itself. This would eliminate first time user dropouts which would otherwise happen due to lack of information.
In Strive's case, completion of Stage 2 quest included a task to join Discord and get a role. Getting that role would result in auto whitelisting for that user.
Get a whitelist as a task
- 5.Validation through API - Strive gave endpoint APIs to Wall to verify testnet tasks. Wall used those API to create a seamless user experience of task submission.
- 6.Combination of leaderboard and lucky draw rewards - Leaderboard prizes encouraged top contributors to rise up in the leaderboard and lucky draw kept the pull factor for anyone to do the quest.
Strive's Leaderboard - referrals and top rewards