ChromaWay overview notes

These days during the bear, I’ve been moreso helping behind the scenes for groups doing quick reviews rather than in depth analyses.

Came across ChromaWay and wanted to jot down some points

Summary:

• Blockchain integrated with existing database solutions

Advantages and primary use case

• Other comapnies may write data to both its own blockchain and database. This requires an SQL developer as well as a blockchain developer to generate reports. ChromaWay blockchain is integrated in the SQL database and so the SQL developer just has to run a query to access the information. Obviously ChromaWay will still maintain the blockchain if required.
• Added layer of redundancy via Byzantine Fault Tolerance

Disadvantages

• ChromaWay admits processing time is required to also validate the transaction to the blockchain sequentially but on fast servers, 100–1000’s of tx per second could be achieved.
• It looks like a weakness is if the primary key issuer for the blockchain is not redundant? (To be confirmed)

Competition

• What if Microsoft or Oracle developed their own similar, seamless blockchain for their SQL solutions? No enterprise would risk going for a third party. ChromaWay would be hoping for either early market adoption or acquisition.

Paper and team

The language used by the team seems consistent and makes sense on a high level.

It’s a team of four based in Sweden, so it could be some time before we see acceptance in big markets such as USA.

Risk/Reward

• High risk due to difficulty entering existing market but if enough traction can happen from companies adopting ChromaWay then this project will fly.