You are viewing a single comment's thread from:

RE: Hive Dev Proposal #2

View the full context View the direct parent

Ok great, I'll come back to that page tomorrow then. With regard to your proposal - the cost of development is more controversial than ever now, partially due to AI tools typically increasing productivity by 10x, 20x or even more.

The amount you are asking for is roughly about the amount charged by a single pro developer per day (in the UK - at the bottom end of the market rate) - so it's not unreasonable, especially if you have multiple team members.

My main thought about the proposal relates to alignment and optimisation of the proposed features:

Marky has already got his analytics project funded (for a high price) - so I'm not sure I can justify having two projects with such similar goals being funded - especially when they aren't really even core features or selling points.
For me, I think most of the other features are 'nice to haves', rather than necessary for any realistic growth goals for Hive as a whole. I am not opposed to them, but wonder if there are some other more pressing needs.

Personally, I would MUCH rather see funding pointed at support for L2 community protocols being developed on VSC or tools to support onboarding via checkinwith.

Have you thought about adding features to help with onboarding? Such as tracking retention over 30 days and quantifying the quality of new accounts? That would be a huge benefit for growth on Hive generally.

Cheers

·inHiveDevs·by

$0.02

Sort:

Thank you @ura-soul for the thoughtful feedback! (did not see those downvotes either, possibly a glitch I agree, don't worry about them)

Yes we currently have a team of six developers, several of whom have been working for years on HAF-based development, so they bring strong experience and efficiency to the table.

Regarding the proposed features, while we shared a short-term roadmap, some of the items you mentioned are indeed among the directions we plan to prioritize. In particular, integrating VSC data and smart contract interaction is something we’ve already been exploring. As the smart contract layer on Hive matures, we envision the Block Explorer evolving similarly to how Etherscan or BscScan allow users to view and interact with contracts directly on-chain.

On the L2 side, we've also been discussing new reports and endpoints to surface L2-related data and activity, which ties nicely into your suggestion for supporting L2 protocols / VSC.

As for analytics, we absolutely value the great work Marky has done — and our goal isn't to duplicate but to complement. Our focus has been on:

Providing open-source, decentralized APIs as part of HAF nodes, enabling anyone to access, host, or extend the same data.
Building analytics that can drive real economic visibility on Hive — things like DeFi metrics (Total Transfer Volume, TVL, Trading Volume, Per-Account Financial Summaries), as well as user-centric insights (Daily Active Users, Inactive/Returning Accounts, etc.).

Your idea around onboarding and retention tracking is excellent — measuring 30-day retention, new account quality, and engagement flow would be highly valuable. These could indeed be new API endpoints and visual cards on the explorer’s dashboard, helping quantify user growth and Hive’s funnel performance.

Again, really appreciate your input — much of our current work has evolved directly from community suggestions, and we’re always open to aligning new features with what Hive needs most.

$0.00