$STORE Engineering

💪 BlockfinBFT is in active development

✅ Next version of the BlockfinBFT simulation

CTO Rag explaining BlockfinBFT

📖: storecoin.com/cpt

We are not talking about specialized services or APIs here -- basic storage needs of apps. This is what we summarized in the CPT paper -- that the *decentralization premium* must be *reasonable* to attract app developers.

12/ Here's the summary of the comparison across multiple crypto projects against the cost of development on AWS.

24/ And, finally a nitpick. From 0Chain's Github — github.com/0chain/docs — the highlighted sentences below will *not* provide Byzantine Fault Tolerance. This document may be old, but wanted to highlight on the BFT *safety*.

19/ If the committee cannot agree on the block, the process is repeated with no guarantees of success the next time. *Liveness* is guaranteed only if there is a period of "strong synchrony" of sufficient length, which again, it hard to guarantee in real world scenarios.

And, see their second assumption below. This version also assumes a "permissioned" network instead of the "permissionless" network assumed in the original paper. While a "switch" to the latter is mentioned, we all know how hard it is in practice, especially *after* the launch.

The following is quoted from their latest paper (eprint.iacr.org/2018/377.pdf) published on Aug 28, 2018.

19/ If the committee cannot agree on the block, the process is repeated with no guarantees of success the next time. The safety is guaranteed only if there is a period of "strong synchrony" of sufficient length, which again, it hard to guarantee in real world scenarios.