title: Byzantine fault tolerance (BFT) and Crash fault tolerance (CFT)
body: <p>Crash fault tolerance (CFT) is one level of resiliency, where the system can still correctly reach consensus if components fail. While Byzantine fault tolerance (BFT), which says the orderer can do its job even in the presence of malicious actors. Below are my questions</p>
  
  <ol>
  <li><p>CFT is more useful for single enterprise. Presently Hyperleger Fabric uses Kafka which is CFT. Even in the case of multiple organization we are using Kafka in Hyperledger Fabric network. Does it mean still we are using CFT? </p></li>
  <li><p>In CFT, How system can still correctly reach consensus if components fail? For example network is down, or malcious node present in system etc </p></li>
  <li><p>Can CFT work even in presence of malicious actor?</p></li>
  <li><p>How Hyperledger Fabric implements BFT? When will they release it?</p></li>
  <li><p>What is the main difference between CFT &amp; BFT?</p></li>
  </ol>