Hive Dev Proposal #2

In mid-2024, we embarked on an exciting journey to contribute to the development of key Hive-focused tools and projects within the HAF ecosystem, working closely with @blocktrades' core development team.

We extend our sincere thanks to everyone who supported our previous proposal — your backing has been vital to our continued progress.

Quick Recap

Over the past year, our work has spanned multiple Hive projects, including:

• Hive Block Explorer (UI): A modern, user-friendly block explorer interface. We maintain a live instance at hivescan.info
• Balance Tracker: A HAF application that provides API endpoints for user account balances and transaction history on Hive.
• Health Checker: A visual React component for checking, fetching, and switching between Hive nodes.
• HAF Block Explorer: A HAF backend app exposing endpoints for transaction and operation data within Hive blocks.

We have maintained consistent transparency and communication with the community through several channels:

• Periodic blog posts showcasing progress (dev update 1, dev update 2, dev update 3, dev update 4)
• Monthly updates shared during Hive Core Dev meeting.
• Weekly highlights via Swarm of Swarms (thanks @hivetrending for the initiative and including our updates)
• by the hour? you could check gitlab as all is public :)

To highlight a few areas of last year's work: (you can check the above links for more details and further updates - also visit hivescan.info for block explorer UI related work)

• New all blocks page + live mode for dynamic updates
  
• Landing Page Revamp: to include many useful components and statistics, such as trx stats, hive price chart, communities...
• Hive Price chart: is now available as a default card component as part of the landing page just below the hive feed price that is also expandable to modal view.
  
• Tabbed views on user profile: To support easy access to user’s comments (& posts), we introduced comments tab that allows quick view and filtering of user content, that also links to the Interactions tab which allows visualizing the activity on a particular post/comment. All those tabs are now also bookmarkable and filtering is accessible via get links.
• Balance history page: Introduced the New User Balance history page and chart, utilizing new Balance Tracker endpoints to enable larger historical tracking and more data points availability.
  
• Bad Actors list: we integrated bad actors list so that warnings appear if a potential bad actors account is being viewed
• Vests / HP conversion: Supporting both displays comes in handy whether you're a user or a developer, so we integrated switching mechanisms and related settings.
• New Transactions statistics card and chart
  
• New Proposals page with related charts and filtering criteria
  
  
• New Communities page and supported communities display on account pages, alongside subscribers and other data.
• Voters List, Voters history, and many other charts as well as search capability for witnesses & proposals
  
• New raw single post page: This is essentially a replica of the old hiveblocks implementation of the single raw post page, including post/votes/comments and is accessible via the same structure as the standard hive post
• Witness page revamp + witness schedule support
• Vops Support: Add virtual operations to Transaction page and raw view of Block
• Export CSV functionality: Similar to other block explorers, we now support exporting the data all across the BE. Whether in the operations view, comments, or any other view, you can export the current results you have on the page.
• Introducing card-based components and display
  
• User profile page complete revamp: Example below showcasing new wallet card view.
  
• Extended account balances endpoint: Expand account balances API endpoint to include market orders and balances under conversion.
• Extended view for proxied accounts' votes under witness votes card, going down 3 layers deep to display votes of the proxied account (userA --> proxy A --> proxy B --> votes)
• New API endpoint for account proxy-ing users: Grab users who set a particular account as proxy. This is displayed as a user card under user's profile.
• Tokenize Block Explorer and include a language switcher supporting 10+ languages.
• Improve Health Checker display and functionality
• Layout Enhancements: Improving the layout, UX & UI across Block Explorer UI, including landing page, transactions page, user profile, witness schedule and others.
• New API endpoint for Hive's Richlist: This enables querying top holders according to their HIVE/HBD/HP or even savings balances. A related page is also now available as part of BE UI.

Over the past year, we have processed 320+ issues and 330+ merge requests, covering enhancements, bug fixes, new API endpoints, and community-driven feature requests.

We initially started with a team of 4 developers and, in recent months, expanded to include 2 additional members increasing our count to 6 developers.
This growth strengthens both our frontend and backend development capacity, enabling us to accelerate our work across the above HAF-based projects, and expand into new HAF-based initiatives where we see strong potential and community value.

