oasisprotocol / oasisprotocol/explorer
[UX]: Total network data visualisation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 13
- Avg merge
- 58m
- Merged PRs (30d)
- 2
Description
IMPACT
- High
- Medium
- Low
URGENCY
- Critical
- Major
- Medium
- Minor
PRODUCT ENVIRONMENT
No response
DESCRIPTION OF ISSUE
From community:
Given the architecture, with consensus, core paratimes / OPL + custom paratimes (Pontus-X and more to come) all coming online — would it be possible to have the explorer capture total network traffic and active accounts and then break this down into respective components? I would be happy to build something like this for my own page but would be good to see this metric on the OPF explorer **forgot to add ROFL —— Plus, having this kind/s (would be good to treat many metrics this way) of compendium metrics available via the nexus API too so other sources can pick up on it, i.e. defilama etc
DEVICE / VIEWPORT
- Desktop
- Mobile
STEPS TO REPRODUCE
No response
ALTERNATIVES AND SUGGESTIONS
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by clarifying the definitions and sources for total traffic, active accounts, and component breakdowns; done would require these metrics to be visualized in the explorer and made available through the Nexus API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, blockchain, data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100