Contract control history
TimelockController on Base — who can change it, and what changed
This timelock at 0xfddf…c62f on Base sits behind a 0s timelock. Gliese has recorded 2 control changes. Last checked 2026-09-06 11:28:47 UTC.
1 critical, recentTimelock0s timelockBase
Current control surface
snapshot 2026-09-06 11:28:47 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 0sminimum 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 0xfddf…c62f executedtimelock.call_executed · tx 0xe09bd139…c0b9fb · block 50,940,186· 2026-09-06 04:41:59 UTC
- Timelock minimum delay changed from 1d to 0stimelock.min_delay_changed · tx 0xe09bd139…c0b9fb · block 50,940,186· 2026-09-06 04:41:59 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.