Rollup fees run on two meters: execution gas and the L1 data bill
Your L2 fee is two separate charges, rollup execution and a data bill paid to Ethereum, and they move for different reasons.
Rollups and Layer 2 reporter
Montréal, Canada
Ilan Ferrand writes about rollups and the rest of Ethereum's Layer 2 landscape for Etherelysium from Montréal, Canada. The beat covers how optimistic and ZK rollups prove their state to Ethereum, who runs the sequencer, how long a withdrawal really takes, how bridges decide that a deposit happened, and why a rollup fee has two parts.
The starting point is usually the rollup's own documentation and contracts rather than its marketing page: the length of the challenge window, whether permissionless fault proofs are live, who can upgrade the bridge contract and with how much notice, and what a user can do if the sequencer stops. Public risk frameworks help with structure, but each claim is checked against the project's own published parameters, and the article says plainly when a project does not publish one.
The aim is to make "secured by Ethereum" mean something specific. Each piece separates what an L2 inherits from layer 1 from what still depends on a team, a multisig or an operator, and shows what changes for someone moving funds. There are no rankings or price talk on this beat; comparisons on the site ask every chain the same questions and state the date the data was read. Corrections and tips go to the desk through the contact page.
Your L2 fee is two separate charges, rollup execution and a data bill paid to Ethereum, and they move for different reasons.
Rollups truly inherit Ethereum's data availability and settlement, but not liveness, ordering or upgrade-key safety.
Bridge designs differ in who attests your deposit happened, and in what happens when they're wrong.
Arbitrum One, OP Mainnet and Base share fraud proofs but not exit clocks or override powers.
Most rollups still run one sequencer, which creates censorship and downtime risk that new designs target.
Optimistic and ZK rollups prove correctness differently, but the label alone says little about security.
An L2's quick confirmation is not L1 settlement; three explorer checks tell the two apart.
The stages framework rates who can still override a rollup, whatever its proof type.
No value crosses a bridge, so its risks sit in contracts, validators, oracles and wrapped assets.
EIP-4844 gave rollups a separate, temporary blob data lane with its own fee market and burn.