TimelockController on Base — who can change it, and what changed

Timelock under 24hthis contract is a timelock with a 1h minimum delay (under 24h)

This timelock at 0xb285…⁠df17 on Base sits behind a 1h timelock. Gliese has recorded 2 control changes and 9 deployment-time events. Last checked 2026-09-13 19:59:35 UTC.

Timelock1h timelockBase

0xb285e953b1832f7009aab1289b499e0c3591df17

Post on X Share on Telegram

Current control surface

snapshot 2026-09-13 18:57:33 UTC

Implementation: —
EIP-1967 logic contract; an upgrade changes this
Proxy admin: —
who can upgrade
Owner: —
owner()
Timelock delay: 1h
minimum wait between queue and execution

Recorded events

Open in the feed →

Event	Real	Setup
Role admin changedaccess.role_admin_changed	0	4
Role grantedaccess.role_granted	0	4
Call executedtimelock.call_executed	1	0
Call scheduledtimelock.call_scheduled	1	0
Min delay changedtimelock.min_delay_changed	0	1
Total	2	9

Recent changes

Setup-time events hidden

Scheduled call to 0xd1ec…⁠b297 executed
timelock.call_executed · tx 0x6b63bd68…⁠9bdd98 · block 51,270,119
1h ago · 2026-09-13 19:59:45 UTC
Call to 0xd1ec…⁠b297 scheduled, executable after 1h
timelock.call_scheduled · tx 0xa8218371…⁠793aa7 · block 51,268,221
2h ago · 2026-09-13 18:56:29 UTC

Full history since deployment →

Get alerted when this contract’s control changes

Free for personal wallets. Telegram, within a minute of the block.

Watch this contract Telegram bot ↗

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.