Implement DPOS BFT— Pipelined Byzantine Fault Tolerance

ryanRfox commented 5 years ago

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 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

pmconrad commented 5 years ago

Related: #831

clockworkgr commented 5 years ago

Actually it seems EOS has not implemented BFT either (!!!).

Current version is not using BFT consensus: https://github.com/EOSIO/eos/issues/4965#issuecomment-410049124

and the relevant development issue has been blocked since April(??): https://github.com/EOSIO/eos/issues/2192

FWIW: This probably means that time to irreversibility is TWICE as long on EOS than BitShares for the same number of BPs/witnesses since BPs rotate every 6 seconds on EOS (12*0.5s) compared to every 3 on BitShares.

bitshares / bitshares-core

Implement DPOS BFT— Pipelined Byzantine Fault Tolerance #1144

CORE TEAM TASK LIST