blockchain, komodo,

Komodo compared to Ethereum & ETH architecture problems

Follow Dec 29, 2018 · 2 mins read
Komodo compared to Ethereum & ETH architecture problems
Share this

Lately I have seen more questions asked on what is Komodo compared to Ethereum?  Ethereum architecture problems are well known currently and the dev team is working on it – or has been thinking/working on it for some time.  This tweet storm about ethereum architecture problems and more (economic changes etc.) is epic and brutally honest in my opinion.  Has some good references to back up the argument.

ETH’s whitepaper directly highlights the limitations of bitcoin.   These limitations are arguably in place so that the project does things a certain way – not provide a general purpose blockchain.  Whether the ethereum architecture problem needs to be highlighted has been covered by many projects and bloggers.

Komodo Compared To Ethereum

I was fortunate enough to get curious on what komodo compared to ethereum was like for a komodo tech tuesday in early december 2018.  The architectural advantages of Komodo compared to Ethereum needed to be highlighted for an infographic competition to assist graphic designers in understanding how komodo solves blockchain scalability, here is an earlier post about blockchain scaling tests on AWS infrastructure prior to komodo being recognised as a blockchain innovation leader and becoming an AWS advanced tech partner.

Blockchain Scalability With Sharding

In the tweet storm linked in the intro, the author mentions a lot of sharding and proof of stake stuff.   The most efficient way to achieve peer2peer scalability is by sharding.  There’s many ways to do sharding, like any architecture.  I’m not an expert in sharding methods so cannot preach about the holy grail methods of doing it, but it works.  It’s been done with databases for years and now it’s working with blockchain technology.

How komodo does it is:

  • Multi-chain architecture
  • Fungibility between chains
  • Burn protocol to maintain coin supply

The secret to this lies in MoM technology – simply – merkle root of merkle roots.

merkle root of merkle roots


Between chains an on-chain oracle needs to observe the MoMs and broadcast them to all participating chains in the cluster.

sync to main chainsync from main chain

Ecosystem Innovation & Abrasive Responses

Ecosystem comparisons of Komodo compared to Ethereum would be unfair and biased at this point.  I think Komodo is great, and the ecosystem (through Verus lead dev – and ahem, architect of Microsoft .net platform) can collaboratively solve blockchain problems e.g. with proof of stake chains.  It is interesting the statements that come out of the eth thought leaders.  But they have been working on “cooler” sharding technologies than MoM recently.  Time will tell whether the linked tweet storm holds more truth than rage-tweeting.


Written by