Fuel: A Trustless Sidechain
Editor's Note: This article is from:Ethereum enthusiasts (ID: ethfans)Editor's Note: This article is from:
Ethereum enthusiasts (ID: ethfans)
Ethereum enthusiasts (ID: ethfans)https://www.youtube.com/, Author: John Adler, reproduced by Odaily with authorization.
This article is a speech given by John Adler on behalf of Fuel Labs at the EthCC3 conference. Fuel is a project that aims to provide stable currency payment services using the rollup method. John's speech is essentially discussing the significance of the Layer-2 expansion scheme.
Video address of the speech:
(very short, only 13 minutes)
In the first part, the author stated the scalability problem faced by the public chain, and pointed out the misunderstanding of everyone: the number of consensus nodes does not affect the scalability of the chain, because the bottleneck is not the consensus mechanism. The real bottleneck lies in the social contract (we pursue decentralization), so we don't want to impose higher requirements on the amount of resources invested by consensus nodes.
The expansion dilemma of Ethereum lies in the complexity of transactions, as well as the growth and access requirements of state data (this complexity requires nodes to invest more resources in verification, and the acquisition of state data is one of the prerequisites for verification, so must access the state data on the hard disk).
Next, the author talked about the core idea of the Rollup scheme: using the Ethereum blockchain to provide data availability, execute transactions and save state under the chain. As for how to ensure the validity of the rollup block on the chain, each shows its own magic: using zero-knowledge proof is called zk rollup; optimistic rollup uses error proof and synchronization assumption; in addition, there is an interactive challenge Game.
So why does Rollup scale throughput? Because the execution of transactions is completely off-chain. This is significant because, obviously, this is the bottleneck in transaction execution that is maximally resolved.


