Distributed systems now have a traditional consensus approach that focuses on building fault tolerance in the face of unreliable systems, provisioning mainly for fail-stop faults. Some examples of the Byzantine General's Problem are Paxos, Raft, and Viewstamped replication. The traditional consensus approach is used for putting an order of transactions in the distributed databases, to order client-generated requests and other respective stage changes which take place in distributed applications by using replicated state machines. The number of nodes needed in such networks is 2 f + 1 to be able to tolerate f fail-stop failures. Tolerating Byzantine faults increases the complexity of the consensus protocol by adding several extra layers of messaging to the system. All these solutions carry overhead and add more complexity, making them practically impossible.