Context and Problems

A quick glance at this GitHub page and you will notice that there are currently more than 25 smart contract platforms. Although some have similar languages, there is a lot of diversity:

Solidity

C++

Go

Javascript

.NET

Plutus (Haskell-inspired)

Ivy-Lang

Scrypto (Typescript-inspired)

Michelson

Rust

Despite some language overlaps, it’s important to note they all have different ABI heuristics.

The plethora of choice seems confusing, and rightly so! However, at MPOS (we don’t have a name yet), we believe this is just the beginning of a huge growth in smart contract platforms.

Smart people around the world are putting pen to paper and code to screen to try and solve some of the toughest scalability problems on existing platforms. Every iteration, new release, fork and breakthrough is simultaneously applauded and cursed by developers who are expected to keep up to date.

Enter the Game of Smart Contracts and a sneak-peak at what to expect. The battle for smart contract supremacy will intensify over the next years, leaving developers shouting at their screens:

“Why can’t I reuse code across platforms?”

“I’ve written so many smart contracts in Ethereum, and now my (new) employer demands the same logic to be deployed on EOS. Am I doomed to learn everything from scratch?”

“How can I make sure my smart contracts are bug-free and not pay a 5-figure amount for that?”

Anticipating more twists and turns than a George R R Martin novel, at MPOS we aren’t getting too emotionally attached to a smart contract platform, less it be killed off in the next season.