We have an extensive roadmap ahead for above projects. This involves building more functionality into the Block Explorer UI with dynamic dashboards, richer user interactions, expanded reporting and analytics capabilities, integrations, user authentication and more. In parallel, we are also focused on developing new API endpoints to make this data more accessible and integrable across other Hive applications and tools as part of HAF.

Roadmap

In response to community feedback and growing interest, we are pleased to present a preliminary roadmap that highlights the next wave of functionality and innovation we currently plan to deliver across the HAF ecosystem projects within our development scope.

1- Block Explorer Customizable Modular Dashboard: (EDIT December 2025: This has been implemented now, will be visible once the authentication feature has been implemented)

This task features a new Dashboard that will transform the homepage into a dynamic, user-driven workspace where each user can fully tailor their experience.

Core Features:

1. View Toggle: Users can switch between the traditional static homepage and their personalized interactive dashboard.
2. Edit Mode: Enables users to move, resize, add, and remove widgets within a drag-and-drop grid layout.
3. Layout Persistence: Each user’s configuration is automatically saved (initially to local storage, later to their account once authentication is integrated).
4. Widget System: Existing homepage components (e.g., Market Info, Network Stats) will be refactored into independent, resizable widgets.
5. Widget Library: Users can open a gallery to browse available widgets, adding or removing them as desired.

More details here

2- Interactive Financial Sunburst View:

This feature will transform our current raw transaction lists into a powerful, intuitive, and visually stunning sunburst chart. By doing so, we will move beyond being a simple data utility to become an indispensable analysis tool for all Hive users.

This will allow users to:

1. See the Big Picture: Instantly understand the proportional breakdown of their financial activity (e.g., "45% of my activity is from Curation, 30% from Posting").
2. Drill Down for Details: Click on any category (e.g., "Posting") to smoothly zoom in and see a breakdown of the specific operations within it (e.g., author_reward, comment_benefactor_reward).
3. Analyze Specific Transactions: Click further on an operation type to see the individual transactions, posts, or comments that generated that value.
4. Navigate Intuitively: A simple "Back" button and breadcrumb trail will allow users to navigate up and down the data hierarchy with ease.

More details here

3- User Authentication & Personalization

Building on the success of leading block explorers such as Etherscan and BscScan, our goal is to elevate the Block Explorer into a fully interactive, user-centric platform—one that not only displays data but also empowers users to engage directly with the Hive blockchain.

To achieve this, we plan on introducing a multi-option authentication system that unlocks personalized access and on-chain functionality. This feature will enable users to log in and perform key blockchain actions seamlessly—voting for witnesses and proposals, casting content votes, claiming rewards, and more—all directly within the explorer interface.

More details here

4- Interactive RC Footprint & DApp Usage Dashboard

Create an interactive, visual dashboard summarizing RC usage per DApp, allowing users to easily see which apps, operations, or activities they use the most and/or consume the most resources.

Features Proposed:

1. Dynamic charts showing RC consumption by operation type, frequency, and app source.
2. Filtering and time-based views (e.g., daily, weekly, monthly).
3. Clickable segments linking to related transactions or operations for detailed inspection.
4. Integration with custom_json parsing to attribute RC usage to specific DApps.
5. Categorization of custom_json & proportional breakdown of activity into several core categories (Social Graph, Gaming, DeFi, etc.).

More details here

5- Interactive "Influence & Delegation" Map

Build an interactive visual map on the account page to represent influence relationships and delegation flows — who delegates to whom, how influence is spread, and how power is distributed across accounts.

Key Benefits & Value:

1. Enables users to visually explore their influence network, making delegation paths clear and intuitive
2. Helps users understand the impact of their delegations and whom they are influencing (directly or transitively)
3. Enhances transparency and engagement by turning raw delegation data into a meaningful, interactive graph

Feature Highlights:

1. Zoomable, clickable nodes and edges representing accounts and delegation links
2. Filtering options (e.g., show only first-degree delegations, indirect paths, weighted influence)
3. Tooltips and drill-down views to reveal more details about each delegation (amount, source, history)

