Fast block confirmation (N-Blocks irreversibility)

[abitmore]

User Story

Recently the Hive project implemented One-Block Rrreversibility (OBI) through the 26th protocol upgrade (hard fork).

While in theory it may not be perfect, in practice it makes great sense (IMHO), especially for business use cases.

We can probably try to port it to BitShares, although the code about voting and witness schedules is quite different between Hive and BitShares.

Actually, I have been thinking about doing something like this (and others) on the P2P layer for a long time, starting around 2016.

(This may or may not be a protocol upgrade.)

Additional Context (optional)
There were discussions about BFT over DPoS on EOS but I don't know if it's finally delivered.

• https://github.com/KryptonWorld/bftDpos/blob/master/README.md

Impacts
Describe which portion(s) of BitShares Core may be impacted by your request. Please tick at least one box.

• API (the application programming interface)
• Build (the build process or something prior to compiled code)
• CLI (the command line wallet)
• Deployment (the deployment process after building such as Docker, Travis, etc.)
• DEX (the Decentralized EXchange, market engine, etc.)
• P2P (the peer-to-peer network for transaction/block propagation)
• Performance (system or user efficiency, etc.)
• Protocol (the blockchain logic, consensus, validation, etc.)
• Security (the security of system or user data, etc.)
• UX (the User Experience)
• Other (please add below)

CORE TEAM TASK LIST

• Evaluate / Prioritize Feature Request
• Refine User Stories / Requirements
• Define Test Cases
• Design / Develop Solution
• Perform QA/Testing
• Update Documentation