onflow / onflow/flow

Status page for Mainnet

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

Nobody has claimed this yet.

Developer Tool Team Docs Site Feature Feedback
Dominant language
Go
Stars
361
Forks
159
PR merge metrics
No merged PRs in 30d

Description

Issue To Be Solved
  • More detailed information about the status of the mainnet spork
  • Historical/upcoming spork dates and other information needs to be added on the status-page in order to eliminate the need for developers to reach out to the team to get this information.
(Optional): Suggest A Solution

Break out the Mainnet status page into it's own, and provide the following information in addition to what is already there:

  • Upcoming mainnet spork

    • Sub-section - announcement
  • Spork updates (a run-time view of what is happening with the spork)

  • Mainnet network

  • State extraction

  • Root snapshot generation

  • Bringing up nodes on the new network

  • Uploading root snapshot for partners

  • Spork Complete

These status should be updatable via a curl command so as to make it easy to update during spork.
e.g. curl "http://someurl/sporkupdate/status/3"

e.g.

  • Mainnet network stopped ✅
  • State extraction ✅
  • Root snapshot generation ✅
  • Bringing up nodes on the new network ✅
  • Uploading root snapshot for partners [in progress]
  • Spork Complete

Contributor guide

Open the contributing guide

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

No files, tests, or entry points are identified. Start by locating the existing status page and the mainnet spork workflow, then determine how status updates could be exposed through the proposed curl endpoint. Done should include the listed spork stages, upcoming and historical information, and an independently updateable status view.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.