Computing went from single --> connected --> central --> decentral (without central authority)
Internet nature are decentralised, hence comes the security problem.
The old internet use permissioned access to achieve security.
Classic BFT systems could only reach deterministic consensus only if less than 1/3 of all the nodes were malicious (and was applied for 3 decades)
Bitcoin consensus probabilistically guaranteed trustless consensus in a permissionless setting in the presence of less than 50% of byzantine nodes (a huge improvement over the less than 1/3 allowed by BFT systems and its variants at the time)
Others are using synchronous BFT, e.g. an optimized version of practical Byzantine Fault Tolerance (optimized pBFT) as used in Zilliqa¹⁴, delegated Byzantine Fault Tolerance (dBFT) as used in Neo blockchain¹⁵, and PoS BFT as implemented in EOS blockchain. --> unsuitable for TRULY permissionless blockchain settings where “network links can be unreliable, network speeds change rapidly, and network delays may even be adversarially induced
Asynchronous Byzantine Fault Tolerance: A Time-independent & Future-proof Byzantine Fault Tolerance for the Brave New World | by Crypto Insights | Medium.pdf
https://medium.com/@crytpol_25852/asynchronous-byzantine-fault-tolerance-a-time-independent-future-proof-byzantine-fault-f6f1a4d1f17a
Computing went from single --> connected --> central --> decentral (without central authority)
Internet nature are decentralised, hence comes the security problem. The old internet use permissioned access to achieve security.