Implementation upgrades
countProxy implementation changes on registry contracts in the selected period.
Dashboard · VantagePlanned
Smart Contract Upgrade Tracker: Proxy and Owner Changes
Which major protocol contracts changed their implementation, admin, owner or multisig signers this week?
Implementation, admin, owner and multisig signer changes on major protocol contracts, and the upgrades already queued in timelocks.
ShareEmail it
Blueprint
What the dashboard will show.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
Changes
Implementation, admin, owner and signer changes in the selected period.
Admin and owner changes
countProxy admin and owner changes on registry contracts in the period, renouncements included.
Multisig signer changes
countOwner, threshold, module and guard changes on the protocols' admin Safes in the period.
Changes made by a single key
countChanges in the period made by one key, with no timelock or multisig in the path.
Every change
Every change with its time, protocol, contract, the values before and after, the caller, the path taken, the protocol's value locked and the transaction.
Queued
Calls waiting in timelocks and when they can execute.
Calls queued now
countCalls queued in registry timelocks that have neither executed nor been cancelled.
Next call becomes executable
hoursTime until the earliest queued call can execute, with its protocol, target and function beside it.
Queued calls by protocol
countQueued timelock calls per protocol, split into upgrades, parameter changes and transfers.
Timelock queue
Each queued call with protocol, timelock, target, decoded function and arguments, the governance proposal behind it where one exists and the time it can execute.
- Period
- Last 7, 30 or 90 days
- Chain
- Ethereum and the other covered EVM chains
About
What it answers, and for whom.
Many large protocols run upgradeable contracts: a proxy whose code can be swapped, controlled by a multisig or a timelock. A change of implementation, admin, owner or signers is the moment a protocol's rules can change, and it is also the first trace of a compromised key. This dashboard lists those changes on major protocol contracts each week, along with the upgrades already queued in timelocks.
Each change shows the contract, what changed from and to, who made the call and through which path: a timelock delay, a multisig vote or a single key. Queued timelock calls are decoded, so readers can see what will execute and when, before it does.
Method
How it will be measured.
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 →- Proxy changes come from EIP-1967 Upgraded, AdminChanged and BeaconUpgraded logs, checked against the implementation and admin storage slots at the same block.
- Ownership changes come from OwnershipTransferred logs, and access-control changes from RoleGranted and RoleRevoked logs, on a registry of major protocol contracts.
- Safe multisig changes come from AddedOwner, RemovedOwner, ChangedThreshold, EnabledModule and ChangedGuard logs on the protocols' admin Safes.
- Timelock queues come from TimelockController CallScheduled, CallExecuted and Cancelled logs, with each target and its calldata decoded against the target's ABI.
- Each change is classed by its path: through a timelock, through a multisig with its threshold or by a single key.
The data it needs
Read from chain state and history
- address_labelsTo buildAddress labelsLabels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
- governance_votesTo buildGovernance proposals and votesProposals, votes, voting power and turnout in on-chain governors, with off-chain votes recorded with their source.
- defi_tvl_dailyTo buildDeFi value lockedAssets deposited in DeFi protocols per protocol, chain and asset at day end, valued with oracle prices, never double counting receipt tokens.
- EIP-1967 Upgraded, AdminChanged and BeaconUpgraded logs
- OwnershipTransferred, RoleGranted and RoleRevoked logs
- Safe AddedOwner, RemovedOwner, ChangedThreshold, EnabledModule and ChangedGuard logs
- TimelockController CallScheduled, CallExecuted and Cancelled logs, with decoded targets and calldata
- Implementation and admin storage slots via eth_getStorageAt at each change block
Questions
Questions people ask.
What is a smart contract upgrade?
Upgradeable contracts split into a proxy that holds the state and an implementation that holds the code. An upgrade points the proxy at a new implementation, which changes the contract's behaviour while keeping its address and balances.
Why do contract upgrades matter for security?
Whoever can upgrade a contract can change what it does with the funds it holds. An unexpected upgrade, admin change or signer change can be a planned release or a compromised key. Delays such as timelocks give users time to see a change before it takes effect.
What is a timelock?
A timelock is a contract that holds admin rights and executes calls only after a fixed delay from when they were queued. Queued calls are public, so a pending upgrade can be read before it takes effect, which is what the queue page shows.
How can I tell if a contract is upgradeable?
Check whether it is a proxy: an EIP-1967 proxy stores its implementation address in a standard storage slot, which can be read with eth_getStorageAt. A non-zero value there means the proxy's admin can change the code.
What does an ownership transfer mean?
OwnershipTransferred records that a contract's owner role moved to a new address. It can be a routine move to a multisig or timelock, a renouncement to the zero address or the first step of an attack, so each one here shows the new owner's type.
- Implementation contract
- The contract holding the code a proxy runs; replacing it is what an upgrade does.
- Proxy admin
- The address allowed to upgrade a proxy, often a multisig, a timelock or a dedicated admin contract.
- Timelock delay
- The minimum time a timelock waits between queuing a call and executing it.
- Safe threshold
- How many owner signatures a Safe multisig needs before it executes a transaction.
Related
More apps like this.
DeFi Admin Keys: Multisig Thresholds and Timelocks
Proxy admins, owners and multisig thresholds for each major protocol, with the timelock that stands between a change and its execution.
Multi-chainEthereumArbitrum+2Safe 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+3Token Safety Check: Mint, Blacklist and Owner Powers
The powers a token contract still keeps, from minting and blacklisting to pausing, fee changes and upgrades, read from the contract.
Multi-chainDAO Governance Tracker: On-Chain Proposals and Votes
Live and recent on-chain DAO proposals: votes cast, quorum progress, voting power and whether each passed and was executed.
Multi-chainEthereumArbitrum+1Crypto Hack Tracker: Exploits and Losses This Year
Every major hack and exploit of the year with the amount taken, how the attackers got in and where the stolen funds sit now.
Multi-chainNorth Korea Crypto Hacks: Lazarus Group Theft Tracker
Thefts attributed to North Korea-linked groups, what their attributed wallets still hold and how the funds move across chains.
Multi-chainEthereumBitcoinBuild Smart Contract Upgrade Tracker: Proxy and Owner Changes on verified data.
Start 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.