Honeycomb
Last Hivefest I stood on stage and announced the development of Honeycomb and laid out a few features for our roadmap. It's been a little over a year and with the help of a couple of Hive projects we've been able to deliver working versions of most of these features. Honeycomb allows anyone to create a token on Hive using little more than a few resource credits and a block stream. It has a fully decentralized operation that builds a multi-signature wallet to operate a DEX with minimal liquidity requirements. We've operated 3 chains(DLUX, SPK, DUAT-Ragnarok) with marginal errors, that have all lead to more resilient exchange routines, and increased financial security. With HF26 incoming testing has begun on further changes that really bring Honeycomb up to the level required to operate a large network like SPK.
This paradigm brings censorship resistant smart contracting to HIVE in a big way. And we aren't done yet.
We would like to petition HIVE to support further development that continues to improve our ecosystem.
DHF Proposal (TL/DR)
- Automated configuration for New Token Ecosystems
- RC Credit Automation to Support Network Traffic
- RC Credit Markets
- Account Creation Markets
- ZK-Rollups for L2 <-> L2 Bridging
- Continue Stability Improvements
- Documentation Improvements
- Refactor
150 HBD /Day for 1 year.
Automated configuration for New Token Ecosystems
We hope to build and maintain easy to use tools to build new token ecosystems. Answer a few questions and generate the 2 files the will turn a Honeycomb fork into a decentralized ecosystem. Config and initial state/token distro. This will include setting up the initial DEX account with multi-sig authorities. All that will be left is for the community to clone the new repo, update the .env with there account and run the architecture.
RC Credit Automation to Support Network Traffic
After HF-26 the node accounts that run honeycomb can be even more secured by not having a HP delegation. While custom_json costs are expected to go up, all transactions may have additional RC costs associated with multi-sig verification. This leads to conditions that must be monitored to ensure the parties to an ecosystem can maintain their ability to send custom-Jsons as well as transfers from the DEX. This can and should be automated.
RC Credit Markets
Additionally RC markets can be created for much broader purpose and honeycomb is certainly a vehicle to build them.
Account Creation Markets
Not a single provider of free accounts hasn't been taken advantage of. Having a market for ACT(Account Creation Tokens) that can be claimed and sold with-in the current rules for ACTs would be hard to impossible on other Hive paradigms. Utilizing the already decentralized nature of the nodes on Honeycomb, accounts that have ACTs could be automated and their ACTs sold at market value with some controls like minimum price.
~ZK-Rollups for L2 <-> L2 Bridging
Build on similar code to bridge different honeycomb ecosystems thru use of Hive Escrow Transactions and Zero-Knowledge Proofs(Better and faster than similar oracle solutions).
Continue Stability Improvements
Software is always moving an improving, keeping up to date with changes and implementing fixes is a must for any far reaching architecture.
Documentation Improvements
Release documents and guides to help ecosystems take advantage of NFT markets, ICOs, smart contracts, and more.
Refactor
Improve the base code readability so it's easier for the community to get involved and improve the ecosystem with further features.
Costs
While server costs and other things are usually a concern I believe that each community should be able to incentive their node runners and API services internally. To that effect I'm only asking for $150/day to work on the outlined base layer architecture while maintaining significant time to aid communities in their own development. I believe services like this would normally pay in the $100/hr range, but as this is a project I firmly believe in and I don't require the biggest paychecks $150/day seems to be more than fair to keep the lights on. I want to utilize the DHF because I believe value to the overall community will be much higher than this payout and all community members should benefit from this proposal thru price action of those that intend to use these features.
Track Record
With over 6 years on the blockchain I have been working here exclusively for the last 4. I've brought several concepts to life from DLUX, SPK, DUAT to HashKings v1. My github is chock-full of concepts brought to life, and my posting history has discussions in a wide range of industry knowledge. I run a witness and a backup for ensured up time, where I'm currently in the top 50. (You can help improve this standing as well with a vote). I've also increased my stake to over $20k in Hive denominated assets with several thousand more on Honeycomb assets.
Voting
Here are a couple links to vote on the proposal via your preferred platform:
https://peakd.com/proposals/234
Hivesigner
View all the proposals on:
https://hivedscan.com/proposals
https://wallet.hive.blog/proposals
https://peakd.com/proposals
Finally
I maintain my first language is code and English is only my second... But I'm more than willing to answer your questions below. No necesitas ser tímido, puedo responder en español e também em português.