The Hydro team provides updates on Hydrogen’s blockchain and decentralization efforts, including the Hydro API and Hydro smart contracts.

 

Since last week’s update, we’ve been continuing to think through the ramifications of ERC-1484. The more samples and integrations we write, the more excited we become! At this point, we’re quite confident that ERC-1484 is going to be an extremely robust infrastructure layer for all kinds of identity driven applications. Getting into specifics:

1. We’ve been working to port all of our existing Snowflake code over into a 1484-compliant contract. The biggest challenge we faced was that in Snowflake, identities were denominated by HydroIDs stored as strings. In 1484, identities are denominated by EINs (Ethereum Identification Numbers) stored as uints. We successfully extricated HydroIDs from Snowflake, and are continuing to work out kinks in this ERC-1484 branch.
2. In case anyone was worried: we are not abandoning HydroIDs. Instead, we’re simply migrating HydroID creation and management into a Client Raindrop resolver. While this was slightly painful at first (because it meant reorganizing a fair amount of our backend infrastructure) we realized that it is ultimately going to be a much more sustainable and modular system. Best of all, it won’t cause any disruption to current users of the Hydro app. You can track our progress on this in the Client Raindrop resolver directory.
3. Finally, we’ve been working on integrating proposed ERC standards 725 and 1056 into a 1484 framework. Frankly, we were shocked at how easy it was to write resolvers that allow 1484 identities to be compliant with both sets of standards. We think that this is a powerful indication that our standard is robust enough to handle a wide, wide variety of use cases. For those interested, you can follow along here.

As a reminder, we welcome Hydro-related feedback on ERC-1484 in the Hydro Community discussion forum. Developers and others who wish to contribute to the official discussion forum are encouraged to do so. Finally, anyone interested in looking through the reference implementation (i.e. the smart contract that contains all the logic to construct and manage an ERC-1484 identity), can do so here.

 

We’d love to hear from you! Please get in touch via Discord, Reddit, or Telegram.