Byzantine Fault Tolerance (BFT)

A preventive counteraction against malicious attacks and software errorsHow in the world of decentralized digitization everything function accordingly within an ecosystem without an authority? What if a node intended to misbehave or just fell asleep and failed to act on an important message?Of Nodes, Peers, and ConsensusThe invention of the blockchain allowed for the trustless and permissionless functioning of subsequent digital creations such as cryptocurrencies, defi’s, and fintechs. To participate, a computer called a node or peer must follow the rules of the blockchain in a network, called a protocol. All other nodes rely on the protocol to make the general intent happen so that the goal is achieved. The decentralized system of the blockchain makes every node equal to each other, without a node having more power than the others. All they have to do is to agree to reach a consensus of following the protocol in order for all to enjoy its benefits. So as long as the majority rules where those who agree are greater than those who disagree. The protocol continues to function. But since there is not a manager or police to correct the inevitable failure, disobedience, or disagreement of some peers or nodes to the consensus, the Byzantine Fault Tolerant (BFT) was introduced into the blockchain system to keep it running despite the inevitables.The Byzantine Fault Tolerant (BFT)The concept of the Byzantine Fault Tolerant was borne out of the inspiration from the 1982 Byzantine General’s Problem paper published by Leslie Lamport, Robert Shotak, and Marshall Pease. It alludes to the hardships of achieving consensus within a decentralized ecosystem. Before an impending battle, the Byzantine generals who are in command of their own army battalions and are manning different locations around the city they intend to attack need to reach an agreement.-They can only agree…