Skip to content

Implement DPOS BFT— Pipelined Byzantine Fault Tolerance #1144

New issue
New issue
Open
Open
Implement DPOS BFT— Pipelined Byzantine Fault Tolerance#1144
Labels
1a EpicHigh level concept to be addressed. Description should contain a list referencing child User Stories2a Discussion NeededPrompt for team to discuss at next stand up.3c EnhancementClassification indicating a change to the functionality of the existing imlementation6 ProtocolImpact flag identifying the blockchain logic, consensus, validation, etc.6 SecurityImpact flag identifying system/user securityhardfork
Milestone
 
Future Protocol Upgrade Release
@ryanRfox

Description

@ryanRfox
ryanRfox
opened on Jul 16, 2018

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    1a EpicHigh level concept to be addressed. Description should contain a list referencing child User Stories2a Discussion NeededPrompt for team to discuss at next stand up.3c EnhancementClassification indicating a change to the functionality of the existing imlementation6 ProtocolImpact flag identifying the blockchain logic, consensus, validation, etc.6 SecurityImpact flag identifying system/user securityhardfork

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions