SafeProxy on Base — who can change it, and what changed

Upgradeable by a single keySafe 1 of 1: one signature is enough

This Safe safe at 0xe94c…⁠6102 on Base is controlled by a 1-of-1 Safe. Gliese has recorded 2 control changes and 3 deployment-time events. Last checked 2026-09-10 17:46:58 UTC.

1 critical, recentSafeSafeSafe 1/1Base

0xe94c8e3d34399955af76116615549f8964f66102

Post on X Share on Telegram

Current control surface

snapshot 2026-09-10 16:01:36 UTC

Implementation: —
EIP-1967 logic contract; an upgrade changes this
Proxy admin: —
who can upgrade
Owner: —
owner()
Safe threshold: 1 of 1
signatures required to act
Safe owners · 1 of 1: 0x1b3a…⁠e523

Recorded events

Open in the feed →

Event	Real	Setup
Added ownersafe.added_owner	1	0
Changed fallback handlersafe.changed_fallback_handler	0	1
Enabled modulesafe.enabled_module	0	1
Removed ownersafe.removed_owner	1	0
Setupsafe.setup	0	1
Total	2	3

Recent changes

Setup-time events hidden

Signer 0x1b3a…⁠e523 added to the Safe
safe.added_owner · tx 0xeb80cae3…⁠c0976c · block 51,133,344
2h ago · 2026-09-10 16:00:35 UTC
Signer 0xbe81…⁠51f9 removed from the Safe
safe.removed_owner · tx 0xeb80cae3…⁠c0976c · block 51,133,344
2h ago · 2026-09-10 16:00:35 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.