bitshares / bitshares/bitshares-core
Implement DPOS BFT— Pipelined Byzantine Fault Tolerance
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 660
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 26
Description
**User Story**
As a `Consensus Protocol` I want `to ensure the network will not fall out of consensus` due to `conflicting last irreversible blocks`.
**Additional Context (optional)**
eosio/eos/#2718 Describes the need to harden DPOS Protocol
Dan Larimer later wrote about the implementation of [DPOS BFT](https://medium.com/eosio/dpos-bft-pipelined-byzantine-fault-tolerance-8a0634a270ba) within EOSIO
## CORE TEAM TASK LIST
- [ ] Evaluate / Prioritize Feature Request
- [ ] Refine User Stories / Requirements
- [ ] Define Test Cases
- [ ] Design / Develop Solution
- [ ] Perform QA/Testing
- [ ] Update Documentation
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked eosio/eos#2718 issue and the referenced DPOS BFT article to understand the consensus requirements. Define the conflicting-last-irreversible-block scenarios and test cases before locating the consensus implementation in this repository. Done means the design, implementation, QA coverage, and documentation tasks are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100