GlieseGliese — protocol change radar
Explorer ↗Watch this contract
Contract control history

AgentVaultManagerOFT on Arbitrum One — who can change it, and what changed

Multisig, no delayadmin 0x0d86…4377 is a contract · no timelock in the path

This transparent proxy at 0x2942…⁠9d4a on Arbitrum One is upgradeable, sits behind a 1m timelock. Gliese has recorded 6 control changes. Last checked 2026-09-08 02:50:10 UTC.

Transparent proxyUpgradeable1m timelockArbitrum One
0x294258fa3e2905f38c7a605fd37ff18985a89d4a
Post on XShare on Telegram

Current control surface

snapshot 2026-09-08 01:52:43 UTC
Implementation
0x322d…⁠4115
EIP-1967 logic contract; an upgrade changes this
Proxy admin
0x0d86…⁠4377
who can upgrade
Owner
0x9089…⁠ee7d
owner()
Timelock delay
1m
minimum wait between queue and execution

Recorded events

Open in the feed →

Recent changes

Setup-time events hidden
  1. Scheduled call to 0x7e26…⁠2f61 executed
    timelock.call_executed · tx 0xfeb7a7fa…⁠8f750f · block 502,901,608
    · 2026-09-08 04:06:01 UTC
  2. Scheduled call to 0xfd08…⁠cbb9 executed
    timelock.call_executed · tx 0xfeb7a7fa…⁠8f750f · block 502,901,608
    · 2026-09-08 04:06:01 UTC
  3. Call to 0x7e26…⁠2f61 scheduled, executable after 1m
    timelock.call_scheduled · tx 0xcb6f34a4…⁠a866ec · block 502,900,196
    · 2026-09-08 04:00:06 UTC
  4. Call to 0xfd08…⁠cbb9 scheduled, executable after 1m
    timelock.call_scheduled · tx 0xcb6f34a4…⁠a866ec · block 502,900,196
    · 2026-09-08 04:00:06 UTC
  5. Scheduled call to 0xb16f…⁠55f9 executed
    timelock.call_executed · tx 0xce742325…⁠6309da · block 502,870,554
    · 2026-09-08 01:55:59 UTC
  6. Call to 0xb16f…⁠55f9 scheduled, executable after 1m
    timelock.call_scheduled · tx 0xb17836c6…⁠4f9221 · block 502,869,675
    · 2026-09-08 01:52:17 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 contractTelegram 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.