More details here

6- Hive Reporting dashboard

Much like Ethereum’s Etherscan “Charts” section or Binance’s BscScan analytics, this dashboard will provide network-wide and user-level intelligence—powered by real-time data from the HAF backend (haf_block_explorer, balance_tracker, haf_stats, and related apps).

Key Features:

🟢 Network Health & Growth

• Daily Active Users (DAU) and Monthly Active Users (MAU) charts
• New accounts vs. deleted/inactive accounts trends
• RC (Resource Credits) utilization – overall and per category (posting, voting, etc.)
• Transaction throughput & block production statistics
• Witness activity, block latency, and missed blocks overview

💰 Economic Indicators

• Total Value Locked (TVL) combining Hive Power, savings, and liquid holdings
• Hive & HBD circulation supply over time
• Total transfer volume (incoming/outgoing) visualized by day or week
• Market-aligned charts showing Hive ecosystem value in USD terms
• Stake power distribution and voting weight concentration metrics

👥 User & Account Insights

• Per-account financial breakdowns (earnings, expenses, staking, rewards, delegation, etc.)
• Top active accounts (by transactions, curation, or authoring)
• Delegation analytics – incoming and outgoing HP and RC delegations
• Engagement analytics – comment/post frequency, voting activity, etc.

⚙️ Governance & Community Metrics

• Proposal vote distribution and participation rates
• Witness vote trends and ranking evolution
• Historical charting of key community actions and milestones

📊 Visualization & Interaction

• Dynamic, responsive charts
• Filtering and drill-down capabilities
• Exportable datasets
• Theming & modular widgets – allowing embedding of dashboard sections into other sites or apps

7- HAF Backend API Endpoints (haf_block_explorer/balance_tracker/haf_stats - new HAF app)

As part of expanding the Hive Application Framework (HAF) ecosystem, this component focuses on building a suite of new public API endpoints that expose critical blockchain data in a developer-friendly, standardized, and scalable manner. These endpoints will serve as the data backbone for both the Hive Block Explorer and any third-party dApps wishing to leverage real-time, high-quality network and financial data.

By integrating with the existing HAF-based services—haf_block_explorer, balance_tracker, and a new haf_stats module—the goal is to deliver transparent, efficient, and query-optimized APIs that empower developers, data analysts, and application builders across the Hive ecosystem.

Planned Endpoints and Capabilities:

• Daily Active Users (DAU)

• • Provides insight into real user activity across the Hive network.
• • Enables developers and stakeholders to monitor ecosystem engagement trends over time.
• • Will include daily, weekly, and monthly aggregation options for analytics dashboards and research tools.

• Total Wallet Addresses (Accounts)

• • Returns the total count of unique Hive accounts and their growth over time.
• • Supports chart-ready data for visualization of user base expansion and onboarding progress.
• • Aids ecosystem monitoring tools in measuring network adoption and participation metrics.

• Total Value Locked (TVL) (EDIT DECEMBER 2025: The API Endpoint has been implemented, will be available soon on HAF NODES)

• • Calculates the overall on-chain wealth in Hive Power, savings, and liquid balances.
• • Provides both chart-based data and USD-converted values through external pricing oracles.
• • Enables developers to integrate real-time economic indicators directly into dashboards and DeFi analytics platforms.

• RC Footprint per User

• • Returns categorized data on Resource Credit (RC) consumption by operation type (posting, voting, transfers, custom JSONs, etc.).
• • Useful for building user dashboards, wallet optimizers, or developer education tools.

• Financial Analysis per User

• • Aggregates and categorizes all on-chain operations per user into financial categories (earnings, expenses, staking, power-ups/downs, etc.).
• • Enables personal and institutional financial overviews, paving the way for portfolio analytics, DeFi dashboards, and tax-reporting tools.
• • Represents a first step toward building full financial intelligence layers on top of Hive data.

• Incoming RC Delegations

• • Lists all incoming RC delegations per user, including source and amount.
• • Can be extended to show historical trends and total delegated RC capacity.

