Already the thing with the 4 different pair of keys is putting people off. Let alone such a complicated scheme. People always forget, for mass adoption interfaces need to be accordingly stupid. I prefer a dumbed down version which is truly user friendly (but brings Hive to 2$) vs. a high-end version for nerds only.
You are viewing a single comment's thread from:
I support adding stuff like this both for investors and to draw more investors to Hive, but yeah, working on the dumbing down part to draw the general public seems like it should take the priority.
100% of the complexity would be back-end only.
A simple UI would allow anyone with $HBD in their wallet to bid on and/or purchase $HBD Bonds. Similarly, a secondary market for trading those bonds would not require any expertise beyond a general understanding of bond markets.
Investors familiar with bond markets would have no issues, with the primary or secondary markets.
The purpose here is not to get existing Hivers to invest in $HBD. The intention is to add an investment use case that is very familiar to a wide range of investors, and to do it in a way that allows the witnesses to focus on managing a metric (TVL) that is more straight forward and much more likely to ensure long-term stability, compared to managing APY.
Hive's multiple private keys is probably one of its greatest strengths.
Even so, onboarding is certainly a big challenge, and will remain so for the foreseeable future.
This added use case ($HBD Bonds) is not geared toward average users, though. This would be meant to appeal to accredited investors and investors who are used to paying advisors and consultants to handle the day-to-day details associated with their investment portfolios.
One thing is potential target of such system, the other is potential influence on other users. If it won't be possible to explain easily, it's going to be seen as old fashioned shady financial shenanigans. It's about perception here. Explaining Hive tokenomics to an avarage person right now is borderline possible.
Let's weight costs and benefits here.
Although, I need to add, personally I find proposed solution appealing.