achieved with a BFT consensus algorithm, tolerating even malicious behavior from a limited number of consortium members. This means that as long as two-thirds of the nodes in the network are functioning correctly, consensus will be achieved. If a node falls out of sync, it can retrieve the lost data from its peers and rejoin the consensus process. • BFT allows transactions to be confirmed in seconds. When the number of blockchain’s validator nodes is 3f+1, a block must receive 2f+1 “votes” to be approved. Comments • We view Chromia's technical base which allows dapps on the network to run their own blockchain (and nodes), as well as the hybrid structure between blockchain and database as the main advantages of this project. In addition, the Chromapolis relational model allows data to be easily administered and accessed by API. • As the platform is database-centric, it is already proving to be better suited for data-intensive applications, than many of its competitors. • There are many projects out there, trying to solve the issues of current blockchain platforms, most of them focus on sidechain scalability or different consensus algorithms to boost their scalability, Chromia's hybrid model is a unique solution, enabling enterprises to adopt blockchain technology without eradicating existing legacy systems. • However, the relational model also has some disadvantages, which the team admits in their whitepaper, but still, it seems to be a promising approach when it comes to the ability to scale in terms usage and developer activity. • Currently, Chromia is still using a fairly centralized development and governance model. Eventually, existing providers will be able to vote for new providers. The goal is to have thousands of providers, but it is uncertain how long this will take. Source: Blockfyre Research | Chromia whitepaper