[IMAGE: https://files.peakd.com/file/peakd-hive/aggroed/j14ctB8e-image.png]
Hive-Engine is an opensource, layer-2, smart contract platform built on top of Hive, which powers communities and Dapps. Hive-Engine is seeking development funding to provide a more decentralized service, a greater range of off-the-shelf, modular, smart contracts that developers and dapp designers can use to create novel services, communities, and dapps, a number of back end performance enhancements, and lastly better interoperability with ETH and BTC.
What's the purpose of Hive-Engine?
Hive-Engine is a witness project managed by @aggroed which seeks to develop the Hive ecosystem by enabling community formation and dapp creation. The backend is an opensource community project hosted on github. The front-end, hive-engine.com as well as tribaldex.com are part of a private business.
Who are the founders of Hive-Engine?
The original founders of Hive-Engine are yabapamatt, aggroed, and harpagon.
Who works on the project now?
aggroed - Director
cryptomancer - smart contract and dev ops lead
lion200 - dswap & hive-engine.com front-end development lead
bait002 - web designer, mobile app designer
reaziliqbal - front end developer, and dapp developer
eonwarped - Nitrous creator and developer, smart contract developer
donchate - smart contract developer
inertia - documentation and block explorer guru
gerber - advisor and support
clayboyn - customer support lead
someguy123 - Privex support for the crypto token converter
What can Hive-Engine do now?
-
Hive Engine supports community and dapp creation. Hive-Engine users can create:
-
Fungible Tokens - which can be allowed to stake or be delegated, these power communities and businesses.
-
Nitrous - A fork of condenser, which uses Fungible Tokens created on Hive-Engine as an additional reward pool. Essentially users can create their own blog with rewards.
-
PoS mining - This is supported both as an off the chain and on-chain smart contract. Users can create inflation pools and doll out rewards to stakeholders.
-
Non-Fungible Tokens- NFTs from Hive-Engine power multiple Dapps already. Dcity, Rising Star, and nftshowroom are 3 examples.
-
Nested FTs in NFTs - Users can create NFTs with FTs inside of them.
-
Beechat - A chat tool (and mobile app soon) that can be used to communicate between members of the Hive Community. It's able to be integrated for free into any dapp. The client side is open source.
What is Hive-Engine developing?
Hive-Engine is looking to be the home of no-code, modular, smart contracts, which a project manager can integrate into services and dapps without the need to code anything (just configure). By doing this we're hoping to make Hive the easiest place in crypto to create a community and form a business.
In order to have the best experience possible we're looking to implement several things:
- A P2P system
- More modular smart contracts
- General performance enhancements
- Bridge to Ethereum and ERC20s
- BTC markets
What's are the benefits?
-
A P2P system helps ensure that servers operate a specific way and continue to operate that way. Hive-Engine can make unilateral decisions on hard-forks now, which is a concern to many users. By implementing a voting system and ensuring that the network consents to upgrade the system is protected from unpopular and potentially unethical changes.
-
Modular Smart Contracts - The range of options to Dapp designers and features of various websites are completely dependent on what Smart Contracts exist. While not every contract should live on the Hive-Engine platform itself there's many examples of smart contracts which benefit multiple apps, which we intend to create. Examples include:
Pack Manager - sell packs containing randomized NFTs
Bid Markets - Bid market where users can put up funds to purchase certain NFTs at a specific price
Auction Contracts - ebay inspired auction of NFTs
Liquidity Pools - Uniswap inspired liquidity pools
Witness-style Voting Systems - community leadership by consensus
Automated Payouts - Automated payouts for convenience and dapp development
Air Drops - trustless air drops
Claim Drops - trustless claim drops
These projects typically take at least a month by seasoned developers. Coding can typically be done much faster, but unit testing and maximizing resource efficiency on the blockchain end up being significant contributors.
Each one also needs front-end website development to allow a simple interface for community and dapp developers to easily utilize them.
-
General Performance Enhancements - full block log replays take 2.5 days to complete. That's pretty long. We're looking to cut that down both for the core node and account history.
-
Bridge to Ethereum and ERC20s - Hive is a fantastic resource for developing community and dapps, but one place that it's severely weak is in the price of the $HIVE token. This one gap creates endless headaches in that it's difficult to get the funding required to build here because HIVE is essentially looked at as a backwater chain by serious blockchain investors. To overcome this gap we have to tie the financial markets of Ethereum to the ease of use of Hive, and that can be accomplished by created SWAP.ETH, SWAP.ERC20s, SWAP.ERC721s as well as the reverse action of creation Wrapped Hive, Hive-Engine Fungible Tokens, and lastly Hive-Engine NFTs.
-
BTC Markets - every exchange out there bases trading pairs on BTC. Hive-Engine needs to add the same capability so that users can choose their market of trading tokens against BTC or Hive.
Budget
I'm requesting 1000 HBD for 100 days for a total of 100,000 HBD.
P2P development and testing - 20,000 HBD
Smart Contract Development - 40,000 HBD
Performance Enhancements - 20,000 HBD
Ethereum Bridge - 10,000 HBD
BTC market - 10,000 HBD
Payment request will start Nov 24 (after the refund proposal is finished).
What's the result?
By funding this project over the next 3 months Hive-Engine can continue development of the smart contract platform as a base for community and business growth, in a provably fair and community driven ecosystem, which is connected to the financial powerhouses of BTC and ETH. By combining ease of use of Hive/Hive-Engine with new modular smart contract capabilities powered by Hive-Engine and powered by the capital markets of the larger marketcap coins Hive will finally be setup for community and business growth.
If you want people, you need communities and businesses, if you want those they need an easy to use and robust smart contract platform to use. Hive-Engine is built for that goal specifically and needs your help to get all the pieces in place to do it.
Note these funds are ~98% for the development of the public, open source, community driven backend aspects of Hive-Engine and only a minor part are devoted to creating a handful of front-end forms for the smart contracts on hive-engine.com.
Good afternoon, Aggroed. Good luck with your proposal.
> After 4 years of trying it seems unlikely to come from blogging rewards anymore, and will come from new apps and communities.
I'm not sure if the word 'trying' is accurate. You see, content is a product. Our general onboarding attempts are often if not always targeted towards attracting new potential creators with a subtle promise of being paid. So we've been filling our shelves with this product for years, then refusing to open our doors and sell it to the consumer. Consistently cramming the stage full of performers, then ignoring the fact the seats are empty. I've not seen any attempts to attract consumers over the years, even though we offer them the best deal in entertainment this world has to offer.
I do recall a time when potential consumers were quite literally being paid to look away, during the whole paid vote/bidbot era. A content creator back then stood no chance of growing a consumer base because being paid to not consume or look away was advertised to be far more appealing. So let's subtract those years from the four years of "trying".
Many tribes followed the same path. Open the floodgates to creators, create perks that would appeal to the crypto crowd, create amazing consumer perks, then completely ignore the consumer's role. Without those consumers, how are the tribes doing?
The missing element or key ingredient is the consumer, when you're offering a product. Let's just pretend for a moment I'm a professional here. If you ask me what I need in order to succeed, I will tell you I need consumers. If you ask me what I'm lacking here, I will say consumers.
You can't even watch a livestream these days without the host stopping every few minutes to thank consumers for their donations. That steady stream of money pours in daily and it's not exclusive to video content. Consumers are donating or tipping all over the internet. The platforms often take a huge cut. The entire time consumers and creators were getting ripped off by those platforms, Hive sat here offering them a far better deal, and kept it a secret.
The content creators did not fail this platform. Blaming the blogger has seemingly become so incredibly fashionable as of late. So now not only is the massive market of consumer potential being ignored, but a wide swath of the existing and dwindling userbase is also being pushed away further.
I wish to see this place succeed and nothing else. I do not see any problems with creating more apps and communities. I just hope people can learn the importance of placing butts in the seats.
It's crazy how one line can trigger so many thoughts. Just know I mean well.
Social media services like Twitter and Facebook are most often used by the consumer class to help distribute content found on content production platforms like Youtube or online magazine style sites, etc.
A blog post isn't social media. A video isn't social media. A short word and a link to a blog post is social media.
Short form content and social media are two different things. A quick ten second video is not created on Facebook or Twitter, it's shared there; passed around to consumers so more people can see.
Monetizing a tweet and calling that content seems kind of strange to me. That's like paying for advertisements, promos, flyers, etc.
Typically consumers outnumber creators by a huge margin. Creators benefit when consumers use a service to distribute the creator's content free of charge. Maybe now they can earn a few cents for it. It would be incredibly awkward though if distributing content paid more than creating it.
Also, far too often on Twitter I see lengthy thoughts shared in a series of Tweets. When someone has a lot to say, Twitter fails them. They'd be better off having access to a place where they can speak their entire mind in one go without interruption. I would have been incredibly annoyed if I had to break down this response into several responses due to the limitations of the software I use.
So your service does have a place in this world. If I had a UI that organizes and separates my social media from my content creation, I'd probably use your service a lot more. But right now my d.buzz would blend and get mixed in with my content and make my blog look messy, so I prefer not to use it.
If there were two separate feeds, I'd probably use it to announce new content or share what we call reblogs to my following here. I'd use it to quickly scroll through what those I follow are sharing. That feed would need to be in it's own little space that's always accessible, even as I type these words here in this box. Or as I'm creating a post, I should be able to easily scroll through the d.buzz feed without having to leave the editor. I think d.buzz would work great as a social media app built right in to something like PeakD, instead of posing as a content creation platform of its own.
@klye | Nov. 3, 2020, 11:14 p.m. | Votes: 10 | [
VOTE ]
$100,000 to develop what essentially boils down to a suite of plugins to convert ERC-20 transaction data into JSON is a pretty decent ask. As a developer myself totally understand the dev team has got to eat but from a technical standpoint I'm hesitant to even begin to entertain the idea that something of this nature, assuming the foundation of it isn't already available open sourced somewhere, wouldn't take a team of a few decently skilled individuals a few months and about a 1/5th of the budget you're asking here to complete. This isn't a shot at the HE team or your proposal, merely an observation from someone who has inhabited this ecosystem longer than most people have even had a concept of development being possible within the cryptocurrency space.
What strikes me the most troubling about this whole idea isn't the money ask being put fourth here but the entire idea behind developing something that directly or indirectly tries to build upon the coat-tails of another network we should be aiming to become an alternative to, not for lack of a better term be assimilated by via actions striving towards integration. Perhaps my vision issue on this is clouded by the disdain I harbour towards what I can only describe as "crypto for people who don't crypto".. Etherium should be something that anyone who truly embraces the spirit of crypto isn't wholeheardedly excited to get involved with. It isn't immutable, it's built to suck capital from it's users and ultimately failed as a viable cryptocurrency fundamentals wise with the DAO. As a network Etherium is nothing which can be considered anything remotely resembling satoshis original vision for crypto currency.
With all that being said though, I will support your proposal even if I don't agree with the fundamentals of what you're trying to achieve.. The Hive-Engine.com platform is a cornerstone of what made steem and is making HIVE somewhat of an interesting environment to work and develop in and frankly without it my own development en-devours would be far less amusing. Between it's ability to create value from ideas spawned by communities to simply being able to create shitcoins for lulz with a cost to the creator amounting to less than a pack of smokes the economic and entertainment value of what's been built with Hive-Engine.com is something that I personally cannot downplay.
I'll support Hive-Engine, but getting deep into bed with Etherium rather than perhaps focusing on your own unique offerings seems akin to chasing after a sinking ship. If the broken fundamentals and gas price gouging aren't enough to make a person leery on that shit I don't really know what would be.
As for your HE rewrite I wish you luck on the update. Going from a single threaded, blocking process architecture to a multi-threaded asynchronous architecture is no small feat and I'm interested to see what you guys come up with. The idea of codeless smart contracts is a somewhat tempting thought.. and I'm sure to the non-technicals out there the sort of buzzword they froth at the mouth upon hearing.. however in practice a system such as that will be somewhat underwhelming both in utility as well as ability to spawn innovation, likely resulting in the system being overlooked by serious players, unless said system itself was designed around allowing developers to submit and modify their own code to be able to create unique instances of headless applications.
If done right a properly resource managed fully functional smart side chain could be an absolute game changer for all involved.. However bringing something like this to market that is both capable enough to get serious developers involved but at the same time simple enough for the average internet serf to be able to comprehend and use is going to be an extremely delicate balancing act.
As for making a functional BTC trading pair exchange given what you've already built it's simply a matter of changing a few variables and setting up some RPC calls differently to make HE BTC compliant. In all honesty besides the legal loopholes you'd need to cover given your pre-existing code base this could be knocked out in an afternoon over some beer.
The real question I find myself asking here at the end of writing all this is.. how is it possible after being quite well established in this ecosystem for what most would consider a decent length of time and having built number of seemingly profitable applications on top of HIVE that you've not been able to self fund your in house development with profits earned to avoid this whole asking for what is essentially a float to keep development moving forward? Now please don't mistake the tone of that question as being arrogant nor provocative as some would like to paint it as. Honestly curious as to what percentage of income from established services gets put back into R&D and what percentage in the future would need to be put back into development in order to avoid what is essentially crowd sourcing seed money for a privately held company.
Now if people get triggered by this post so be it however I certainly didn't come here to fucking troll nor am I here to piss anyone off or kiss anyone's ass. I'm merely expressing my point of view and potential concerns from the perspective of a developer who builds applications without the financial backing of established income sources or crowd sourced seed money for the most part. No part of this is meant to come off as salt or piss, but rather an objective look at what has been observed over a lengthy period of time within the ecosystem.
Can I get a link to the proposal to vote the thing here shortly or is it still being drafted?
Anyways, hope ya'll get your vision built even if it does involve fundamentally stunted network integration. Ya'll got's my support simply on the basis of having created Hive-Engine which regardless of some less than amiable ramblings from folks within the HIVE horde is a pretty friggin' decent service.
Keep on keeping on. Any development outfit that is trying to build things to give HIVE more utility even if in my opinions is not a great direction is still an ally to the community. /rant