Account Page: Feature Ticket: Interactive RC Footprint & DApp Usage Dashboard
Summary
This ticket outlines the development of a market-leading Interactive "RC Footprint" Dashboard. This feature will visualize a user's custom_json activity, transforming an opaque, technical transaction list into an insightful and intuitive Donut chart. This will provide users with an unprecedented understanding of their on-chain behavior and Resource Credit (RC) consumption.
1. User Story and Workflow
As an active Hive user,
I want to visualize my custom_json activity in an interactive, drill-down chart,
so that I can easily understand which applications I use the most and where my valuable Resource Credits (RCs) are being spent.
Step 1: The Initial View - The Big Picture
The user navigates to the new "RC Footprint" section. They are immediately presented with a clean, high-level overview of their activity for the last 30 days. The dashboard contains three key elements:
- KPI Cards: At the top, a series of cards display the most critical metrics: "Total custom_json Operations," "Top Category (e.g., Gaming)," and "Top DApp (e.g., Splinterlands)."
- The Category Donut Chart: On the left, a large, vibrant donut chart shows the proportional breakdown of their activity into our 9 core categories (Social Graph, Gaming, DeFi, etc.).
- The Initial Bar Chart: On the right, a bar chart initially shows a breakdown of the Top Category. For example, if "Gaming" is the top category, the bar chart will show the breakdown of operations between Splinterlands, dCity, Rising Star, etc.
Step 2: The Interaction - Exploring a Category
The user is curious about their "DeFi & Tokens" activity. They move their mouse and click on the "DeFi & Tokens" slice of the donut chart.
Step 3: The Insight - The Dashboard Responds
Instantly, the dashboard comes to life:
- The "DeFi & Tokens" slice in the donut chart is highlighted.
- The bar chart on the right smoothly animates and updates. It now displays a new set of data: the breakdown of operations within the DeFi category, showing bars for Hive Engine, dLease, LeoDex, etc.
Step 4: The Granular Detail - Connecting to Raw Data
After analyzing the breakdown, the user wants to see the actual transactions. Below the bar chart is a simple button: "View All 'DeFi & Tokens' Transactions." Clicking this link takes them directly to the existing "Operations" tab, which is now pre-filtered to show only the relevant custom_json operations for that category within the selected date range.
2. Technical & Implementation Details (High Level)
-
Backend API: A new endpoint (GET /api/v1/accounts/{username}/rc-footprint) is needed.
- The API response will be a structured JSON object containing the aggregated data needed for the KPI cards, the donut chart, and all possible breakdowns for the bar chart. This allows the frontend to be extremely fast, as it doesn't need to make new API calls when the user clicks a donut slice.
-
Frontend Development:
- Charting Library: We will use ECharts for React (or our existing Recharts library, as both excel at donut and bar charts).
- State Management: The component will manage the "selected category" state, which will control which data is displayed in the dynamic bar chart.
3. Categorization System (The Blueprint)
The exhaustive research has produced a definitive, 9-category system for classifying all custom_json activity. This is the core intelligence of the feature. Also there is a list of Dapps https://hive.io/eco/
The Final Blueprint: Definitive Categorization System with id Examples. These are just examples and the API implementation team might find other ways to fetch the categories and IDs
Category |
Description |
How It's Identified (The Logic) |
Key id Examples Discovered During Scans |
Social Graph |
Core, protocol-level social actions. The foundational layer of on-chain social life. |
Stage 1 Decoder: Hard-coded rules. |
follow, reblog, community |
Social Front-Ends |
Platform-specific actions from major social interfaces (notifications, settings, image uploads). |
Stage 2 Decoder: Registry lookup. |
peakd, ecency, notify, liketu, dapplr |
Gaming |
All interactions with Hive-based games and their associated token/asset ecosystems. |
Stage 2 Decoder: Registry lookup. |
splinterlands, sm_, risingstar, dcity, rabona, dcrops, terracore, hashkings, psyberx, cryptoshots, ragnarok.game, holybread, neoxian_city |
DeFi & Tokens |
All interactions with Hive Engine, tribe tokens, and second-layer financial protocols (leasing, liquidity pools, bridges). |
Stage 2 Decoder: Registry lookup. |
ssc-mainnet-hive, hive-engine, scot_claim_token, leodex, dlease, beeswap, tribaldex, archon, hbdstabilizer_, cinetv, pimp, neoxag, waiv |
NFTs |
All interactions with NFT marketplaces for minting, buying, selling, or transferring NFTs, including VR/AR assets. |
Stage 2 Decoder: Registry lookup. |
nft, nftmart, nftshowroom, dlux, nftt |
Media & Content |
Interactions with specific content platforms, like video, microblogging, or specialized blogging front-ends. |
Stage 2 Decoder: Registry lookup. |
3speak, dbuzz, engrave |
Community & Social DApps |
Interactions with specialized social DApps, curation services, and community tools. |
Stage 2 Decoder: Registry lookup. |
curangel, posh, actifit, ocd, travelfeed, hivetasks |
Governance & Infrastructure |
Actions related to managing account resources, developer tools, and core network/governance protocols. |
Stage 2 Decoder: Mix of rules and registry. |
rc, spk.cc, hive-keychain, hiveonboard, vsc.network, podping, inji, witness_set_properties (if custom_json) |
Uncategorized |
Operations with an id not found in our decoders. The goal is to keep this slice minimal. | The fallback. | some_new_app_id, testing_id_123 |