mimblewimble/grin

Chain split monitoring tool

Open

#3008 opened on Aug 29, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (4,876 stars) (991 forks)batch import
help wantedneeds more infoquestion

Description

The current language in SECURITY.md mentions a yet to be built software:

The Grin Team runs a chain split monitoring tool at (TBD). It is encouraged to monitor it regularly and setup alerts. In case of an accidental chain split:

  • Exchanges and merchants should either cease operation or extend considerably confirmation delays.
  • Miners and mining pools should immediately consult with Grin's development team on regular channels (Grin's Gitter mainly) to diagnose the split and determine a course of events.
  • In the likely event of an emergency software patch, all actors should upgrade as soon as possible.

Raising this issue as this Chain Splits section is set to be removed from SECURITY.md in the implementation of RFC-0003.

Do we still plan to build the "chain split monitoring tool"?

Contributor guide

Tech stack
rust
Domain
securityblockchain
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of Mimblewimble protocolRead RFC 0003Familiarity with chain split concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the current status of the chain split monitoring tool referenced in SECURITY.md. Review RFC 0003 (text0003 security process.md) to understand the intended removal of the Chain Splits section. Check repository history or related issues for any progress on building the tool. Provide a recommendation on whether the tool should be built or if the section should simply be removed.