Publication: The opinions and opinions expressed here are exclusively to the author and do not represent the views and opinions of the editorial editorial of crypto.news.
Do you not hate it if you still see a launch of Layer-1 and claim a million, 10 million or even 100 million TPS? “How can I redeem the hype?” you ask. Well, today is your lucky day! Here is a step-by-step manual for building your own 1 billion TPS Layer-1 network that leaves those posters in the dust.
Maybe you also like it: From crypto projects to digital asset companies: it’s time to deliver Web3 Comms | Opinion
Step 1: Buy a supercomputer and perform EVM
A high-end machine can perform transactions in the Ethereum Virtual Machine (EVM) to ~ 100k TPS-a fairly well documented technical fact. But to achieve this level of transit, you must bypass the Patricia Merkle Tree during reads and write to permanent state to remove an important bottlenecks that limits the standard EVM to slightly less than 100 TPS. This mechanism in the EVM exists to ensure that the network, sorry, the single machine, is able to handle rollbacks and network reorganisations correctly … Anyway, what gives it, it is slow, it’s gone, don’t worry.
We use the EVM because EVM is compatible, or better yet, EVM equivalent, is quite important nowadays, because it has become a standard in web3 development. Most Web3 applications in the world are written in solidity or other languages that compile in the EVM -Bbytecode. In this way you can attract more developers to build on your new 1 billion TPS network. Believe me, Bro, “EVM equivalent” sells completely.
Step 2: Forget the network
A single machine is also technically a network. Why makes this side more complicated with more than one machine?
By the way, having other machines on the network just slows things. If you have filled a network with different machines that are run by different people, they now suddenly have to agree with each other about what is happening on the network. This includes communicating information in the network, coming up with mechanisms to agree on what is happening and then to reach a consensus before making progress. Sounds slowly. This consensus mechanism is just a lot of waste overhead. Who needs it?
Let’s just stay with a single machine. View all these hot projects called Layer-2s; Their networks are all just one machine. If you are worried that you are called to be centralized, you can easily create a number of other machines on the network and you admit them nice names, such as “Data availability nodes” or something similar. Everyone does it.
Step 3: Make 100 shards
Get ready, here we raise your game, with sharing.
You take your network of one machine and make 100 copies of it; We call this sharding, very trendy. Technically, the status of a Sharded Network is only temporarily distributed over machines and will ultimately be partially or completely synchronized to guarantee consistency during Cross-Shard transactions. In opponents such as crypto, machines are often shaken about shards to prevent collusion.
But let’s not become technical. These 100 copies do not have to synchronize anything; They don’t even have to communicate with each other. It is a network of 100 shards!
If you keep the score, we now have 100 shards * 100k TPS = 10 million TPS!
Step 4: Dump the EVM
Did we say that EVM equivalent is all anger? That is old news. Now it is about being the EVM murderer.
EVM is just so slow. It is a packed-based virtual machine that is designed to be fully agnostic for the underlying hardware architecture and operating systems, to maximize the repeatability and correctness of the implementation, so that a large group of different machines can work safely and safely on the same network. But man, it’s slow.
Let’s go with something sexy like Washm-Jit. It is very performance, adult and most large programming languages can be compiled in washing. Because it compiles to native on registration-based machine code that focuses on specific hardware architectures, it is inherently less portable than a pure stack-based VM such as EVM. In real-world implementations, Washm-Jit can perform better than the EVM up to 100 times in implementation speeds.
Dump the EVM, we now have 10 million TPS * 100 = 1 billion TPS.
You did it!
Stay up to date, and we will teach you how to further elevate your 1 billion TPS Layer-1 network with unrealistic-optimistic simultaneity!
Read more: Beyond the Hype: Web3 is urgently needed for a rebrand | Opinion
Steven PU
Steven PU Is the co-founder of Taraxa, a specially built, fast, scalable and device-friendly Layer-1 public ledger that is designed to democratize the reputation by making informal data reliable. Prior to Taraxa, Steven launched several companies and products in IoT and Mobile Healthcare. He was also a partner in the strategy practice of Monitor Deloitte, led their digital strategy line and served Fortune 500 companies with hundreds of millions on an upward impact. Steven also had the honor to merge the book “Next Blockchain” with Makoto Yano, vice-minister of the Japanese Ministry of Economy, Trade and Industry. Steven did not achieve braduated and master in electrical engineering at Stanford University.
