mimblewimble/grin

Chain split monitoring tool

Open

#3,008 建立於 2019年8月29日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Rust (4,876 star) (991 fork)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
議題類型
research
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
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.