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

Multisig + 24h+ timelockthis contract is a timelock with a 1d minimum delay

This timelock at 0xd3a5…⁠13db on Base sits behind a 1d timelock. Gliese has recorded 1 control change and 5 deployment-time events. Last checked 2026-09-09 01:48:46 UTC.

Timelock1d timelockBase

0xd3a5975be4ed37f471ab377aed1003bfc1f613db

Post on X Share on Telegram

Current control surface

snapshot 2026-09-09 01:14:22 UTC

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

Recorded events

Open in the feed →

Event	Real	Setup
Role grantedaccess.role_granted	0	4
Call scheduledtimelock.call_scheduled	1	0
Min delay changedtimelock.min_delay_changed	0	1
Total	1	5

Recent changes

Setup-time events hidden

Call to 0xf149…⁠0621 scheduled, executable after 1d
timelock.call_scheduled · tx 0xd0b62365…⁠307a43 · block 51,063,515
10h ago · 2026-09-09 01:12:57 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.