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.