Does Hive Want a Second Functional Wallet Option Besides Hive Keychain?
(Spoiler: It's already created)
We are reaching out to the Hive community to ask a simple but important question:
Does Hive want a second functional wallet option besides Hive Keychain? If so... why? how much?
* A Wallet that performs actions on Hive apps/websites
Current Situation
Right now, Hive Keychain is the primary wallet used across the ecosystem. While it offers great value, it also creates a "single option" dependency for most users interacting with Hive dApps/websites.
Peak Vault, an alternative wallet, is available but its broader adoption and future development depend on community feedback and support. Up to this point the development proposal to support the development has not received enough support:
Peak Vault So Far
- Proven Track Record: Peak Vault was developed and successfully released as a fully functional wallet extension, showcasing our team’s capacity and commitment.
- User-Friendly: It has a clean, intuitive interface supporting transactions on PeakD.com, HiveHub.dev, and RiseofthePixels.com.
- Developer-Ready: A wallet-agnostic SDK is available to help any app easily integrate Peak Vault. However, widespread adoption requires more apps to implement this option.
Why Multiple Wallets Matter
- Strengthen Ecosystem: Diversifying wallet options reduces dependency on a single team or product, enhancing Hive’s resilience.
- Encourage Innovation: Multiple options can create a drive to be the best option, leading to better features for the community.
- It could also lead to faster/focused development with an eye on reduction of the DHF burden after development.
Why Bring This Up Now?
The proposal to fund continued development of Peak Vault has:
- Strong community support (31 million HP voted) but hasn’t yet reached the funding threshold.
- Ranks as the 3rd most-voted proposal (by number of votes).
- A modest funding request of under 50,000 HBD if fully funded for the remaining 182 days.
What Would Funding Do?
- Compensate Past Work: Pay a key developer who worked passionately on Peak Vault without full funding.
- Enable Small Updates: Provide resources for community-requested updates or features.
- Support Open-Source Projects: Refund @peak.open for upfront costs, enabling the development of other open-source projects.
What Funding Does NOT Mean
- No Excessive Costs: We do not expect high compensation moving forward. Building a second wallet is already a valuable step for Hive’s ecosystem.
- Community-Driven Approach: The team would consult the community on future features to prioritize what matters most.
- No Software Audit: Unfortunately the proposal has not been funded for the best part of the year and we'll not be able to move forward with the 3rd party "software audit" we had planned for this project.
- No focus on Metamask Wallet: While it's essentially done the focus is likely going to be on Peak Vault primarily at this point of reduced funding.
Why Our Team?
Our team is efficient, fast and costs are comparatively very low. Also the intuitive nature of our products is highly respected.
Our Ask
We want your input and feedback to answer these questions:
- What are the benefits of a second functional wallet for Hive?
- Is an additional wallet options a priority for Hive?
- Should we continue developing Peak Vault? If so, how extensively?
Let us know what you think and what features you’d like to see in a second wallet. The Peak Vault team is ready to adapt to the needs of the Hive ecosystem.
NOTE: There is no shade to wallets that advanced users use... they have a time and place and are needed but are not the wallets used by 99% plus of our user base or any other app on Hive and are not part of this discussion.
Published with PeakVault
