oasisprotocol / oasisprotocol/explorer

[Feature]: Mark data from previous network generations

Open
#2,067 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
TypeScript
Stars
13
Forks
13
Avg merge
58m
Merged PRs (30d)
2

Description

Is there an existing issue for this?
  • I have searched the existing issues
SUMMARY

The blocks from previous network generations can be annotated

DESCRIPTION

The data (e.g., blocks) from previous network generations/milestones/upgrades (e.g, Cobalt, Damask) could be marked/annotated in Oasis Explorer to distinguish them from the current network generation (Eden). This would simplify the search for users who are interested specifically in historical data.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by tracing how Oasis Explorer displays blocks and identifies the current network generation, then inspect the search or filtering entry points relevant to historical data. Confirm where generation metadata is available and define done as historical blocks being visibly distinguishable from Eden blocks without disrupting current-data browsing.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
blockchain, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.