>>Hydro Community Development Program (HCDP) Overview
Hydro Community Development Program (HCDP) Overview2019-03-01T16:09:24+00:00

Hydro Community Development Program (HCDP) Overview

When the Hydro developer 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.

Anyone can complete HCDP tasks that have been created by the Hydro community.  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

A Quick Overview

Tasks created by the Hydro team 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.

A wide range of community members and participants will be responsible for the development.

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.

Type of Tasks

Overview of Different Type of 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, one of our developers, Hydrogen, have released JavaScript and Python SDKs for their 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. 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 for. 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, a community member created the following C# wrapper :

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.

Feature Image -

Hydro Team

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 formed the open source Hydro team.

Team roles include HCDP task creation, development, bringing new developers into the ecosystem, building partnerships (startups, scaleups, and enterprises), hosting meetups and hackathons, maintaining social media channels, content writing, existing and new project management, and much more.

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. Github contains all documentation. 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. A major barrier when it come Each HCDP task creator can call on the community to translate documents into any language as needed.

Do NOT follow this link or you will be banned from the site!