An optimistic rollup promises permissionless exit. In practice a small council can upgrade the bridge that holds your funds.
Key takeaways
Find the upgrade authority first.
Check the timelock length in blocks.
Confirm a permissionless exit exists.
Verified October 27, 20261 min read
The three questions
Who holds the upgrade key? A multisig of named people is a trust assumption. A single deployer key is a bigger one.
How long is the timelock? Long enough to exit, or only long enough to look reassuring?
Is there a forced exit? If users can post a transaction directly to the base chain and leave, the timelock matters less. If not, it is the only protection.
Why concentration turns this systemic
When a handful of rollups hold most of the value, a defect in one upgrade process is not a single-protocol incident. It is a shared dependency, in the same way that a common library bug becomes everyone’s bug.
Every offer is re-checked against the official terms page, the bonus amount and the expiry date before it is published, and again whenever a campaign changes.
One short email each morning with the offers that changed overnight.
No spam, unsubscribe in one click. We never share your address with the brands we review.
We respect your privacy. Chain188 uses cookies to keep the site running, measure traffic and improve your experience. Under the EU GDPR you can accept all non-essential cookies or keep only the essentials. See our Privacy Policy.
0 comments
No comments yet — ask a question and we will answer it here.