to more innovative enterprise use cases also grew. However, many enterprise use cases require performance characteristics that the permissionless blockchain technologies are unable (presently) to deliver Participants must be identified/identifiable • Networks need to be permissioned • High transaction throughput performance • Low latency of transaction confirmation • Privacy and confidentiality of transactions fully byzantine fault tolerant consensus might be considered unnecessary and an excessive drag on performance and throughput. In situations such as that, a crash fault-tolerant (CFT) consensus protocol might

to more innovative enterprise use cases also grew. However, many enterprise use cases require performance characteristics that the permissionless blockchain technologies are unable (presently) to deliver requirements: Participants must be identified/identifiable Networks need to be permissioned High transaction throughput performance Low latency of transaction confirmation Privacy and confidentiality of transactions fully byzantine fault tolerant consensus might be considered unnecessary and an excessive drag on performance and throughput. In situations such as that, a crash fault-tolerant [https://en.wikipedia.org/w

to more innovative enterprise use cases also grew. However, many enterprise use cases require performance characteristics that the permissionless blockchain technologies are unable (presently) to deliver requirements: Participants must be identified/identifiable Networks need to be permissioned High transaction throughput performance Low latency of transaction confirmation Privacy and confidentiality of transactions fully byzantine fault tolerant consensus might be considered unnecessary and an excessive drag on performance and throughput. In situations such as that, a crash fault-tolerant [https://en.wikipedia.org/w

to more innovative enterprise use cases also grew. However, many enterprise use cases require performance characteristics that the permissionless blockchain technologies are unable (presently) to deliver Participants must be identified/identifiable • Networks need to be permissioned • High transaction throughput performance • Low latency of transaction confirmation • Privacy and confidentiality of transactions fully byzantine fault tolerant consensus might be considered unnecessary and an excessive drag on performance and throughput. In situations such as that, a crash fault-tolerant (CFT) consensus protocol might

to more innovative enterprise use cases also grew. However, many enterprise use cases require performance characteristics that the permissionless blockchain technologies are unable (presently) to deliver requirements: Participants must be identified/identifiable Networks need to be permissioned High transaction throughput performance Low latency of transaction confirmation Privacy and confidentiality of transactions fully byzantine fault tolerant consensus might be considered unnecessary and an excessive drag on performance and throughput. In situations such as that, a crash fault-tolerant [https://en.wikipedia.org/w

to more innovative enterprise use cases also grew. However, many enterprise use cases require performance characteristics that the permissionless blockchain technologies are unable (presently) to deliver requirements: Participants must be identified/identifiable Networks need to be permissioned High transaction throughput performance Low latency of transaction confirmation Privacy and confidentiality of transactions fully byzantine fault tolerant consensus might be considered unnecessary and an excessive drag on performance and throughput. In situations such as that, a crash fault-tolerant [https://en.wikipedia.org/w

to more innovative enterprise use cases also grew. However, many enterprise use cases require performance characteristics that the permissionless blockchain technologies are unable (presently) to deliver requirements: Participants must be identified/identifiable Networks need to be permissioned High transaction throughput performance Low latency of transaction confirmation Privacy and confidentiality of transactions fully byzantine fault tolerant consensus might be considered unnecessary and an excessive drag on performance and throughput. In situations such as that, a crash fault-tolerant [https://en.wikipedia.org/w

to more innovative enterprise use cases also grew. However, many enterprise use cases require performance characteristics that the permissionless blockchain technologies are unable (presently) to deliver Participants must be identified/identifiable • Networks need to be permissioned • High transaction throughput performance • Low latency of transaction confirmation • Privacy and confidentiality of transactions fully byzantine fault tolerant consensus might be considered unnecessary and an excessive drag on performance and throughput. In situations such as that, a crash fault-tolerant (CFT) consensus protocol might

to more innovative enterprise use cases also grew. However, many enterprise use cases require performance characteristics that the permissionless blockchain technologies are unable (presently) to deliver Participants must be identified/identifiable • Networks need to be permissioned • High transaction throughput performance • Low latency of transaction confirmation • Privacy and confidentiality of transactions fully byzantine fault tolerant consensus might be considered unnecessary and an excessive drag on performance and throughput. In situations such as that, a crash fault-tolerant (CFT) consensus protocol might

to more innovative enterprise use cases also grew. However, many enterprise use cases require performance characteristics that the permissionless blockchain technologies are unable (presently) to deliver Participants must be identified/identifiable • Networks need to be permissioned • High transaction throughput performance • Low latency of transaction confirmation • Privacy and confidentiality of transactions fully byzantine fault tolerant consensus might be considered unnecessary and an excessive drag on performance and throughput. In situations such as that, a crash fault-tolerant (CFT) consensus protocol might