Autochecked users, Bureaucrats, Editors, Interface administrators, Project members, Push subscription managers, Reviewers, Suppressors, Administrators, Widget editors
5,802
edits
Byzantine fault tolerance: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
| [checked revision] | [checked revision] |
CryptoUser (talk | contribs) m (CryptoUser moved page Commoninfo:vizantyfaulttolerance to Byzantine fault tolerance) |
CryptoUser (talk | contribs) mNo edit summary |
||
| Line 6: | Line 6: | ||
}} | }} | ||
[[File:Art Problem of Byzantine generals.jpg|400px|right|thumb]] | [[File:Art Problem of Byzantine generals.jpg|400px|right|thumb]] | ||
'''Byzantine fault tolerance''' is a property of a system capable of resisting a class of failures arising from the | '''Byzantine fault tolerance''' is a property of a system capable of resisting a class of failures arising from the «problems of Byzantine generals». Having «Byzantine fault tolerance», the system can continue to work even if some of the nodes do not function or act maliciously. | ||
The participants of the [[cryptocurrency]] [[network]] need to regularly coordinate the current state of the [[blockchain]]: this is what we call achieving [[consensus]], but what if some of the [[node]]s act dishonestly? This is a fundamental question about the so-called «problem of Byzantine generals», which gave rise to the concept of «Byzantine tolerance» (BFT). | The participants of the [[cryptocurrency]] [[network]] need to regularly coordinate the current state of the [[blockchain]]: this is what we call achieving [[consensus]], but what if some of the [[node]]s act dishonestly? This is a fundamental question about the so-called «problem of Byzantine generals», which gave rise to the concept of «Byzantine tolerance» (BFT). | ||