Contract control history
YFiTimelockController on Ethereum — who can change it, and what changed
Timelock under 24hthis contract is a timelock with a 0s minimum delay (under 24h)
This timelock at 0x65d6…eff1 on Ethereum sits behind a 0s timelock. Gliese has recorded 4 control changes. Last checked 2026-09-07 22:39:22 UTC.
Timelock0s timelockEthereum
Current control surface
snapshot 2026-09-07 22:20:56 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 0sminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Call executedtimelock.call_executed | 2 | 0 |
| Call scheduledtimelock.call_scheduled | 2 | 0 |
| Total | 4 | 0 |
Recent changes
Setup-time events hidden- Scheduled call to 0x5e51…2ac9 executedtimelock.call_executed · tx 0x3b398c25…dc5706 · block 25,928,551· 2026-09-07 22:45:59 UTC
- Call to 0x5e51…2ac9 scheduled, executable after 0stimelock.call_scheduled · tx 0xe8677b8f…988e5d · block 25,928,498· 2026-09-07 22:35:23 UTC
- Scheduled call to 0x2266…33fb executedtimelock.call_executed · tx 0xb155c314…404976 · block 25,928,460· 2026-09-07 22:27:47 UTC
- Call to 0x2266…33fb scheduled, executable after 0stimelock.call_scheduled · tx 0x24cc65a8…c13c69 · block 25,928,417· 2026-09-07 22:19: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.