mimblewimble/grin

Identify and ban total proof of work cheats

Open

#1,139 创建于 2018年6月5日

在 GitHub 查看
 (4 评论) (0 反应) (0 负责人)Rust (4,876 star) (991 fork)batch import
enhancementhelp wanted

描述

During header sync, we trust the total difficulty given by peers during the handshake to select who to get headers from. This is easy to lie about. We need to identify when a node fails to send us headers to match that total difficulty and ban them.

贡献者指南

技术栈
rust
领域
blockchain
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
RustMimblewimble protocolGrin's p2p header sync
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
The issue requires implementing a mechanism to detect when a peer provides an inflated total difficulty during header sync. Start by examining the header sync code in `src/peers/handler.rs` and the handshake protocol. Check the existing ban logic in `src/peers/peer.rs`. The goal is to verify that the total difficulty sent in the handshake is consistent with the headers subsequently provided. If the peer fails to deliver headers that match the claimed difficulty, they should be banned. Look at comments and previous PRs for any related work.