Introducing the Hydro Community Development Program (HCDP)
**All submissions are managed through the HCDP Github page, run by the Hydro Community. Hydrogen has no centralized control over the program or any tasks.**
When the Hydro dev community launched the Hydro Community Development Program (HCDP), we aimed to have a different and inclusive approach to community engagement. The program has been a success and — thanks to ongoing feedback from our community — we are making it even better. We are making HCDP even more awesome.
Any member of the Hydro community can create HCDP tasks to be completed by others. It is the responsibility of the task creator to define the task clearly, enumerate deliverables, manage submissions, and send out HYDRO allocations upon successful completion. Members of the community will also be able to become admins to contribute more to the program over time.
Program Details
- Tasks created by the Hydro Decentralization Ambassadors (DAs) will account for a maximum of 10% of the total supply of HYDRO over the lifetime of the ecosystem (this number can be increased by the community by following any governance they have setup).
- Tasks will be developer centric and deliverables will normally include submission of code.
- The responsibility of development will be dispersed to a wide range of community members and participants.
- To prevent plagiarism, once tasks are posted they will need to be claimed and submitted on time. If they are not, tasks will become re-eligible for submission from other community members.
Tasks
The tasks eligible for HCDP fall under two general categories: Project Development and Ecosystem Development.
Let’s take a look at what each entails.
Project Development
This section is dedicated to tasks regarding the expansion of the Hydro technology ecosystem internally (dealing with core Hydro code) or externally (extending or implementing Hydro code). Below are some examples of Development tasks.
SDKs & Code Libraries
Code interfaces are important, as they ease the integration of Hydro into existing systems and applications. Tools like these, which enhance the usability of the Hydro ecosystem, are great outcomes for HCDP. For reference, we have released JavaScript and Python SDKs for our Raindrop products:
dApps
All Hydro phases — Raindrop, Snowflake, Ice, Tide, Mist , and Hail— contain underlying protocols that are open architecture. Any developer globally can build a dApp or series of dApps on top of the protocols. For example, in Raindrop, the core Hydro development team has created a mobile app for two-factor authentication that interacts with the smart contracts. In Snowflake, dApps can be built by third-parties to rank and score validators, or even to onboard customers at a bank through KYC. Thousands of dApps will be built on top of Hydro by the community, making the ecosystem sustainable in perpetuity.
Bugs & Code Improvements
Finding and diagnosing bugs is a critical part of code development. While core developers strive to ship code that is bug-free, the reality is that some edge cases may not be accounted. As more and more people implement Hydro technology, bug discovery under HCDP will play a key role in fostering a healthy ecosystem and maximizing user experience.
Integrations & Expansions
While SDKs and Code Libraries facilitate processes within the Hydro ecosystem, integrations and expansions broaden the ecosystem as a whole. An example of this might be a wrapper that connects Hydro smart contracts to systems. For example, this C# wrapper was created by a community member:
Security Reports
HCDP can also include security reports and audits. Since Hydro is integrated into systems that may hold or transmit sensitive data, vulnerabilities can be catastrophic. Whenever new Hydro code is released, security analyses are instrumental in shoring up any potential holes — the more eyes on the code, the better it will be for the entire community. A good example of a security report would be a smart contract audit.
Ecosystem Development
This section is dedicated to tasks that create long-term sustainability of the Hydro token and Hydro ecosystem through decentralization, community development, and cost sharing.
Decentralization Ambassadors
Hydro will operate in over 100 countries, bringing public blockchain to banked, underbanked, and unbanked populations. It is vital that global project ambassadors steward the project long-term, ensuring development and usage in their home market. To accomplish this, the community has agreed to form DAs (decentralization ambassadors). They must submit a CV and write a essay on why they want to be a DA.
Some suggested activities for DAs are bringing new developers into the ecosystem (startups, scaleups, and enterprises), hosting meetups and hackathons, maintaining social media channels, existing and new product management, existing and new project management, and much more.
Smart contracts will be created that allows a vote on how many tokens each DA will get based on contributions to decentralization
Documentation Management
The core Hydro development team will start many documents, but it is expected that the global developer community will add, improve, and finish documentation in perpetuity. All documentation will be posted on GtHub. Examples of documentation includes:
- White papers
- API documentation
- Tutorials
Hydro strives to make it seamless for developers to incorporate blockchain into their apps, and in order to achieve that goal we need to eliminate as many barriers as possible. Language is a key barrier to be addressed, especially for our community, since it spans dozens of countries around the world. Each HCDP task creator can call on the community to translate documents into any language as needed.
Cost Sharing
Every time there is a transaction in the Hydro ecosystem there is a cost. For example, a Raindrop transaction, or a minting of a Snowflake. Rather than passing costs onto consumers, which would discourage usage and be impossible to enforce, these costs are slowly eaten by thousands of developers. This cost will be shared among developers globally by exchanging Hydro tokens for ETH tokens as needed to maintain a healthy ecosystem.
At scale, it is expected this will add a de minimis amount of tokens monthly into the Hydro circulating supply, and will ensure the ecosystem remains strong and vibrant long-term. This will also act as an audit for the public on Hydro usage, bringing true supply/demand dynamics into the blockchain space. Control over the cost sharing wallet will be in the hands of the DAs.
Next Steps
All submissions must be made through the Hydro Community GitHub page:
We’re excited for this evolution of the Hydro community, and we can’t wait to work with developers, product managers, and others in the coming months!
All allocation amounts and program categories under HCDP are subject to change at the sole discretion of the DAs. Submissions that do not go through the officially sanctioned channels of communication will not be considered. Individual submissions are reviewed on a case-by-case basis, and making a submission does not guarantee an allocation of HYDRO. The DAs reserve the right to forgo an allocation if a valid wallet address is not provided, or if any information communicated via the HCDP submission form is found to be incomplete or dishonest. Allocations made under HCDP are not intended to represent a security transfer or investment of any kind. This is not an offer or a solicitation of any offer to buy or sell securities.
