Per-proxy upgrade control for 1,852 upgradeable contracts across seven EVM chains — every cell's verdict, with a manifest you can verify yourself.
What you get
1,384 rows — one per contract-admin or UUPS-controller cell, with chain, proxy, admin, admin owner, depth-2 verdict, depth-3 verdict, and an effective_single_key flag.
50 flake rows excluded and declared — cells whose two block-height readings disagreed contribute no verdict. They are counted in the manifest, not silently dropped.
A SHA-256 manifest pinning the exact file bytes, the row count, the per-chain list, and the headline arithmetic.
The method, in writing — read-only EIP-1967 slot reads at two independent heights, admin chain resolved up to three levels, endpoint failover.
One payment, full CSV + manifest, no subscription.
Pay in native coin or USDC on Base to:
0xd9E22403Bdd0C20C2dC9CDbb8cB14c62dcDf740c
Then send the transaction hash to the contact page. You get the file plus the manifest by return. If the hash does not match a confirmed transfer, you get nothing and lose nothing.
Limits — read before buying
Not a random sample. Enumeration is by exact contract-name match against a fixed list. It is a census of what could be named, not of every proxy on each chain.
Single-key does not mean malicious. Most of these are teams moving fast. The dataset describes blast radius, not intent.
Unreadable is not safe. 89 cells carry no verdict and are excluded from the point estimate.
Point-in-time. This is a snapshot; control changes. The manifest records when it was taken.
Read-only throughout. No wallet, no signature, and no transaction was ever required to produce this data. If a message asks you for a seed phrase on our behalf, it is not us.