EDIT: new Addendum below features 2 new HAF apps as part of our planned work)

8- HAF_CHAT HAF app (companion to @theycallmedan's work on Hive's Encrypted Discord)

To support the growing ecosystem of social communication on Hive, specifically the development of encrypted, decentralized chat applications (akin to a Web3 Discord) by @theycallmedan, we are expanding our planned work to include haf_chat.

While frontend interfaces handle encryption and user interaction, the backend requirement for a chat application is distinct from standard blogging operations. Chat requires instant retrieval of historical context, high-frequency updates, and complex relational querying (e.g., "Show me the last 50 messages in Channel B of Server A, sent between Users X and Y").

Querying the raw blockchain node for this data could be inefficient and slow. Therefore, we are designing haf_chat as a dedicated HAF application.

Architectural Design & Objectives

We have chosen the HAF architecture because it allows us to replay the entire chain history and index relevant custom_json operations into a standardized, high-performance PostgreSQL database, but also as HAF is well-positioned as a defacto standard for building HAF apps, while supporting decentralized serving of APIs across HAF API nodes.

Key Design Decisions:

1- Relational Data Modeling (PostgreSQL):
Unlike NoSQL solutions often used for raw feeds, chat applications rely heavily on relationships (Users ↔ Roles ↔ Channels ↔ Messages). We will implement a strictly typed tabular design that normalizes these relationships. This ensures data integrity and allows for complex joins that execute in milliseconds. As we are building on HAF, we're already utilizing PostgreSQL.

2- Protocol Standardization:
The success of haf_chat relies on a unified data structure. We will define the standard custom_json schemas for chat actions in alignment with design decisions and front end requirements. By standardizing these formats also at the HAF level, this allows the expansion to support other frontend developers to build a chat interface that is interoperable with the backend, preventing ecosystem fragmentation.

3- Optimized Historical Parsing:
The app will utilize HAF’s ability to efficiently parse historical block data. This means when a new user logs in, or a new UI is deployed, the full chat history is already indexed and ready for immediate retrieval—solving the "loading..." bottleneck common in decentralized apps.

Planned Deliverables for haf_chat:

