Contract control history
Timelock on Base — who can change it, and what changed
Multisig + 24h+ timelockthis contract is a timelock with a 1d minimum delay
This timelock at 0xcc3e…4a02 on Base sits behind a 1d timelock. Gliese has recorded 2 control changes. Last checked 2026-09-07 19:59:50 UTC.
Timelock1d timelockBase
Current control surface
snapshot 2026-09-07 18:58:02 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 1dminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Queue transactiontimelock.queue_transaction | 2 | 0 |
| Total | 2 | 0 |
Recent changes
Setup-time events hidden- Transaction deployAndUpgradeTo() to 0xbde8…372d queuedtimelock.queue_transaction · tx 0x26c3c192…02b5f5 · block 51,009,042· 2026-09-07 18:57:11 UTC
- Transaction deployAndUpgradeTo() to 0xbde8…372d queuedtimelock.queue_transaction · tx 0x26c3c192…02b5f5 · block 51,009,042· 2026-09-07 18:57:11 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.