Now that EOS’ ICO is behind us, let’s take a look at the technology powering this project. The developers are putting a strong focus on asynchronous smart contracts (ASCs). This is similar to Ethereum, but it appears EOS will be far more efficient. How does it all work? What benefits does it provide?
ASYNCHRONOUS SMART CONTRACTS EXPLAINED
Whenever someone talks about smart contracts, Ethereum is inevitably brought up. Ethereum is immensely popular because of their implementation of smart contracts. However EOS is approaching this differently with asynchronous smart contracts (ASCs). ASCs are something else entirely. Blockchain technology relies on sequential transaction processing, which causes delays and can render the technology inefficient.
The throughput of a blockchain using sequential processing of transactions is limited to the computational capacity of a single CPU core. Using CPUs with more powerful cores can address some concerns, but it is not a long-term solution. Instead, we need to pursue concepts which allow for horizontal scaling, rather than vertical scaling. This is much easier said than done, but ASCs present an interesting opportunity to achieve it.
The EOS project aims enable a blockchain to process millions of transactions per second. This is an ambitious goal, and its feasibility has yet to be demonstrated. Most of the details regarding ASCs are shrouded in mystery, which makes it difficult to assess its viability. Not sharing the details with the public is a strange decision, and somewhat frustrating to those of us who want to understand ASCs better. However, this project seems to be in good hands. Dan Larimer is its CTO, who also helped develop Steemit and BitShares.
The goal of ASCs is to cut transactions into bite-sized pieces. In theory, this will allow the underlying blockchain to process a high amount of transactions at the same time, while still being able to serve other network commands. For example, the technology allows for transaction processing and Dapp execution at the same time without creating a “queue” on the blockchain. All of this remains theoretical since there are no real-world demonstrations of ASC handling these different commands concurrently.