Hi Cryptokoosha,
I think your first comment hit the nail on the head—increasing a player’s session by 10 minutes can significantly boost a studio’s revenue, and this is exactly what Chrysalis Quest aims to solve by maximizing user engagement. This is very different from the other platform. Here’s a comparative table for reference:
We’re happy to expand on this information. Chrysalis Quest allows the creation of multiple types of missions. In our MVP, we’ve launched daily missions, one-time missions, and social missions. Manual validation is tied to in-game missions in The Sandbox, where the creator must verify that the user has indeed completed the mission. A separate SIP is being prepared to request direct integration with The Sandbox API, eliminating this manual review and improving the creator experience.
The platform calculates metrics associated with these missions and events, such as:
- Number of active users in an event.
- Number of users who have completed a mission.
- Number of users who have completed missions by type (e.g., daily or one-time missions).
- Missions completed per user and/or experience.
These metrics have been crucial in identifying which missions have the highest engagement.
None of this data is provided by The Sandbox, as there is no public API available at the moment. The Sandbox’s roadmap for this year does not include any of these metrics. The request for this API is being handled directly by the DAO, and they will define the resource specifications and priorities.
Multisender and Disperse are excellent tools for asset distribution—in fact, we used Multisender in our first pre-season before BC1. However, these tools don’t fully address the need to automate rewards based on user performance in a season or mission. The manual process involves multiple steps: saving user wallets, creating spreadsheets to track reward criteria, validating rewards, minting rewards, and verifying delivery. This requires multiple applications and has a high chance of failure at some point. Managing rewards is much more than just sending NFTs, and Chrysalis Quest significantly automates and simplifies this process for creators.
For user calculations,
In the first year, we aim to reach only 2.5% of the total user base, with just 10% of those purchasing a season pass. These rewards will come not only from creators participating in a season but also from other sponsors, as mentioned in the space. We’ve already been working with various crypto collections and memecoins to make these reward pools increasingly attractive and to connect us with audiences across the Web3 space. For example, our recent partnership with Ronke (https://x.com/AsharaStudios/status/1898161359801794883), a memecoin in the Ronin ecosystem, allowed us to reach a much broader player base, and the event was fully sponsored by the Ronke team.
This platform is backed by two Design Thinking studies, including interviews and surveys with players (private data). Public data on the results of each feature implemented during Builder Challenge 2 can be found here:
showcasing the incredible growth in engagement. We’ve also tracked the top 20 studios in recent BCs and the tools and needs they’ve had during each season, as outlined in other SIPs. Additionally, there’s a 60-page document peer-reviewed by PhD-level academics, revealing important insights into the development process.
We understand that, in an ideal world, The Sandbox should develop these functionalities, but they are not currently on their roadmap, as we’ve clarified multiple times in this forum.
The voting criteria for this proposal are defined in the first post of this forum. In this case, you can vote No if you believe the proposal is unnecessary, which is a different criterion from the UGC platform.
The entire process of ideation and construction of this proposal has taken over a year. This proposal was first discussed in this SIP, where we gathered feedback from @Delegates and creators. It then underwent an exhaustive review by the DAO’s internal team before being presented in this forum. This has involved the work of many professionals from both internal and external teams, and we are always open to respectful discussions. If you have a proposal on your fridge, take it out and put it in a SIP—the community will surely be happy to review it.