Contract control history
TimelockController on Base — who can change it, and what changed
Timelock under 24hthis contract is a timelock with a 1m minimum delay (under 24h)
This timelock at 0x01fe…9fca on Base sits behind a 1m timelock. Gliese has recorded 8 control changes. Last checked 2026-09-15 10:07:10 UTC.
Timelock1m timelockBase
Current control surface
snapshot 2026-09-15 09:20:26 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 1mminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Call executedtimelock.call_executed | 4 | 0 |
| Call scheduledtimelock.call_scheduled | 4 | 0 |
| Total | 8 | 0 |
Recent changes
Setup-time events hidden- Scheduled call to 0x3387…2a5e executedtimelock.call_executed · tx 0x91f13446…d792e6 · block 51,339,318· 2026-09-15 10:26:23 UTC
- Call to 0x3387…2a5e scheduled, executable after 1mtimelock.call_scheduled · tx 0xf865fd22…201204 · block 51,339,270· 2026-09-15 10:24:47 UTC
- Scheduled call to 0x1009…54e3 executedtimelock.call_executed · tx 0x1ff8b283…eceb87 · block 51,338,317· 2026-09-15 09:53:01 UTC
- Call to 0x1009…54e3 scheduled, executable after 1mtimelock.call_scheduled · tx 0xa6e9c454…712ff8 · block 51,338,231· 2026-09-15 09:50:09 UTC
- Scheduled call to 0x7c18…239d executedtimelock.call_executed · tx 0x67b03442…a53312 · block 51,337,972· 2026-09-15 09:41:31 UTC
- Call to 0x7c18…239d scheduled, executable after 1mtimelock.call_scheduled · tx 0x0c05de22…dd236c · block 51,337,919· 2026-09-15 09:39:45 UTC
- Scheduled call to 0x7c18…239d executedtimelock.call_executed · tx 0xd990f8bf…c65f90 · block 51,337,653· 2026-09-15 09:30:53 UTC
- Call to 0x7c18…239d scheduled, executable after 1mtimelock.call_scheduled · tx 0x8428efeb…41468e · block 51,337,319· 2026-09-15 09:19:45 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.