Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Gwen Dashboard v2

Open
#89 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale

Research direction

Start with the Gwen Dashboard page and the linked Previous Dashboard research document, then identify which live Sandbox data is available for the requested metrics. Done means the Flows menu item is hidden, the account, token, transaction, chart, and table views use live data, and the result is demoed.

Written by the indexing model from the issue text.

Description

backend gwen story ui

Description: Currently we are using mock data on this page, we want a live Sandbox version.

Previous Dashboard research: https://docs.google.com/document/d/1EnN4pswiPu-zjhkohtS1_oYqx2FbpZZ1KHKm5JtRuwY/edit?usp=sharing

ROI: Getting feedback on Sandbox Gwen from the Alpha Cohort will be valuable for informing required changes and future features.

As a user, I want to view information about the Manifest network and its usage so that I stay informed.

  • Should hide Flows from left side menu.
  • Should display the number of accounts.
  • Should display the number of token symbols.
  • Should display the total number of transactions.
  • Should display transaction volume chart.
  • Should display token balances table.
  • Should display recent transactions table.
  • Should be demoed.

Notes:

  • Team should review what can be display now.
  • Possible additions include: median response time (5min), successful requests % (24h), number of invalid requests, and daily requests chart or other network metrics.
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from liftedinit/roadmap

All issues in liftedinit/roadmap

Similar issues

More Data Visualization issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.