Hive Keychain 1.8.3

[stoodkev]

Latest updates

• Refactored the code to use less permissions.
• Better error handling for memo encryption.
• Futureproofed API calls to Bittrex by moving them to keychain-api backend. This is to protect from an incoming Chrome update that would cause CORS errors.
• Enable memo encryption for generic broadcasts. This was necessary for some projects, including @arcange's Account Recovery.
• Keychainify now working on Hive Keychain (big thanks to @quochuy).If enabled in the settings, every transfer, delegation or witness vote tab opened on HiveSigner will trigger a similar request on Hive Keychain. For now this will only work if the broadcasting account is specified on HiveSigner. In the future, we will add a dropdown to let you chose the account performing the actions.

About the Chrome Store

I have been putting a lot of energy in trying to get our extension listed on Chrome Store, reduced drastically the number of permissions necessary for the extension to respect Google policies, and it still gets rejected every time.
The review process takes over a week, and always end up with a generic refusal email with no further information on what causes the rejection. The email says that the PO can answer the email to request further information, which I've done multiple time, only to receive the same email again.
This is very frustrating but we will not give up and will keep doing our best to get it listed. In the meantime, you can install Keychain locally or via Firefox Add-Ons Store.

Firefox extension

Get the latest version of Hive Keychain on the FF Add-Ons Store.
It will update by itself

Local installation or update

• Export your keys (from settings)
• If you have a previous local version of Hive Keychain, uninstall it from your extension manager.
• Clone the repository from Github
• Right click on any existing extension > Manage my extensions.
• Then activate developer mode.
• Then Load Unpacked and select the folder you ve unzipped.
• Import your keys (use the same master password)

We will post again to announce when the extension makes it to the store.

Info for devs

Once the extension installed you can make any kind of requests that were available on Steem Keychain. For this you just need to:

• Replace window.steem_keychain by window.hive_keychain
• Replace STEEM, SBD and SP by HIVE, HBD and HP
• Check out the example folder

---

Hive Keychain

---

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

Support our witnesses using Hive Keychain witness tab.

Comments

[brianoflondon]

Do you know if there is any way for users to help flood Google with requests that a particular extension gets added? Is there a developer ID or something you can give us to help mount a campaign?

[stoodkev]

It has been approved, we tried on @yabapmatt s developer account and it was reviewed and accepted rapidly. Go figure. Matt s post is in here

[brianoflondon]

Ahahhh they're obviously giving preference to trusted developers at this time.

[codingdefined]

Chrome is becoming headache day by day, I have also tried to add an extension in Chrome store but get rejected without any reason as such.

[stoodkev]

yea, that was a pain but it finally got accepted, see Matt s post here

[brianoflondon]

Update:

I'm smarter than I thought :-)
I did this on the terminal in the folder where I had previously downloaded the extension with git:

git switch master

Previous HEAD position was 5f100b9 pr20
Switched to branch 'master'
Your branch is up to date with 'origin/master'.

git pull

Then I restarted Brave and that seems to have done the trick.

I previously followed instructions on an earlier post to use git to get version 1.8.2.4 into a folder on my computer.

Is there a magic Git incantation I can perform (with the obligatory black candles and pentagram inscribed around me first) which will update me without needing the import/export step?

I'm still learning all this github stuff....

[stoodkev]

On some browsers I get issues when pulling the code for the extension, probably due to wrong caching. It might be easier to just erase and clone again.

[brianoflondon]

It does seem to work on Brave though it seems one needs to quit and restart the browser and the big advantage is not losing all the keys and having to re-import.

I'm curious, where does the extension store the user data?

[ew-and-patterns]

This keychain addon is the lifeblood of HIVE. Thank you guys for making our life much much easier...
The most important addon in my browser...

[stoodkev]

Thanks for your kind words. We did it, its now available on the Store

[ew-and-patterns]

Yeah, I saw your post earlier. Thanks for your efforts. Now everyone can use it properly. Glad that I am using Firefox^^.

[urun]

Sucks i want it on chrome :)

Thanks for your work on it!!!!

Btw, do you know why it doesnt work to create a community on peakd or hive.blog using keychain?

The transaction never ends or never broadcast.

Would be awesome if you can help me with this :)

[stoodkev]

I ll look into it ;)

[gadrian]

I believe 0.18.2.5 Hive Keychain is currently disabled on PeakD and hive.blog for chromium-based browsers. I checked on Chrome and Opera. Still unstable for me, even from the master branch. Works in PeakD on Firefox from Mozilla Add-ons. Haven't checked for hive.blog.

[stoodkev]

The stable version is 18.3, anyways now its available on the Store

[gadrian]

Awesome!

[urun]

works with the new version comes Today :))))))

[mattclarke]

Time to ditch chrome then I guess. When an organisation tells you about itself, believe it. Thanks for your efforts, mate.

[marki99]

There you go, I am moving to Firefox. Well done Google.