cases. Introduction What’s new in v1.4 Release notes Key Concepts Getting Started Developing Applications Tutorials Operations Guides Commands Reference Architecture Reference Frequently Asked Questions same characteristics as Bitcoin but adding smart contracts to create a platform for distributed applications. Bitcoin and Ethereum fall into a class of blockchain that we would classify as public permissionless org/wiki/Fault_tolerance] (CFT) consensus protocol might be more than adequate whereas, in a multi-party, decentralized use case, a more traditional byzantine fault tolerant [https://en.wikipedia.org/wiki/Byzantine_fault_tolerance]

cases. Introduction What’s new in v1.4 Release notes Key Concepts Getting Started Developing Applications Tutorials Operations Guides Commands Reference Architecture Reference Frequently Asked Questions same characteristics as Bitcoin but adding smart contracts to create a platform for distributed applications. Bitcoin and Ethereum fall into a class of blockchain that we would classify as public permissionless org/wiki/Fault_tolerance] (CFT) consensus protocol might be more than adequate whereas, in a multi-party, decentralized use case, a more traditional byzantine fault tolerant [https://en.wikipedia.org/wiki/Byzantine_fault_tolerance]

cases. Introduction What’s new in v1.4 Release notes Key Concepts Getting Started Developing Applications Tutorials Operations Guides Commands Reference Architecture Reference Frequently Asked Questions same characteristics as Bitcoin but adding smart contracts to create a platform for distributed applications. Bitcoin and Ethereum fall into a class of blockchain that we would classify as public permissionless org/wiki/Fault_tolerance] (CFT) consensus protocol might be more than adequate whereas, in a multi-party, decentralized use case, a more traditional byzantine fault tolerant [https://en.wikipedia.org/wiki/Byzantine_fault_tolerance]

cases. Introduction What’s new in v1.4 Release notes Key Concepts Getting Started Developing Applications Tutorials Operations Guides Commands Reference Architecture Reference Frequently Asked Questions same characteristics as Bitcoin but adding smart contracts to create a platform for distributed applications. Bitcoin and Ethereum fall into a class of blockchain that we would classify as public permissionless org/wiki/Fault_tolerance] (CFT) consensus protocol might be more than adequate whereas, in a multi-party, decentralized use case, a more traditional byzantine fault tolerant [https://en.wikipedia.org/wiki/Byzantine_fault_tolerance]

Introduction What’s new in Hyperledger Fabric v2.0 Release notes Key Concepts Getting Started Developing Applications Tutorials Operations Guides Upgrading to the latest release Commands Reference Architecture Reference same characteristics as Bitcoin but adding smart contracts to create a platform for distributed applications. Bitcoin and Ethereum fall into a class of blockchain that we would classify as public permissionless org/wiki/Fault_tolerance] (CFT) consensus protocol might be more than adequate whereas, in a multi-party, decentralized use case, a more traditional byzantine fault tolerant [https://en.wikipedia.org/wiki/Byzantine_fault_tolerance]

Introduction What’s new in Hyperledger Fabric v2.0 Release notes Key Concepts Getting Started Developing Applications Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands same characteristics as Bitcoin but adding smart contracts to create a platform for distributed applications. Bitcoin and Ethereum fall into a class of blockchain that we would classify as public permissionless org/wiki/Fault_tolerance] (CFT) consensus protocol might be more than adequate whereas, in a multi-party, decentralized use case, a more traditional byzantine fault tolerant [https://en.wikipedia.org/wiki/Byzantine_fault_tolerance]

Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started Developing Applications Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands same characteristics as Bitcoin but adding smart contracts to create a platform for distributed applications. Bitcoin and Ethereum fall into a class of blockchain that we would classify as public permissionless org/wiki/Fault_tolerance] (CFT) consensus protocol might be more than adequate whereas, in a multi-party, decentralized use case, a more traditional byzantine fault tolerant [https://en.wikipedia.org/wiki/Byzantine_fault_tolerance]

Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started Developing Applications Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands same characteristics as Bitcoin but adding smart contracts to create a platform for distributed applications. Bitcoin and Ethereum fall into a class of blockchain that we would classify as public permissionless org/wiki/Fault_tolerance] (CFT) consensus protocol might be more than adequate whereas, in a multi-party, decentralized use case, a more traditional byzantine fault tolerant [https://en.wikipedia.org/wiki/Byzantine_fault_tolerance]

Introduction What’s new in Hyperledger Fabric v2.x Release notes Key Concepts Getting Started Developing Applications Tutorials Deploying a production network Operations Guides Upgrading to the latest release Commands same characteristics as Bitcoin but adding smart contracts to create a platform for distributed applications. Bitcoin and Ethereum fall into a class of blockchain that we would classify as public permissionless org/wiki/Fault_tolerance] (CFT) consensus protocol might be more than adequate whereas, in a multi-party, decentralized use case, a more traditional byzantine fault tolerant [https://en.wikipedia.org/wiki/Byzantine_fault_tolerance]

same characteristics as Bitcoin but adding smart contracts to create a platform for distributed applications. Bitcoin and Ethereum fall into a class of blockchain that we would classify as public permissionless org/wiki/Fault_tolerance] (CFT) consensus protocol might be more than adequate whereas, in a multi-party, decentralized use case, a more traditional byzantine fault tolerant [https://en.wikipedia.org/wiki/Byzantine_fault_tolerance] etcd/Raft and a fully decentralized BFT ordering service. Note also that these are not mutually exclusive. A Fabric network can have multiple ordering services supporting different applications or application