Fuel v1

Website	fuel.sh
Documentation	docs.fuel.sh
Explorer	mainnet.fuel.sh/network
Repository	github.com/FuelLabs/fuel-v1-contracts
Social	discord.gg @fuellabs_

Description

Fuel aims to be a complete optimistic rollup with low transaction costs, high speed and high throughput.

If you find something wrong on this page you can submit an issue or edit the information.

Risk analysis

Sequencer failureState validationData availabilityUpgradeabilityValidator failure

State validation

Fraud proofs (1R)

Fraud proofs allow actors watching the chain to prove that the state is incorrect. Single round proofs (1R) only require a single transaction to resolve.

Data availability

On chain

All of the data needed for proof construction is published on chain.

Upgradeability

The code that secures the system can never change.

Sequencer failure

Propose blocks

The user needs to run their own node and use it to propose new blocks that include otherwise censored transactions.

Validator failure

Propose blocks

The user needs to run their own node and use it to propose new blocks to replace the validator.

Technology

Fraud proofs ensure state correctness

After some period of time, the published state root is assumed to be correct. For a certain time period, usually one week anyone can submit a fraud proof that shows that the state was incorrect.

Funds can be stolen if there is no one that checks the published state. Fraud proofs assume at least one honest and able validator.

Background - Fuel documentation

All data required for proofs is published on chain

All the data that is used to construct the system state is published on chain in the form of cheap calldata. This ensures that it will always be available when needed.

Background - Fuel documentation

Operator

The system has a centralized sequencer

While proposing blocks is open to anyone the system employs a privileged sequencer that has priority for submitting transaction batches and ordering transactions.

MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.

Users can force any transaction

Because the block production is open to anyone if users experience censorship from the operator they can propose their own blocks which would include their transactions.

Users can be censored if the operator refuses to include their transactions and users lack resources to propose blocks themselves.

Architecture: A High-Level View - Fuel documentation

The user initiates the withdrawal by submitting a transaction on L2. When the block containing that transaction is finalized the funds become available for withdrawal on L1. The process of block finalization usually takes several days to complete. Finally the user submits an L1 transaction to claim the funds. This transaction requires a merkle proof.