RE: RE: Hive Technical Vision
You are viewing a single comment's thread from:

RE: Hive Technical Vision

Words
277
Reading
2 min
Listen
Play
6y

The document will be used as a one-sheet statement piece and potentially leveraged for marketing purposes. This is aimed at developers but can be paraphrased for non-technical readers.

Alrighty. Been clamoring for this left and right.
Thats the first step. Second step is to condense it into a easily spread message and broadcast it.

First and second layer of plugins that allow for functionality without adding bulk to the blockchain itself.

I feel this is a very important point that needs to be expanded on. If you feel this document is not the place for it, id like to see a more comprehensive breakdown and comparison to industry standards and why this solution is superior.
Im not talking a post or a github document but rather places like Hive.io or hiveonboarding.

SMTs and similar would go here.

Im personally not happy with the lack of mention of SMTs. I feel theyre an essential tool to achieve this vision and should get a line of their own in there.

Sidenote:

The thing devs need to understand is that PRICE is a huge factor when it comes to survival of a project. In the simplest of ways put:
"If you dont built that which directly creates demand in economic terms for the token (especially a inflationary one) but focus mostly on creating convenience there wont be monies for you to get payed."

It wont matter how convenient it is to build a dapp on HIVE if the price is 0.
Every system needs to create a incentive to buy HIVE. Otherwise, in that sense, what can happen is that a system can be "useful" and "worthless" at the same time.