A lot has happened this past year, and if you've followed account posts, you know that we've never stopped building features and improving our projects, whether our mobile Apps (available on Android and iOS), our extensions (available on all Chromium browsers and Firefox), or our other projects.
Let's start with some numbers to put Hive Keychain in perspective:
The current proposal is coming to an end soon, but there's still much we want to do to help the Hive ecosystem thrive, hence this new proposal.
This new proposal will start on May 15th, the date at which the current one will expire, there will be no overlap between the two proposals.
Our vision remains unchanged, meaning that this proposal will continue to focus on three different main goals:
Developing new features for our Hive products is and always will be our core objective. Here is an overview of what has been achieved in the past 12 months, and what we want to do next.
From a single extension a few years ago, we are now working on the nine projects described below, plus a few minor ones.
Our extensions (available on all Chromium and Firefox browsers) are at the forefront of our development efforts, and as such, are the first to come with new features. Here's a summary of what we've worked on this year:
hive-tx instead of dhive). This became necessary due to the Firefox add-ons requirementshive-uri scheme support: Add a hive:// URL to your post to have the link transformed into a Keychain request.keychain-commons, allowing us to have the same code running in more and more places for the extension and mobile Apps (better maintainability)Here's a non-exhaustive list of what we plan to work on, on the extension side:
hive-uri schemes to also work with Hive Engine operationsSince our mobile user base keeps growing, there are a lot of features we want to provide to make Keychain a great mobile App that would help the whole Hive mobile ecosystem thrive. As such, we put a lot of work into the mobile side this year :
hive-uri schemeThere are many more things we want to work on the mobile side this year, including:
keychain-commons (having more code in common between the extensions and Apps), using Expo for easier React Native version management, and improving the overall code qualityWe've completely refactored our Keychain Store App, the Android and iOS mobile App for store owners who want to accept payments in HIVE and HBD.
The App is now using Expo and following Keychain branding:

We've added the possibility to automatically convert the fiat value to HIVE/HBD, and to export invoices.
Big thanks to for helping us add stores to our Keychain Store map, for a new total of 77 stores worldwide accepting HIVE/HBD payments
Most of these stores are in Venezuela, but we're glad to see that it has already reached 3 continents! We are happy to connect with other communities who want to push for our tokens adoption!
Here's an example of a Hiver who went to shop for groceries using HBD in , a supermarket that uses Keychain Store for checkout.
We're looking forward to improving the Apps based on the stores' feedback, and working with the community to onboard more shops on Hive to facilitate everyday payments.
We also plan on adding a way for shops to export the list of payments, for easier accounting.

In case you are not using it yet, Keychain Swap is our one-step swap between HIVE, HBD, and all Hive Engine tokens. It compares different providers to ensure the best rate possible and performs all the steps needed to realize the swap.
We've processed over 50,000 swaps, with a combined value of over $2,000,000. The most swapped tokens are HIVE and HBD, followed by SWAP.HIVE, SPS, DEC, and LEO.
This year, we've introduced a swap widget that dApps can integrate easily to generate some revenue. The widget is easy to configure from our playground.
After the Hive-Engine incident, we also improved the robustness of our backend when nodes fail.
We've added new features to our Keychain SDK, most notably functions related to the VSC integration.
These functions are also available for testing on our playground and will be available in production soon. As mentioned above, we also added a Swap Widget customization tool to the playground.
This year, we will work on adding the missing Keychain requests (see 1/), such as Savings operations, to the SDK and playground.
After toying with the idea of a monorepo, we've decided it would take too long to refactor and kept working on extracting common code between the extensions and Apps to keychain-commons instead.
We've refactored the project to use hive-tx instead of dhive to reduce package size (see 1/), and added code as we ported extension features to mobile.
Our planned refactor of the mobile Apps (see 2/) will allow us to extract more code there, making our entire codebase much more maintainable.
Keychain commons is available on Github and npm
We've completely redesigned our Hive Keychain landing page, available here. did a great job adapting it to our branding.
Additionally, it now provides shortcuts to many small tools we developed over the years, and a way to share invoices in the hive-uri format.
We plan to add more of these tools as we go along, and better integrate our documentation and playground into the site.
Last year, we introduced our tutorial page, shown to new users on both the extensions and mobile Apps to ease them into our Hive ecosystem.
Since then, we've adjusted it based on user feedback, and are now planning to add some actions to make it more interactive.
The corresponding repository can be found here.
On the backend side, we've created new APIs for our Beacon RPC integration (see 1/) and our domain blacklist.
We are also creating many new endpoints for our multichain development.
The corresponding repository can be found here.
To improve the usability of our chain, we've started getting more and more involved with the ecosystem. A few examples :
hive:// schemesBecause Hive shouldn't be an island, we are also working on connecting with more third parties.
As you may know, following a great majority of users' support, we've started putting a small portion of our time and resources towards making Keychain multichain, by first working on EVM chains integration.
It is taking more time than we previously anticipated, but we are making good progress, notably thanks to work. At this point, Keychain can import or create accounts, auto-detect tokens and NFTs, display tokens, transfer, and show their history. It can also display NFTs and transfer them. More importantly, we've finished preparing Keychain to respond to the different EVM requests to connect to Web3 dApps.
There is still some work to be done before we are ready to deploy it. In the meantime, here's some eye candy:



We are always striving to give a timely response to issues and feature requests reported on our Discord.
Big thanks to for her commitment to helping users on our channel and others!
is doing an amazing job growing our X/Twitter presence and promoting both Keychain and the whole Hive ecosystem through his daily tweets.
Thanks to his work, we gained another thousand followers this year.
Additionally, we are regularly holding giveaway events to push forward Hive's presence on X, with around 100,000 HP delegated in the past year.
Translations are nearly up to date in five languages on the extension, landing page, and tutorial pages.
On top of some more translations for the latest features, we will work on adding more languages and translating the mobile Apps as well.
We are maintaining several auto-scaling servers for our API backend, Keychain Swap, and our other services.
For this new proposal, we are applying for the same daily budget of 600 HBD for 12 months, since our team size and overall expenses remain the same.
You can find download information for the Apps and extensions, as well as links to different resources on our landing page.
As mentioned above, we can be reached on our Discord server
: Founder - Witness
: Lead Developer
: Full-stack Developer
: Community Manager - Witness
: Advisor - Witness
You can also help us by reblogging this proposal.
100% of the rewards of this post are going to the DHF