Akash Network
Zealy Q2 Proposal #822
piber-dev
started this conversation in
Governance Proposals
Zealy Q2 Proposal
#822
Replies: 1 comment
-
|
Hey Piber, great to see this proposal and that you are planning more Zealy sprints. From what I've seen, there are more people joining every sprint, some do stay around and become Akash users and providers. There have also been some interesting deployments. I've also seen some people learn more about Akash, how they learned to deploy and even create their own providers. I think this is a great way to promote Akash to different kinds of devs and users. I do hope this program continues, so I do support you all. |
Beta Was this translation helpful? Give feedback.
0 replies
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
-
Zealy Q2 Proposal
Introduction
The program targeting marketing and education is back! This time, we are fighting abuse, scaling the program away from Zealy, and improving downtime's between the sprints. Support us to see monthly sprints and a few smaller contests being hosted the coming months.
Details from the first proposal
Details from the second proposal
Details from the third proposal
Highlights from the last proposal
The planned user's journey was received with negative feedback from users as these missions led to a lower user retention than normal and to long waiting times before they could finish the next sprint. These missions also took up a lot of reviewing time and was automated by botters using AI generated text.
The "Star GitHub Repo's" mission was scrapped as although there was real users completing the mission showing screenshots of doing so, we believe automated anti-spam systems on GitHub prevented us to see the stars both from the user's profile and on the repo's themselves.
The "Deploy on Akash Console" mission was automated and botted but also very successful among real users, having 300 total successful submissions in total across the 3 months.
The "Create a web-app & deploy it on Akash" mission did receive a good number of submissions, for a total of 56 submissions at the end of the campaign.
Approximately 20% of submissions during the January sprint was suspected by us to be automatically completed and submitted by a highly skilled botter.
The first promotional mission "Deploy on Quasarch" was successful, bringing the beta testing feedback of 140 users and at least the same number of users to the platform at a cost of 1.0-2.5 AKT per user.
Although it wasn't easy, we were able to keep the budget in check. The first month was very successful even though the rewards were not higher than previous sprints, which used up all the unused funds from last proposal.
Changes to the program
As we figured out a workflow on how to limit the downtime between sprints, we are going to put this into practice and make the Zealy program be available almost every day of the year instead of having days or weeks of downtime sometimes like we used to have.
Abuse is something that we have always seen to an extent on Zealy, but now with the large scale it has been happening on we are going to create missions in such a way that it cannot be exploited anymore. One example of this is the "Develop your own ideas!" mission we had in the February sprint where people could submit projects to a few different tracks with only the best project being eligible for a larger prize.
Another idea we want to bring forward is making the program less reliant on Zealy, giving us the opportunity to host smaller contests on other platforms as well such as Galxe and hosting our own competitions not relying on any paid platform at all. This will be worked on with the same rewards budget and only given to successful participants like always, just that we may diverge a little from Zealy to explore other ways of finding and educating users.
Resources required
In the past, we have only used 2 roles in total in the Zealy Program, but now we are considering changing this so that it can scale. Last run, we wanted to make the program smaller but got overwhelmed with abuse and complaints, so now we are bringing it back to the level previously used in discussion 633. By changing the number of roles and using the same budget as previously approved, this gives us the opportunity to let other people contribute and for us to be more flexible with who is responsible for what tasks.
Proposal funding
Due to the Steering Committee Meeting not always occuring at the last Thursday of each month, we are going back to requesting 4 months at a time with a month-long buffer at the end where we present our results and request additional funds. This will be done exactly as we did previously:
We are going to start a sprint for March as soon as the proposal passes or earlier if we feel like the left-over funds can be utilized in a meaningful way. A new wallet will be used to manage new Zealy funds.
If no changes are made, we will publish this proposal to request funding for 4 months for a total request of $29336 USD one week after the Steering Committee Meeting. If requesting USDC and AKT in the same proposal is not possible on Mintscan or through the CLI, we will request everything in AKT with an added 10% buffer, using the fiat rate for payments tracked in USD. This would total to $32270 USD worth of AKT.
Beta Was this translation helpful? Give feedback.
All reactions