Each month at least one new consensus (consensus protocols) is being introduced to community. There are a lot of reviews and analyses, but all of them do use not one methodology. It is difficult to compare consensuses without structured approach. I am proposing my vision (and of course comparison) how to analyze different consensuses.
I have tried to combine the most important aspects. Of course this list could be extended, but will cause difficulty in information perception.
- What is kind of protocol?
- What is maturity of protocol?
- Who should produce the next block of updates to apply to the database?
- When should the next block be produced?
- What transactions should be included in the block?
- How are changes to the protocol applied?
- How should competing transaction histories be resolved?
- How should blockchain forks be resolved?
- Are smart contracts supported?
- How is side-chains inter-operating implemented?
- How is performance changing on growing number of nodes?
- What is limit of nodes in consensus?
- What is block producing interval?
- What is period of irreversibility (99.99%, 10% Adversary)?
- How much is transaction fee?
- Nothing-at-Stake
- incentives for nodes to vote on the correct block
- Failure
- ability to reach consensus
- Sybil attacks
- a single adversary is controlling multiple nodes on a network
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent