You are viewing a single comment's thread from:

RE: My Take on Hive Proposal System – Analysis of Current Situation, Brainstorm and Questions (and as It Turned Out a Bit of History and a Marketing Announcement)

in OCD4 years ago (edited)

Hivesigner proposal is for more than 2 years and roadmap of things that will be implemented is listed in proposal: https://github.com/ledgerconnect/hivesigner/issues/2

It is long term maintenance and iterative improvement proposal, so money is spend for hosting hivesigner service which is used by many apps plus improve and add new changes. Proposal has Edit section to give update on progress. Also investors or voters should know person trustworthiness through actions and delivered products.

Sort:  

I’m glad that you responded @good-karma but unfortunately you have not answered the core questions. I have of course checked all the available data you have provided and I have never stated that your roadmap doesn’t make sense.

Let me highlight the core questions that remain unanswered:

  • What does Hivesigner bring to the table compared to Keychain that has already been funded?
  • How much exactly is needed for the maintenance and how much goes straight to you for how many hours of work (as it seems like you’re the sole developer)? Where are the calculations? Where are man-days estimates?
  • I find the fact that proposal is supposed to last for 2 years kinda irrelevant. What is relevant is that you’re asking for money that basically covers full-time job during this time. Therefore I think that the community deserves VERY detailed information and business case for a product that seemingly is already in place...

I mean none of this in a bad way. I am GENUINILY interested in those answers. My sole intention is to make good use of the funds we have at our disposal and to make the proposals look professional from more than just “roadmap standpoint”.

  1. Main difference between Keychain and Hivesigner, is that Hivesigner not only chrome extension, it is OAuth2 authentication system that is industry standard for any mobile and web applications.
  2. Funds are used for ~40 hours of development plus server costs per months.
  3. Current state of the product is far from perfect, so goal is to not only improve it but also improve onboarding and ease of login, library maintenance, integration help/support, across all Hive apps. There will be tools and services that also help users sign transactions easily.

So essentially Hivesigner has 2 goals:

a) Developers, onboarding, offering them tools and services to integrate Hive into their apps easily.
b) Users, safe and secure transaction signing

I am going to add these notes to original proposal as a side note hopefully will clarify some/future confusions.

Thanks for the civil reaction and a more in-depth explanation! Yes I think that it would be a good idea to implement those not notes into the proposal so users can make more educated decisions.