Hive Keychain DHF - Week 5

As promised in our proposal, we will post weekly updates to let you know what's going on regarding Keychain development.

Keychain extension

Let me start with a good news, after battling with Google for a while, the 1.9.2 version of Keychain was finally accepted on the Chrome Store. We plan to release another update this week with the latest changes.

This week development included :

Fixing minor issues
Completing work on Keychainify for custom_json, in order to let online stores using WooCommerce interact with Keychain. For those who are not familiar with it, you can enable Keychainify from your extension settings and it will transform some HiveSigner urls into Keychain transaction requests.
Also added support for redirecting after a Keychainify operation, through the redirect_uri field
In a new export branch, QR codes are added to the account management screen. This will be used in the future to import accounts from the extension to the mobile version. As such, it won't be released just yet, but the basic implementation is there, although I might tweek it a bit before production.

Mobile App

The mobile App development is going smoothly :

Implemented encryption and decryption methods. This was a bit tricky since the Node.js native crypto library can't be used directly in React Native.
Persisting accounts list through redux-persist middleware.
Creating an Unlock screen and switching between Sign Up and Unlock according to the saved state.

In the coming weeks, we ll complete the account setup by adding the possibility to add account by QR code or by authorized account,and managing account decryption upon unlocking the App.

Core Team

@yabapmatt : Founder - Witness
@aggroed : Founder - Witness
@nateaguila : UI/UX
@stoodkev : Lead Developer - Witness

Frequent contributors

@arcange - Witness
@quochuy - Witness

Support Hive Keychain development by voting for our proposal on PeakD (on the upcoming section), on HiveDao or with HiveSigner.

100% of payout is redirected to the DAO