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 0xf59b…⁠0681 on Base is controlled by a 1-of-1 Safe. Gliese has recorded 2 control changes and 2 deployment-time events. Last checked 2026-09-08 21:37:02 UTC.

1 critical, recentSafeSafeSafe 1/1Base

0xf59b3769dc510efcecca1fa6cc17f87043500681

Post on X Share on Telegram

Current control surface

snapshot 2026-09-08 20:30:30 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: 0xa909…⁠68b2

Recorded events

Open in the feed →

Event	Real	Setup
Changed master copysafe.changed_master_copy	0	1
Disabled modulesafe.disabled_module	1	0
Enabled modulesafe.enabled_module	1	0
Setupsafe.setup	0	1
Total	2	2

Recent changes

Setup-time events hidden

Module 0x760e…⁠7e7a disabled
safe.disabled_module · tx 0xf5e75819…⁠dd6876 · block 51,055,006
1h ago · 2026-09-08 20:29:19 UTC
Module 0x760e…⁠7e7a enabled — can execute without signatures
safe.enabled_module · tx 0xf5e75819…⁠dd6876 · block 51,055,006
1h ago · 2026-09-08 20:29:19 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.