Byzantine node simulation
Open
- Dominant language
- Go
- Stars
- 36
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Hi @bobg ,
Interesting project you have here!
Does your code also simulate byzantine / faulty nodes? The protocol itself probably handles it, but I am wondering about the tests. Would it be hard to add a faulty node test, maybe in the `lunch.go` sample code?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the `lunch.go` sample code and the existing protocol tests, if present, to understand how nodes are simulated. Define the faulty-node scenario and expected consensus behavior before adding a test; done means the test reliably demonstrates how the protocol handles Byzantine behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100