Contract control history
SafeProxy on Base — who can change it, and what changed
Upgradeable by a single keySafe 1 of 2: one signature is enough
This Safe safe at 0xe917…f1be on Base is controlled by a 1-of-2 Safe. Gliese has recorded 2 control changes and 2 deployment-time events. Last checked 2026-09-14 12:47:49 UTC.
Current control surface
snapshot 2026-09-14 11:15:40 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Safe threshold
- 1 of 2signatures required to act
- Safe owners · 1 of 2
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Added ownersafe.added_owner | 1 | 0 |
| Changed guardsafe.changed_guard | 1 | 0 |
| Enabled modulesafe.enabled_module | 0 | 1 |
| Setupsafe.setup | 0 | 1 |
| Total | 2 | 2 |
Recent changes
Setup-time events hidden- Safe guard set to 0xc9e2…10dasafe.changed_guard · tx 0xf7a4e998…860a8f · block 51,297,569· 2026-09-14 11:14:45 UTC
- Signer 0x4168…18fa added to the Safesafe.added_owner · tx 0xf7a4e998…860a8f · block 51,297,569· 2026-09-14 11:14:45 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.