The idea is to create a landing web page for engaging with potential new users. This landing page could be hosted on the official hive.io website or on a separate domain as an independent project. In the first case, trust levels would increase significantly.
The landing page itself should be structured to provide information through organized text, slides, or infographics, followed by a knowledge test with questions and multiple-choice answers. The test can be developed in detail over time, including various stages, subsections, etc. Tests can also be designed to span several days, but this would require significantly increasing the final reward. While this isn’t the focus of the article, the core idea is to convey the concept.
The goal of the test is to establish the first point of contact with a potential user while avoiding the impression that everything is overly complicated. Instead, it should emphasize that the system is complex in its execution but simple to learn. It might also make sense to offer the quest in multiple languages to cater to a wider audience.
Quest Topics (this is just an example; if implemented, the test structure will require significant work and multiple internal testing phases):
- Basics of Hive: what is HIVE, HP, HBD, decentralization.
- The role of curators, authors, witnesses, and communities.
- Basics of security: how to protect your account.
After completing the test, the final stage involves creating a new account. Depending on the number of correct answers, the participant will receive a reward in HIVE on their new account (how this will be funded is explained below). The reward should be symbolic, but enough to include some HP and enable test transactions. However, this should be HIVE from the participant who completed the test, with no additional conditions, etc. The reward amount should likely range from 5 to 10 HIVE (for a short test lasting 15-30 minutes), or higher if the test is split into multiple stages. To receive a higher payout, the questions can be made somewhat challenging, ones that not every active user would answer correctly, but a correct answer must exist.
To anticipate, investors don’t need small transactions, as they can refill their balance from an exchange themselves. Therefore, it makes sense to add an option at the end of the test to decline the reward (this way, more participants will be able to complete the test).
The idea of creating new tokens and rewarding with them is fundamentally unsuitable here, as at the initial stage of introducing information, there is already too much to absorb. Adding information and interaction with additional tokens complicates the initial task, whereas the goal is to simplify it.
This idea potentially solves two problematic aspects:
Marketing — Such an initiative can attract new users. It might make sense to create several landing pages to handle contact with different types of potential new users — content creators, readers, decentralization enthusiasts, and ecosystem investors. Alternatively, the first questions could be about whether the user is an investor or not, and depending on the answer, the quest should adapt accordingly.
Introduction to the basic information about the Hive project — The proposed model of information and knowledge testing allows for a structured approach to educating new users about all aspects of interacting with the Hive ecosystem.
I don't have all the skills and resources to fully implement this project on my own, but I am willing to invest time and work on it on a voluntary basis. Therefore, I invite anyone interested to join the discussion.
Reward for participation
Participants in the quest who provide correct answers receive a reward, while incorrect answers do not result in a payout. If the test is failed, there should be an option to retake the quest after some time. The principle should be: more correct answers = higher reward.
Source of funding
It is likely that this initiative will require the creation of a separate project (account) that will receive curation rewards from the publication of reports. It should also be understood that such work will require significant time investments, and therefore, both the initiative and the work performed should be funded. I currently don’t have a proposal for distribution. How do you see this?
Another option is to create something like an airdrop by establishing a separate fixed budget from the funding pool.
In the case of insufficient program funding, test completion should be automatically suspended until the project’s budget is replenished.
This program must be fully transparent and verifiable. Regular reports on finances and reward distribution (test completions) should be published.
Attracting participants
The option of completing the quest with rewards in itself seems more attractive. A link with the text — "Take the quest and receive rewards" — should theoretically motivate new users to familiarize themselves with the ecosystem. Such a program can complement existing initiatives or create new ones.
The motivator for new participants will naturally be the reward in HIVE.
This serves as an additional way to attract investors to the ecosystem, as this approach seems more structured in terms of presenting information. At the same time, the way the quest structure is developed will be of great importance.
Potential challenges and solutions
The main barrier to implementation is, of course, the funding of this project. If this initiative cannot attract the attention of large HP holders, it will end at the idea stage. A possible solution would be to create a funding pool to start the project. Please share your suggestions.
Combating fraud
There will likely be many people wanting to repeatedly take the test to receive rewards. To prevent such actions, mechanisms need to be implemented. One option could be to restrict access to the quest based on the device's IP address, or require registration via email/phone (which somewhat contradicts the spirit of decentralization). Another approach could be to track the activities of new accounts for a period of time, in case multiple new accounts start transferring HIVE to specific wallets, etc. I would appreciate your suggestions on how to implement this.
In conclusion...
The first steps in the Hive ecosystem seem quite complicated to me in terms of understanding what it actually is and how it works. The task is further complicated by the existence of other, mostly irrelevant alternatives, but all of this requires enormous time investment to figure out what works and what doesn’t. I believe this kind of initiative has the potential to develop.
Feedback is very important for this post. This is just a draft idea, and everything depends on the community. What would you add or remove from the idea? What do you think of the essence of the idea? How can the idea be improved? Can it potentially benefit the community? Has something similar been done before? Any comments or criticism are important.