Contract control history
TimelockController on Base — who can change it, and what changed
Timelock under 24hthis contract is a timelock with a 0s minimum delay (under 24h)
This timelock at 0xd574…7c31 on Base sits behind a 0s timelock. Gliese has recorded 2 control changes. Last checked 2026-09-12 19:40:39 UTC.
Timelock0s timelockBase
Current control surface
snapshot 2026-09-12 18:45:23 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 |
| Call scheduledtimelock.call_scheduled | 1 | 0 |
| Total | 2 | 0 |
Recent changes
Setup-time events hidden- Scheduled call to 0x6d20…45ea executedtimelock.call_executed · tx 0xfc0b815c…fc5ab2 · block 51,224,682· 2026-09-12 18:45:11 UTC
- Call to 0x6d20…45ea scheduled, executable after 0stimelock.call_scheduled · tx 0x8f4fcd20…ba0614 · block 51,224,675· 2026-09-12 18:44:57 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.