Contract control history
TimelockController on Base — who can change it, and what changed
Multisig + 24h+ timelockthis contract is a timelock with a 2d minimum delay
This timelock at 0x4fd2…bf89 on Base sits behind a 2d timelock. Gliese has recorded 2 control changes. Last checked 2026-09-09 20:57:11 UTC.
Timelock2d timelockBase
Current control surface
snapshot 2026-09-09 20:24:51 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 2dminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Call scheduledtimelock.call_scheduled | 2 | 0 |
| Total | 2 | 0 |
Recent changes
Setup-time events hidden- Call to 0xd475…eda7 scheduled, executable after 2dtimelock.call_scheduled · tx 0x731a5e55…63d815 · block 51,098,046· 2026-09-09 20:23:59 UTC
- Call to 0xb235…22c4 scheduled, executable after 2dtimelock.call_scheduled · tx 0x731a5e55…63d815 · block 51,098,046· 2026-09-09 20:23: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.