Blockchain fundamentals
Optimistic rollups: claims, challenges and the exit route
The security argument depends on what can be challenged and who can actually submit the challenge.
Research articles and reference entries are published in English. Navigation is available in seven languages.
People & projects
In this article
An assertion with a dispute process
An optimistic rollup publishes information about its state changes to a settlement layer and allows incorrect assertions to be challenged under its protocol. The dispute mechanism aims to stop an invalid result from becoming accepted settlement merely because an operator submitted it.
The design requires usable data, a functioning challenge process and participants able to act within the relevant conditions. A project can be described as optimistic while its deployed permissions still restrict important parts of that process.
Inspect the deployed controls
Identify who can propose outputs, who can dispute them, which implementation resolves a dispute and who can upgrade that implementation. Then trace a user's withdrawal during an operator outage or hostile upgrade. An architectural whitepaper alone does not establish those live permissions.
Challenge periods also explain why a canonical withdrawal may take longer than a liquidity-provider shortcut. The shortcut introduces its own counterparty or liquidity dependence. Compare validity proofs, available data and upgrade powers before reducing an L2 comparison to fee and transaction-speed rankings.