Contract control history
EtherFiTimelock on OP Mainnet — who can change it, and what changed
Multisig + 24h+ timelockthis contract is a timelock with a 1d minimum delay
This timelock at 0xbaca…e283 on OP Mainnet sits behind a 1d timelock. Gliese has recorded 4 control changes and 5 deployment-time events. Last checked 2026-09-12 01:58:52 UTC.
Timelock1d timelockOP Mainnet
Current control surface
snapshot 2026-09-12 01:25:49 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 1dminimum wait between queue and execution
Recorded events
Open in the feed →Recent changes
Setup-time events hidden- Call to 0xbaca…e283 scheduled, executable after 1dtimelock.call_scheduled · tx 0x040f0b72…389762 · block 156,788,734· 2026-09-12 01:24:05 UTC
- Call to 0xbaca…e283 scheduled, executable after 1dtimelock.call_scheduled · tx 0x040f0b72…389762 · block 156,788,734· 2026-09-12 01:24:05 UTC
- Call to 0xbaca…e283 scheduled, executable after 1dtimelock.call_scheduled · tx 0x040f0b72…389762 · block 156,788,734· 2026-09-12 01:24:05 UTC
- Call to 0xbaca…e283 scheduled, executable after 1dtimelock.call_scheduled · tx 0x040f0b72…389762 · block 156,788,734· 2026-09-12 01:24:05 UTC
Get alerted when this contract’s control changes
Free for personal wallets. Telegram, within a minute of the block.
Critical — power movedHigh — safeguards changedInfo — announced, not yet effective
Data derived from on-chain state and events only. Gliese does not custody funds and does not interpret intent — severity is assigned by how much power a change moves.