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

This Safe safe at 0x4fc0…⁠8594 on Base is controlled by a 2-of-4 Safe. Gliese has recorded 2 control changes and 2 deployment-time events. Last checked 2026-09-06 16:54:28 UTC.

2 critical, recentSafeSafeSafe 2/4Base

0x4fc091925ee12404e235bb87f9f2f7c8df128594

Post on X Share on Telegram

Current control surface

snapshot 2026-09-06 16:54:28 UTC

Implementation: —
EIP-1967 logic contract; an upgrade changes this
Proxy admin: —
who can upgrade
Owner: —
owner()
Safe threshold: 2 of 4
signatures required to act
Safe owners · 2 of 4: 0x69cb…⁠173f
0x8899…⁠9512
0xedb1…⁠5e48
0xedf9…⁠7b9f

Recorded events

Open in the feed →

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

Recent changes

Setup-time events hidden

Module 0x23d5…⁠e0f6 enabled — can execute without signatures
safe.enabled_module · tx 0x7bbba33a…⁠fac89c · block 50,962,337
1h ago · 2026-09-06 17:00:21 UTC
Safe threshold changed to 2
safe.changed_threshold · tx 0x233fed59…⁠010543 · block 50,962,120
1h ago · 2026-09-06 16:53:07 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.