Contract control history
SafeProxy on OP Mainnet — who can change it, and what changed
Upgradeable by a single keySafe 1 of 4: one signature is enough
This Safe safe at 0x86f8…67ff on OP Mainnet is controlled by a 1-of-4 Safe. Gliese has recorded 2 control changes and 3 deployment-time events. Last checked 2026-09-11 01:27:10 UTC.
Current control surface
snapshot 2026-09-10 22:11:20 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Safe threshold
- 1 of 4signatures required to act
- Safe owners · 1 of 4
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Added ownersafe.added_owner | 2 | 1 |
| Enabled modulesafe.enabled_module | 0 | 1 |
| Setupsafe.setup | 0 | 1 |
| Total | 2 | 3 |
Recent changes
Setup-time events hidden- Signer 0xed3e…86d9 added to the Safesafe.added_owner · tx 0xaa47be46…9881fe · block 156,739,716· 2026-09-10 22:10:09 UTC
- Signer 0x13f0…2f49 added to the Safesafe.added_owner · tx 0x11910dbf…b22aaf · block 156,718,318· 2026-09-10 10:16:53 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.