We propose the following deliverables to build the backend backbone of Hive’s chat ecosystem (to be confirmed down the road in alignment with theycallmedan's extensible vision):

• Schema Definition: Design and implementation of the SQL schema to store:
  • Contexts/Communities: equivalent to Discord "Servers."
  • Channels/Rooms: Sub-categorization of contexts.
  • Membership & Permissions: Who can read/write in specific channels.
• Ingestion Engine: Developing the HAF sync logic to listen for specific custom_json IDs, validate the payload structure, and populate the PostgreSQL tables in real-time.
• High-Performance API Layer: Creation of API endpoints (via PostgREST/Python API) optimized for:
  • Infinite scrolling (cursor-based pagination).
  • Thread retrieval.
  • Global search (finding a message across all channels).
• Indexing Strategy: creation of specific database indexes to ensure that queries for "User X's participation in Group Y" return in sub-second timeframes, regardless of chain history size.

By delegating the heavy lifting of data management to haf_chat, we allow frontend developers to focus entirely on encryption implementation and UI/UX, significantly accelerating the timeline for a fully functional "Hive Discord."

That's correct. In a formal proposal aimed at stakeholders, the detailed math and granular metrics should be consolidated into a high-level summary to maintain clarity and focus on the strategic outcomes.

Here is the revised haf_fyp section, incorporating the core "ingredients of the algorithm" briefly and persuasively into the Planned Deliverables section.

9- HAF_FYP App: Decentralized Content Discovery Engine (FYP)

The next critical step for ecosystem growth is solving the Content Discovery problem. Current systems prioritize wealth and chronology; the community needs a high-performance, personalized For You Page (FYP) powered by algorithms to onboard new users and increase cross-community engagement, which could be served by any front end.

We propose developing HAF_fyp as a dedicated, open-source HAF application that will serve as the engine for all Hive frontends seeking a modern discovery feed.

Architectural Design & Objectives

This project will follow a Hybrid Open-Source Architecture built entirely on HAF components to ensure transparency, decentralization, and performance.

1. HAF-Centric Data Source: The application will use the HAF sync mechanism to index posts, comments, and votes directly into its PostgreSQL Database.
2. Leveraging HiveSense for Intelligence: We will integrate closely with the existing HiveSense HAF application. Our custom FYP Ranking Service will utilize HiveSense's semantic vector embeddings for deeper personalization.
3. Open-Source Algorithm: The core ranking logic will be open-source and auditable, focusing on quality and engagement.

Planned Deliverables for haf_fyp:

The initiative requires the development of three major software components and the integration of three existing HAF services:

• New Software Components to be Developed:

  • haf_fyp HAF App: A new HAF application responsible for data ingestion, metric calculation, and schema optimization.
  • FYP Ranking Service: The custom, open-source algorithm that generates User Profile Vectors and calculates the final weighted score, relying on the inputs listed below.
  • High-Performance API Layer: The public-facing endpoint (REST/GraphQL) that compiles the final post JSON and utilizes the Redis Cache for low-latency delivery.

• Existing HAF Services to be Integrated:

  • HiveSense HAF App: Provides the Semantic Vector Embeddings (Post Vector Similarity) for relevance scoring.
  • Balance Tracker HAF App: Provides up-to-date HP stake data for Author Authority scoring.
  • Redis Cache: Used by the Ranking Service to store the final ranked Post IDs for instantaneous retrieval by the API Layer.

CORE ALGORITHM INGREDIENTS (The Secret Sauce Summary - feedback welcome):

• The Open-Source FYP Ranking Service will use a Hybrid Weighted Model that calculates the final score for every post by combining four key metrics:

1. Engagement: Heavy weighting on Comment Volume and Reblogs, moderated by Net Value Score.
2. Recency: Uses an aggressive Time Decay Curve to prioritize content posted within the last 48 hours.
3. Authority: Filters for quality by using the author’s Staked HP and/or Reputation Score.
4. Semantic Relevance: The personalized factor, calculated by measuring the vector similarity between the user's historical activity (User Profile Vector) and the post's content (via HiveSense).

Key Benefits & Value:

• Scalable User Acquisition: Provides a familiar, low-friction content discovery experience for new Hive users, reducing initial churn, in addition to the history new, hot and trending streams.
• Enhanced Engagement: Increases the chances of users seeing relevant content outside of their immediate communities, fostering cross-pollination across the ecosystem.
• Democratization of Discovery: Shifts emphasis from stake-weighted visibility to genuine reader engagement (read time, comments, semantic relevance), boosting quality creators.
• Content Diversity & Virality: Introduces users to novel content they wouldn't have manually searched for (serendipitous discovery), which is key to finding content that can go viral within niche communities.
• Creator Retention: Provides a new, high-visibility distribution channel for mid-tier creators and new accounts, increasing their potential earnings and motivation to continue contributing content.
• Platform Stickiness: By continuously adapting to user behavior in real-time, the FYP delivers a consistently relevant experience, maximizing the average Time on Page and encouraging users to return daily to check their personalized feed.
• Reduced Information Overload: Algorithmic filtering sifts through the immense volume of daily Hive content, ensuring users are not overwhelmed and only see what is most valuable to their personal interests.

HAF_fyp, we believe, can provide the decentralized backbone necessary for Hive DApps to compete with centralized platforms on the critical metric of content relevance and user stickiness.

Proposal Ask

We are requesting 590 HBD/day (EDIT: In Alignment with reducing DHF Inflation footprint, we are downsizing team size/ask by 30% down to 415 HBD/day) to cover the payments to the team and related development infrastructure.

We're proud and grateful to help shape Hive's future by delivering open-source tools that empower developers to easily access blockchain data and build innovative applications on top of it.

We invite you to support our second-year proposal and help us continue improving Hive’s ecosystem.

Support This Proposal (360):

• Vote for our proposal on peakd
• Vote for our proposal on ecency
• Vote for our proposal on Hive wallet
• Vote for our proposal via hivesigner

Thank you for your continued support in helping us strengthen Hive and its growing ecosystem.

Hive Dev Team