Contract control history
TimelockController on Ethereum — who can change it, and what changed
Timelock under 24hthis contract is a timelock with a 5m minimum delay (under 24h)
This timelock at 0xbbeb…f91f on Ethereum sits behind a 5m timelock. Gliese has recorded 2 control changes. Last checked 2026-09-07 19:58:10 UTC.
1 critical, recentTimelock5m timelockEthereum
Current control surface
snapshot 2026-09-07 19:16:18 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 5mminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Call executedtimelock.call_executed | 1 | 0 |
| Min delay changedtimelock.min_delay_changed | 1 | 0 |
| Total | 2 | 0 |
Recent changes
Setup-time events hidden- Scheduled call to 0xbbeb…f91f executedtimelock.call_executed · tx 0x581366fd…5c69c1 · block 25,927,500· 2026-09-07 19:14:47 UTC
- Timelock minimum delay changed from 3d to 5mtimelock.min_delay_changed · tx 0x581366fd…5c69c1 · block 25,927,500· 2026-09-07 19:14:47 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.