Search for projects by name
Fuel Ignition is a high-performance Ethereum L2 built on FuelVM and the Sway language.
Fuel Ignition is a high-performance Ethereum L2 built on FuelVM and the Sway language.
The project will be classified as "Other" due to its specific risks that set it apart from the standard classifications.
The project will move to Others because:
Consequence: projects without a proper proof system fully rely on single entities to safely update the state. A malicious proposer can finalize an invalid state, which can cause loss of funds.
2024 Aug 28 — 2025 Feb 21
2024 Aug 30 — 2025 Feb 20
The section shows the operating costs that L2s pay to Ethereum.
2024 Feb 21 — 2025 Feb 20
Currently the system permits invalid state roots. More details in project overview.
There is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.
Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
Ultimately, Fuel will use one round fraud proofs with single round performed via a RISC-V-based zkVM. Currently, there is a 7d challenge period.
Funds can be stolen if an invalid state root is submitted to the system by the proposer (CRITICAL).
All executed transactions are submitted to an on chain smart contract. The execution of the rollup is based entirely on the submitted transactions, so anyone monitoring the contract can know the correct state of the rollup chain.
While forcing transaction 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.
Because the state of the system is based on transactions submitted on the underlying host chain and anyone can submit their transactions there it allows the users to circumvent censorship by interacting with the smart contract on the host chain directly.
If the user experiences censorship from the operator with regular L2->L1 messaging they can submit their messages directly on L1. The system is then obliged to service this request or halt all messages, including forced withdrawals from L1 and regular messages initiated on L2. Once the force operation is submitted and if the request is serviced, the operation follows the flow of a regular message.
The FuelVM makes use of the UTXO model and a register-based design to enable parallel transaction processing. The language used is Sway and it does not support Solidity contracts.
Whitelisted addresses that can pause the ERC20Gateway.
Whitelisted addresses that can pause the FuelChainState.
Permissioned address submitting tx data as blobs.
Permissioned address that can propose new state roots.
A Multisig with 10 / 13 threshold. Can upgrade the FuelERC20Gateway, FuelMessagePortal and FuelChainState contracts, potentially gaining access to all funds. It can unpause contracts and remove L2->L1 messages from the blacklist. It can also limit the tokens that can be bridged to L2.
Standard gateway to deposit and withdraw ERC20 tokens. It implements rate limits and a whitelist for tokens. The whitelist is currently active. This contract can store any token.
Contract that allows to send and receive arbitrary messages to and from L2. It implements a max deposit limit for ETH, currently set to 115792089237316195423570985008687907853269984665640564039457.584007913129639935 ETH, and rate limits withdrawals. Pausers are allowed to blacklist L2->L1 messages. This contract stores the following tokens: ETH.
Contract that allows state root submissions and settlement.
The current deployment carries some associated risks:
Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on upgrades (CRITICAL).
Funds can be frozen if pausers blacklist L2->L1 messages (CRITICAL).
Funds can be frozen if the limit of tokens that can be withdrawn is set too low.