mimblewimble/grin

Identify and ban total proof of work cheats

Open

#1,139 opened on Jun 5, 2018

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Rust (991 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (4,876 stars)
PR merge metrics
 (Avg merge 6d 11h) (25 merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Investigate the header sync process and identify where total difficulty is trusted. Implement validation of headers against claimed total difficulty and ban peers that fail to provide matching headers.
Tech stack
rust
Domain
backendblockchain
Issue type
Bug
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-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustBlockchain concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40