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 0x88cc…2783 on Base sits behind a 1m timelock. Gliese has recorded 2 control changes. Last checked 2026-09-09 00:45:49 UTC.
Timelock1m timelockBase
Current control surface
snapshot 2026-09-09 00:22:36 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 | 1 | 0 |
| Call scheduledtimelock.call_scheduled | 1 | 0 |
| Total | 2 | 0 |
Recent changes
Setup-time events hidden- Scheduled call to 0xc6cd…e12d executedtimelock.call_executed · tx 0x311362e6…ff8c7a · block 51,062,011· 2026-09-09 00:22:49 UTC
- Call to 0xc6cd…e12d scheduled, executable after 1mtimelock.call_scheduled · tx 0x1f1d2530…1944d9 · block 51,061,968· 2026-09-09 00:21:23 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.