Contract Powers Registry / ethereum
Safe singleton 1.4.1
0x41675c099f32341bf84bfc5382af534df5c7461a on ethereum
In one line: verified, non-upgradeable, no privileged powers matched.
Can this code be replaced?
No proxy pattern found. The standard upgrade slots (EIP-1967, ZeppelinOS)
are empty, the explorer does not declare a proxy, and no implementation() answered.
The code at this address is very likely the code that runs.
Caveat: a custom upgrade mechanism that does not use those slots would not be detected here.
Who holds the keys?
no owner()/getOwner()/admin() responded — access control may use roles (AccessControl) or be renounced Access control may use role-based permissions (OpenZeppelin AccessControl), or it may have been renounced. This registry does not enumerate role holders.
What the privileged role can still do
No privileged capability matched — no mint, pause, blacklist, fee, sweep or upgrade function was found in the code or in the verified interface. This is not proof there is none. A capability can be spelled in a way this registry does not match, or reached through another contract this one trusts.
Is there a bug bounty on this?
No live bug-bounty program matched this contract’s name in my index (186 Immunefi + 52 Cantina programs, rebuilt daily). Matching is by name, not by address — a program can cover this contract without the names lining up. Browse the full index at Bounty Radar.
Raw facts
| Chain | ethereum (chainId 1) |
|---|---|
| Contract name | Safe |
| Compiler | v0.7.6+commit.7338295f |
| License | GNU LGPLv3 |
| Bytecode size | 23,579 bytes |
| DELEGATECALL | present |
| SELFDESTRUCT | absent |
| CREATE2 | absent |
| Explorer | view on block explorer ↗ |
How this was produced, and what it cannot tell you
Storage slots, bytecode and eth_call results were read from public RPC nodes;
where the source is verified, the published interface was read too. Nothing here is copied from another
site’s opinion. Generated in 196 ms on 2026-08-29.
- confidence="declared" means the ABI exposes the function. confidence="bytecode-heuristic" means the 4-byte selector appears in the code — usually its own dispatch table, but it can also be a selector this contract CALLS on another contract. Only a verified ABI settles it.
- admin.ownerType="contract" does not mean multisig — this endpoint does not inspect the owner contract.
- bounty.match="name-heuristic" matches a contract NAME to a program name; it is not proof the address is in scope.
What would change the answer: an upgrade after the date above; a power reachable only through a contract this one trusts; or role-based access control, whose holders this registry does not enumerate. Re-read the chain before you rely on it.
Machine-readable
Same facts as JSON, free, no key: /c/ethereum/0x41675c099f32341bf84bfc5382af534df5c7461a.json.
Live lookups for any address (not just this list) are $0.05 per call.
Want a human-grade read?
This page is automated pattern-matching. If you need someone to actually read the code and tell you what breaks, I do fixed-scope micro-audits — you pay after you read the report.