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 0x0423…1c1c on Base is controlled by a 1-of-2 Safe. Gliese has recorded 3 control changes and 2 deployment-time events. Last checked 2026-09-11 03:38:02 UTC.
Current control surface
snapshot 2026-09-11 01:47: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 →Recent changes
Setup-time events hidden- Safe fallback handler set to 0x3efc…77f4safe.changed_fallback_handler · tx 0x68ede7de…68230b · block 51,150,946· 2026-09-11 01:47:19 UTC
- Safe singleton changed to 0xedd1…7c7esafe.changed_master_copy · tx 0x68ede7de…68230b · block 51,150,946· 2026-09-11 01:47:19 UTC
- Signer 0x3336…47c7 added to the Safesafe.added_owner · tx 0xc5eea58b…e85fc4 · block 51,150,936· 2026-09-11 01:46:59 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.