Safe on Ethereum — 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 Ethereum is upgradeable, is controlled by a 1-of-2 Safe. Gliese has recorded 3 control changes. Last checked 2026-09-11 03:35:00 UTC.

1 critical, recentSafeSafeUpgradeableSafe 1/2Ethereum

0x04231dec0e632fcfcbaeaeaf14df22d022111c1c

Post on X Share on Telegram

Current control surface

snapshot 2026-09-11 01:40:29 UTC

Implementation: 0x4167…⁠461a
EIP-1967 logic contract; an upgrade changes this
Proxy admin: —
who can upgrade
Owner: —
owner()
Safe threshold: 1 of 2
signatures required to act
Safe owners · 1 of 2: 0x03c2…⁠1db9
0x3336…⁠47c7

Recorded events

Open in the feed →

Event	Real	Setup
Added ownersafe.added_owner	1	0
Changed fallback handlersafe.changed_fallback_handler	1	0
Changed master copysafe.changed_master_copy	1	0
Total	3	0

Recent changes

Setup-time events hidden

Safe fallback handler set to 0x3efc…⁠77f4
safe.changed_fallback_handler · tx 0xf54b5d75…⁠7a8596 · block 25,950,950
1h ago · 2026-09-11 01:44:23 UTC
Safe singleton changed to 0xedd1…⁠7c7e
safe.changed_master_copy · tx 0xf54b5d75…⁠7a8596 · block 25,950,950
1h ago · 2026-09-11 01:44:23 UTC
Signer 0x3336…⁠47c7 added to the Safe
safe.added_owner · tx 0xe5af9263…⁠00dee8 · block 25,950,924
2h ago · 2026-09-11 01:39:11 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.