Safe Multisig Checker: Owners, Threshold and Modules
Inspect a Safe before trusting it: its signers, how many must sign, the modules and guards that can act on it and its recent changes.
Multi-chainEthereumBase+3Who can upgrade or move funds in each major protocol, how many signers must agree and how long is the timelock?
Proxy admins, owners and multisig thresholds for each major protocol, with the timelock that stands between a change and its execution.
The table as it will open in Strata. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
One row One row per protocol contract and power, such as upgrade, pause or move funds, at a pinned blockSorted by Value at stake, highest first
| Protocol | Contract | Chain | Power | Held by | Holder | Threshold | Timelock delayhours | Safe modules | Value at stakeUSD | Last change | Receipt |
|---|---|---|---|---|---|---|---|---|---|---|---|
Filter by Chain, Held by, Power.
Most DeFi protocols can be changed after launch. A proxy admin can swap the code behind a contract and an owner can change parameters or move funds. Those powers usually sit with a multisig, a timelock or a governance contract. This table shows, for each major protocol, who holds each power, how many signers must agree and how long a change must wait before it can run.
Every row comes from contract state: the EIP-1967 admin and implementation slots, owner() and role assignments, a Safe's owners and threshold and a timelock's minimum delay. It describes control, not quality: a short delay or a low threshold is a fact to weigh, not a verdict on a protocol. Each row links to the reads behind it.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →Read from chain state and history
Any address with special power over a protocol's contracts: upgrading their code, pausing them, changing parameters or moving funds. It can be a single wallet, a multisig, a timelock or a governance contract.
A multisig needs a set number of its signers to approve each transaction, such as three of five. A higher threshold makes one stolen key less dangerous, though how independent the signers are matters as much as how many there are.
A timelock forces a wait between when a change is queued and when it can run. During that window anyone can see the pending change on-chain and withdraw if they disagree, which is why a missing or very short delay is worth noticing.
Admin keys are a trade-off. They let teams fix bugs and respond to attacks, and they also let a compromised or malicious key change the rules. This table shows who holds each power and what stands in its way, so readers can weigh that trade-off themselves.
A contract that forwards every call to a separate implementation contract whose address can be changed. Users keep interacting with the same address while the code behind it can be replaced by whoever controls the proxy.
Inspect a Safe before trusting it: its signers, how many must sign, the modules and guards that can act on it and its recent changes.
Multi-chainEthereumBase+3Implementation, admin, owner and multisig signer changes on major protocol contracts, and the upgrades already queued in timelocks.
Multi-chainEthereumThe powers a token contract still keeps, from minting and blacklisting to pausing, fee changes and upgrades, read from the contract.
Multi-chainEvery major hack and exploit of the year with the amount taken, how the attackers got in and where the stolen funds sit now.
Multi-chainLive and recent on-chain DAO proposals: votes cast, quorum progress, voting power and whether each passed and was executed.
Multi-chainEthereumArbitrum+1DeFi value locked on each chain, counted once at oracle prices, with the chain ranking, Ethereum's share and the protocols behind it.
Multi-chainEthereumSolana+3Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.