Fuel Staking

Fuel Staking presents an unresolved question about which product the record covers; it does not prove that a pool falls below the size floor. DefiLlama retains a dummy Fuel Ignition record with null TVL and no current samples. The Rig says every remaining native L2 stake migrated to stFUEL on October 7, 2025, while Fuel’s current stable documentation still tells users to stake on Fuel and lists both L2 Staking and The Rig mainnet contracts. Ethereum-origin Shared Sequencer delegation is also live but is not measured by this slug. Ketju rejects it at zero because this conflict blocks the individual version-1 lifecycle review until the tracked product, contracts, balances and successor boundary reconcile.

Review triggers: events that reopen the verdict
• Fuel publishes a migration completion record or onchain transaction set reconciling every legacy L2 receipt into stFUEL and identifies the exact active product, receipt, implementations, administrators, supply and attributable reserve measured by the survey slug
• The identified product maps authorities, validator concentration, slashing, audits and incidents and demonstrates a proposed-size stressed exit through its documented unbonding or stFUEL liquidity path

Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.

The research file

Mechanism applicability

Fuel uses FUEL delegation to validators that secure its Tendermint proof-of-stake Shared Sequencer Network. Ethereum-origin delegation lets a holder select a validator and returns principal only after an unbonding sequence. Fuel-native documentation instead says Ignition distributes delegation automatically. The Rig pools FUEL across operators and issues stFUEL. These are separate direct and liquid-staking claims, so a null aggregate slug cannot show which contracts, receipt or exit the client would hold.

Current observation and lifecycle conflict

The DefiLlama protocol API read on 2026-08-16 still identified Fuel Staking on Fuel Ignition, but it used dummy.js, returned null TVL and provided no current chain samples. The Rig says all remaining L2 positions were automatically converted to stFUEL on October 7, 2025. Fuel’s current stable documentation conflicts with that statement: it still gives users a Stake on Fuel workflow, and its verified-address registry lists both a Fuel-mainnet L2 Staking contract and The Rig contract. The sources therefore prove neither complete retirement nor a current balance that can be tied to the record.

Control and exit applicability

Delegators choose validators and bear validator, smart-contract and token-price risk. To unstake from Ethereum, they must wait through a 14-day unbonding period plus approximately 4,096 sequencer blocks before funds return to Ethereum. Migrated native positions depend on The Rig and stFUEL liquidity or its withdrawal path. This adds liquid-staking contract and secondary-market dependencies to the original validator exposure.

Security and incident evidence boundary

Fuel publishes current verified addresses for the sequencer, L2 Staking and The Rig, while The Rig cites an Oak Security audit. Those facts do not tie one audit and incident history to the null DefiLlama slug or prove whether legacy native balances remain. A full review must identify the exact held contract and receipt, verify who holds its upgrade and emergency powers, check validator and slashing exposure, and separate legacy L2 stake from The Rig stFUEL and direct Ethereum delegation.

Decision, comparison and exact unresolved evidence

Null does not prove that TVL falls below the size floor, and the conflicting documentation about the successor prevents a class-rule shortcut. The active coverage record remains an individual rejected memo. Deleting or archiving it would break live coverage, while treating it as current native staking would claim that it operates without proof. Resolution requires a primary record that the migration was completed or an onchain transaction set that maps every legacy L2 receipt into stFUEL. It also requires the exact currently callable L2 Staking and The Rig implementations and administrators, receipt supply and attributable reserves, and confirmation of whether the survey slug measures legacy stake, stFUEL, direct Ethereum delegation or none of them. Ketju must then show an exit at the proposed size and compare direct Ethereum delegation with The Rig on validator control, slashing, authorities, audit coverage, liquidity and withdrawal timing.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Fuel — live Fuel staking migration notice · primary · accessed 2026-08-15
  Supports: Fuel Ignition staking, migration, The Rig, stFUEL claim
• Fuel — Ethereum delegation and unstaking · primary · accessed 2026-08-15
  Supports: validator delegation, Ethereum, 14-day unbonding, 4096 blocks, withdrawal
• Fuel — token and Shared Sequencer overview · primary · accessed 2026-08-15
  Supports: FUEL, proof of stake, Shared Sequencer Network, validator rewards, ETH gas
• Fuel — current verified staking contracts · primary · accessed 2026-08-16
  Supports: Fuel mainnet, L2 Staking, The Rig, Ethereum, deployed contracts
• The Rig — Fuel staking migration · primary · accessed 2026-08-15
  Supports: L2 stake migration, stFUEL, automatic migration, withdrawal path, secondary liquidity
• DefiLlama — Fuel Staking survey record · secondary · accessed 2026-08-15
  Supports: null current TVL, empty chain samples, Fuel Ignition, survey observation

Inherited controls

The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.