Thread by @lingebar314

1/x Why @fuellabs_?

Fuel began as a L2 scalability technology for a monolithic Ethereum. It was the first optimistic rollup on mainnet Ethereum.

Now, Fuel is the fastest MEL. It delivers the highest security & flexible throughput, with a focus on a dev experience.

@fuellabs_ 2/x User Sovereignty with Fraud Proofs

Fuel was designed & built specifically to be fraud-provable, which enable support for trust-minimized light clients. Trust minimized light clients and shared data availability enables trust minimized bridges to other MEL..

@fuellabs_ 3/x ..something impossible to achieve between L1s.

What this means in practice:
• Long-term liquidity access
• Users can validate the chain without having to run full nodes
• Safely bridging assets

@fuellabs_ 4/x Fuel’s optimization for fraud proofs is the use of the UTXO model, which in turn means Fuel has no global state tree or account trees. If you wanted to apply the general construction of a fraud proof to a chain that uses the account model like Ethereum..

@fuellabs_ 5/x the cost could be unbound, making it extremely expensive to produce a fraud proof. In this general construction of a fraud proof, given a pre-state and a state transition, you locally execute the transition and compare the output to the post-state produced..

@fuellabs_ 6/x ..by the block producer. If these differ, the post-state by the block producer was invalid. If you apply this general fraud proof model to Ethereum today, someone could create a transaction that calls many different contracts, and those contracts could each have up to..

@fuellabs_ 7/x ..24kb of bytecode. In order to locally re-execute, you need to provide all the bytecode for all the contracts that were interacted with.

Superior DevEx

Fuel’s technology comes together to provide a superior developer experience. Here’s how we do it:

@fuellabs_ 8/x Sway and Fuel Toolchain

The FuelVM is designed to be vertically integrated with tooling. Unlike EVM which was designed without a language from the start, the FuelVM is built alongside its companion language, Sway, ensuring it has handy and efficient ops, such as..

@fuellabs_ 9/x ..getting specific parts of a tx. Sway is a Rust-based DSL created specifically to leverage a blockchain VM without needlessly verbose boilerplate. Sway leverages Rust’s safety and catches errors and bugs at compile-time, giving developers peace of mind.

@fuellabs_ 10/x Parallel Execution

Fuel brings scale to Ethereum without sacrificing decentralization. The FVM is designed to reduce wasteful processing of traditional blockchain VM architectures, while vastly increasing the potential design space for developers.

@fuellabs_ 11/x Fuel Configurations

As a Modular Execution Layer, Fuel can function in any one of these categories. Developers can configure Fuel as-needed by switching out a few modules in the client.

@fuellabs_ 12/x Improved VM

The Ethereum community has suggested many implementation improvements to improve EVM performance. Unfortunately, many of these improvement proposals haven’t been implemented because they would break backward compatibility. Execution layers built on Ethereum..

@fuellabs_ 13/x ..give us a new opportunity to build something better. Designs don’t need to be backward compatible and in fact, can do whatever is necessary to deliver global throughput and adoption for Ethereum. The FuelVM is the EVM greatly improved.

@fuellabs_ 14/x Thanks for the attention ^-^

#modularity #fuellabs #evm #fuelvm #layer2 #blockchain #celestia