Hive Keychain Proposal

<p dir="auto"><span>A lot has happened this past year and if you've followed <a href="/@keychain">@keychain account posts, you know that we've never stopped building features and improving our projects, both on our mobile Apps (available on Android and iOS) and extensions (available on all Chromium browsers and Firefox). <p dir="auto">Let's start with some numbers to put Hive Keychain in perspective: <p dir="auto"><img src="https://images.hive.blog/768x0/https://files.peakd.com/file/peakd-hive/keychain/23v4ZsJujymMQriBJgKgherKMNHzQH6Dn1h8nDWiCpiHLi3UBcjrSEqcP2HK6539SVCrZ.png" alt="Proposal material (3).png" srcset="https://images.hive.blog/768x0/https://files.peakd.com/file/peakd-hive/keychain/23v4ZsJujymMQriBJgKgherKMNHzQH6Dn1h8nDWiCpiHLi3UBcjrSEqcP2HK6539SVCrZ.png 1x, https://images.hive.blog/1536x0/https://files.peakd.com/file/peakd-hive/keychain/23v4ZsJujymMQriBJgKgherKMNHzQH6Dn1h8nDWiCpiHLi3UBcjrSEqcP2HK6539SVCrZ.png 2x" /> <p dir="auto">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. <h2>Hive Keychain DHF <p dir="auto">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. <p dir="auto">This proposal will mainly focus on three different goals: <ul> <li>Development: Maintaining, improving, and adding features to our extensions, mobile Apps and other products (~65% of resource allocation), based on the ecosystem needs and popular user demands <li>Redesign the extensions and mobile Apps, improve their design and UX (~15% of resource allocation) <li>Bridge Hive to the broader ecosystem (~20% of resource allocation) <h2>1. Development <p dir="auto">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. <h3>Hive Keychain Mobile <p dir="auto">There is a ton 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 on the mobile side : <ul> <li>Transactions can now be initiated via QR Code, useful for businesses <li>Companion dApp enables to create the said QR Codes, find it <a href="https://qr.hive-keychain.com" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">here <li>Software Development Kit (SDK) for 3rd party developers to create said QR Codes, <a href="https://github.com/hive-keychain/hive-qrcode" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">here <li>Browser improvement: better search bar autocomplete including all ecosystem dApps and favorites, possibility to clear cache (long press on refresh), swap between tabs, etc. <li>Added a governance page (witness vote, proxy, proposals) <li>Added missing Hive Engine features (staking, delegations, etc.) <li>Full account history, filterable <li>Full Hive Engine account history <li>Added a Buy HIVE/HBD feature <li>Added the possibility to create accounts, by paying HIVE or with account creation tickets <li>Adding/Importing accounts by authority <li>Show current savings withdrawals <li>Better RPC nodes management <li>"What’s new?" popup <li>More dApps in the Explore section (contact us on Discord to add yours) <li>Apps size optimization <li>Improved HiveAuth integration to facilitate dApps experience on mobile <li>UI/UX improvements <li>Added unit and integration tests <p dir="auto">We've basically done everything we planned to do and more, except for dApp to dApp integration. We were planning to work on it but soon realized that with more and more dApps integrating HiveAuth, making sure it worked well was more of a priority, since it does the same thing but across more devices. We will work on it during this new proposal if there is a demand for it. To make it easier to work across platforms, it would keep the same format as our extension SDK. <p dir="auto">Additionally, we plan to implement the following : <ul> <li>Notification system <li>Once multisig is ready, mobile implementation and 2FA via multisig <li>In-App QR Code generation for businesses or individuals wishing to receive a HIVE/HBD payment. Customers will just have to scan it with their Keychain and validate the payment. We're seeing more and more Hive businesses and are hoping that this will help with adoption! <li>Widgets (eg. Ticker, Portfolio) <li>Automated tasks (claiming rewards, savings interest, and account creation tickets on a regular basis) <li>Keep improving the browser to make it smoother to use <li>Set up a tutorial system to make things easier for newcomers. <li><code>Keychainify implementation (transform HiveSigner links into Keychain transactions if enabled) <li>UI/UX Redesign (more on this on 2. and 3.) <li>Keeping up with new features introduced by Hard Forks <li>Users / Devs support. <h3>Hive Keychain Extension <p dir="auto">Lots of time and energy were spent on the extension side as well: <ul> <li>We've deployed Keychain v2 to production. It came with a lot of new features and a better UI/UX <li>Ledger integration. This was not an easy one, but we're really proud to offer even more security to our users through Ledger support. More information <a href="https://peakd.com/keychain/@keychain/hive-keychain-v24-ledger-integration-is-live" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">here <li>Swap feature: Swap effortlessly between HIVE, HBD, and Hive Engine tokens (coming soon TM) <li>Plugin system: A system that will enable other extensions to work with Keychain, without impacting security. It is already ready to use, but we are awaiting the completion of our first plugin (funded outside of the DHF scope) before releasing it. Devs interested in developing their own plugins can contact us on Discord <li>Completed the account history (filterable) <li>Added missing Hive Engine operations (staking, delegations, etc.) <li>Created a Governance tab <li>Added dynamic RPC nodes handling <li>Settings can now be exported as a file <li>Automatically claim savings interests <li>Choose RPC nodes for Hive Engine <li>Built a "What’s new?" popup <li>Added Transak integration for quickly buying HIVE <li>Added Hive accounts creation (paid for by account creation ticket or 3.000 HIVE) <li>Added a reminder for governance votes expiration <li>Added pending conversions and savings withdrawals <li>Integrated Analytics (up to users) <li>Added RC delegations <li>Developed an SDK for developers (more details below) <li>Started using <code>hive-tx instead of <code>dhive to reduce the extension size <li>Updated the username autocomplete to include exchanges, past receivers, and own accounts <li>Developing <code>My witness page (shipping soon) <li>Developing a <code>Manage Authorities page (shipping soon) <li>Linking Hive Engine transactions to their block explorer (shipping soon) <li>Completed unit/integration testing coverage <li>Performed UI/UX improvements <li>Updated the documentation <p dir="auto">For the sake of transparency, let's discuss the two items from the last proposal that we didn't deliver: <ul> <li>NFT: Sadly, NFTs on Hive are a mess to work with, due to the lack of a unified format and forced us to work with projects one by one. Since it was too time-consuming, we decided to stop working on it until there is some way to easily fetch and display NFTs. We'd be happy to support anyone working on this. <li>2FA: We decided to wait to implement it using Hive Multisig, which should be ready soon. Once this is implemented, we can have a transaction signed by two different keys on different devices. <p dir="auto">Here's a non-exhaustive list of what we plan to work on, on the extension side : <ul> <li>Advanced key management (multiple keys, authorized accounts, weight, and threshold management) <li>Multisig implementation once it's ready. That will be a big step towards an even safer Hive experience, both at the user and organizational levels <li>2FA system based on multisig as mentioned above <li>Ecosystem page for better dApp discovery <li>Other hardware wallets integration, based on user requests and App availability (only Ledger has a Hive App for the time being) <li>Detect if keys or vesting routes changed <li>Hive Engine automated tasks (auto-staking for instance) <li>Extension tour for a better user onboarding (in-App tutorial). Hive has a steep learning curve, this will aim to smooth it up a little bit <li>Portfolio page <li>Transactions export <li>Redesign UI/UX (see 2. and 3. below) <li>Keeping up with new features introduced by Hard Forks <li>Users / Devs support. <h3>Keychain SDK <p dir="auto">We've recently <a href="https://peakd.com/keychain/@keychain/hive-keychain-sdk-and-playground" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">released our SDK (Software Development Kit), making it easier and faster for dApps to integrate with Keychain. It is available on <a href="https://www.npmjs.com/package/keychain-sdk" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">npm and is accompanied by a <a href="https://play.hive-keychain.com/" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">playground to help devs test the different possible transactions.<br /> We're working closely with developers to make the SDK as useful as possible. <h3>Keychain Commons <p dir="auto">Little by little, we're putting code in a separate repository, that can be accessed by both the mobile Apps and extensions, in order to get the same code running on both sides. So far we mostly use it for our interfaces, but we plan to keep growing this repo in the future. <h3>Landing page <p dir="auto">We've improved a bit Hive Keychain landing page, available <a href="https://hive-keychain.com" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">here. We plan to redesign it to add more information once we're working with a designer (see 2.) <h3>Backend <p dir="auto">Our backend has been refactored, using Typescript. The repository has been reorganized and requests can be tested directly using Thunder Client (a REST API Client extension for VS Code). <h2>2. Design <p dir="auto"><span>We're very grateful to have had <a href="/@nateaguila">@nateaguila's (VP of Creative at Splinterlands) support in designing the original Hive Keychain extensions and mobile Apps. <p dir="auto">Since he has a lot on his plate and we have big changes coming (see 3.), we want to work more closely with a UI/UX designer to design a new, sharp version of Keychain. This will also be a chance to propose a more uniform experience to our users across different devices (on the extensions and mobile Apps). <p dir="auto"><a href="https://discord.com/invite/3EM6YfRrGv" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Discord.<span>If you are a professional UI/UX designer, love Hive, and use Keychain on a regular basis, we should talk! Send us your portfolio and resume on the <a href="/trending/design-application"> #design-application channel of our <h2>3. Bridging Hive to the broader ecosystem <p dir="auto">As the main way to access dApps built on Hive, we are at the center of our ecosystem. But this comes with a problem, users come to Keychain because they are already on Hive. As a wallet, it is hard for us to go onboard users from outside the ecosystem. This brings the following question : <p dir="auto"><strong>How do we help to bring the next million users to the Hive blockchain? <p dir="auto">To answer this question and others, we conducted a survey a few months ago, to which almost 1,200 of you answered. <p dir="auto">We've proposed the following scenario : <blockquote> <p dir="auto">During the bear market, attracting new users from outside the blockchain ecosystem is hard. Why not try to attract people already using dApps instead?<br /> Consider the following scenario: <ul> <li>Integrating Keychain on another blockchain that you're already using, so that you won't need to use multiple wallets <li>Gain users on this other chain by establishing partnerships with dApps <li>Promote Hive dApps <li>Repeat <p dir="auto">We strongly believe that by reaching out to a broader ecosystem, we can grow together to new all-time highs! 🚀🚀🚀 <p dir="auto">Although we thought this could be a bit controversial, the respondents were overwhelmingly in favor : <p dir="auto"><img src="https://images.hive.blog/768x0/https://i.imgur.com/KqGtbhx.png" srcset="https://images.hive.blog/768x0/https://i.imgur.com/KqGtbhx.png 1x, https://images.hive.blog/1536x0/https://i.imgur.com/KqGtbhx.png 2x" /> <p dir="auto"><span>This is why we are proposing to put a small percentage of our resources (~15-20%) towards restructuring Keychain into a multichain wallet, with a focus on Hive dApp discovery. By the end of the proposal, we aim to have a Beta version of our multichain wallet, allowing all basic interactions on EVM chains. Why EVM? Some of our dApps have already led the way in bridging our two ecosystems (<a href="/@splinterlands">@splinterlands with BSC, <a href="/@leofinance">@leofinance with Polygon, etc.), and many of our users are already using EVM chains (76%). <p dir="auto"><strong>Why would the Hive DHF pay for development on another chain though? <p dir="auto">That's probably what you're thinking, right? In our opinion, it would be beneficial for the ecosystem for the following reasons : <ul> <li>As a bridge between Hive and other ecosystems, we could bolster Hive and Hive dApps adoption <li>We would make it easier to fully use the few Hive dApps that are already multichain, from the comfort of a unique wallet <li>We could make it easy for new users to create a free Hive account, verified by their web3 identity: a big step for free onboarding without giving a phone number or email <li>Easier to buy and sell HIVE and HBD on EVM liquidity pools <li>This also gives us the chance to increase our revenue streams and allow us to bring more features thanks to these other sources of funding <p dir="auto">This part of the proposal is open to (polite) discussion, we'd love to see if the community is ready for this or would rather have us focus all our energy and passion on the other Hive features. <h3>Additional work <h4>Admin <p dir="auto"><span>We've set up a company, hired <a href="/@cedricguillas">@cedricguillas full-time last March, <a href="/@theghost1980">@theghost1980 last April as full-time developers, and <a href="/@manuphotos">@manuphotos as a CM last October. At the end of last year, we were enrolled in AppWorks Accelerator as part of batch #25, it's one of the biggest in Asia with a big focus on blockchain. This was a great experience that helped us become better founders. <h4>Support <p dir="auto">We are always thriving to give a timely response to issues reported on our <a href="https://discord.com/invite/3EM6YfRrGv" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Discord and/or <a href="https://github.com/hive-keychain/" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Github. We'll set up a ticketing system on our Discord in the near future to make support easier.<br /><span> Since we're here, big thanks to <a href="/@thekittygirl">@thekittygirl and <a href="/@foxon">@foxon for their commitment to helping users on our channel and others! <h4>Twitter <p dir="auto"><span><a href="/@manuphotos">@manuphotos is doing an amazing job growing our Twitter presence (>2k followers) and promoting both Hive Keychain and the whole Hive ecosystem through his daily tweets. <h4>Translation <p dir="auto">With so much on our plate, the translation of the Apps and extensions lagged a bit behind, but we've worked on automating the translation process through Crowdin and will call translators to work on it soon. <h2>Budget <p dir="auto">For this new proposal, we are applying for a daily budget of 600 HBD for a period of 12 months.<br /> This increase in the daily budget reflects the growth of our team. Last year we grew from a one-person team to 3 full-time devs and 1 part-time CM.<br /> To work towards our new goals, we will hire a designer and an additional front-end developer. <h3>Commitments <ul> <li>We commit to keeping all the code produced through this funding opensource. You can find <a href="https://github.com/hive-keychain/hive-keychain-extension" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Hive Keychain extension and <a href="https://github.com/hive-keychain/hive-keychain-mobile" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Hive Keychain mobile on their respective Github repositories. <li>We commit to writing monthly updates. We hope you enjoyed following our development updates so far. <h3>Downloads and Contact <p dir="auto">You can find download information for the Apps and extensions, as well as links to different resources on our <a href="https://hive-keychain.com" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">landing page. <h2>Team <p dir="auto"><a href="https://hivesigner.com/sign/account-witness-vote?witness=stoodkev&approve=1" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Witness<br /><a href="https://hivesigner.com/sign/account-witness-vote?witness=cedricguillas&approve=1" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Witness<br /><br /><br /><br /><a href="https://hivesigner.com/sign/account-witness-vote?witness=yabapmatt&approve=1" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">Witness<span><a href="/@stoodkev">@stoodkev : CEO - <span> <a href="/@cedricguillas">@cedricguillas : CTO - <span> <a href="/@theghost1980">@theghost1980 : Front-end Developer<span> <a href="/@manuphotos">@manuphotos : Community Manager<span> <a href="/@nateaguila">@nateaguila : UI/UX Advisor<span> <a href="/@yabapmatt">@yabapmatt : Advisor - <hr /> <h3>Support Hive Keychain development by voting for this proposal on <a href="https://peakd.com/me/proposals/262" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">PeakD, or with <a href="https://hivesigner.com/sign/update-proposal-votes?proposal_ids=%5B262%5D&approve=true" target="_blank" rel="noreferrer noopener" title="This link will take you away from hive.blog" class="external_link">HiveSigner. <h2>You can also help us by reblogging this proposal. <p dir="auto"><em>100% of the rewards of this post are going to the DHF