mimblewimble/grin

Chain split monitoring tool

Open

#3,008 opened on 2019年8月29日

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

説明

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"?

コントリビューターガイド

技術スタック
rust
領域
securityblockchain
Issue 種別
research
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Understanding of Mimblewimble protocolRead RFC 0003Familiarity with chain split concepts
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
35
調査方針
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.