Can one person move the money in Compound V3 cUSDCv3 (Comet USDC) on Ethereum? The authority score is 79 / 100 (decent): a multisig and a delay, with gaps.
In short. Comet.governor(), the owner of the proxy admin and the Configurator’s governor all resolve to one Compound Timelock (2-day delay, which is also its floor) answering to the Compound Governor. The bypass found is a 5-of-9 Safe, the pauseGuardian, that can pause supply, transfer, withdraw, absorb and buy instantly.
Exposure, not intent. The score counts what the keys could do, not what their holders will do, and says nothing about the odds of a loss. Re-read it yourself with a public RPC and curl: how.
Try a fix: drag the sliders Open the live dashboard re-read from the chain every 6 hours; this page is the snapshot of the build
| admin key | 78 |
|---|---|
| multisig | 100 |
| timelock | 60 |
| price feed | 52 |
| shared control | 80 |
Composite = 40% admin key + 30% multisig + 30% timelock, rounded. Price feed and shared control are read and shown, not folded in.
To move the money: keys not read, 48 h to react.
Comet.governor(), the owner of the proxy admin and the Configurator’s governor all resolve to one Compound Timelock (2-day delay, which is also its floor) answering to the Compound Governor. The bypass found is a 5-of-9 Safe, the pauseGuardian, that can pause supply, transfer, withdraw, absorb and buy instantly.
$1.36B TVL (all Compound V3 markets on Ethereum)
The pauseGuardian Safe (no module, no guard) is also the Governor’s proposalGuardian and whitelistGuardian, so it can cancel proposals; its instant pause is a freeze (availability) power, not a fund-redirect one, which is why timelockScore is 60 rather than Uniswap’s 75.
Exit window: a confirmed delay, bypass paths not all checked, the time a user has to leave after a harmful change is queued.
If a market used the example policy today (src/ExampleConsumer.sol: revert when stale, 0 under 60, 50% to 80% above): collateral factor 64.25% (score 79). Cheapest path to strong (80): timelock from 60 to 61, that is a confirmed delay before changes apply, every other axis unchanged. This is the smallest step into the next band, not a fix for the weakness: the first requirement not met is Bypass paths of the delay checked and ruled out (the waiting time may be skipped).
[](https://realspap.github.io/oracle/p/ethereum-l1-0xc3d688b66703497daa19211eedff47f25384cdc3.html)
A live badge: the score is read from the published watch files every time the page that shows it loads. Change nothing but your own repository.
Not assessed for this contract: how many keys it takes to move it; the money behind one key (no money figure, or no key count).
Money behind it: $1.3B (DefiLlama), of which $273M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0xc3d688b66703497daa19211eedff47f25384cdc3 on the explorer ↗. Score pushed on-chain on 2026-10-13; stale on the oracle when older than 9 days (the watch re-reads it anyway). Read the score yourself: getScore(0xc3d688b66703497daa19211eedff47f25384cdc3) on the Ethereum oracle, listed in the repository.
Read at block 11922317, methodology 0x46a1a85b619e7db0…. The score reads the authority path (keys, multisigs, timelocks, roles, price feeds); it does not audit the code for bugs, and it measures exposure, not the chance of being hit (see the backtest in the repository). Dispute this score with evidence, or read this page as JSON.
Other hands: pauseGuardian() is a Safe 5-of-9 (0xbbf3…012c). A role is named by its getter, what it can do depends on the protocol (in a MetaMorpho vault guardian() can revoke a pending change, it does not move funds). A change is an alert.
Read live: admin: a timelock; delay: 48 h on the timelock.
Independent read of the admin: a timelock, 172800s delay 0x6d903f60…3925 via EIP-1967 admin -> ProxyAdmin owner(), consistent with the published admin-key score. Unchanged since 2026-10-10. Implementation behind the proxy: 0x63e749153baf1838f63ca22c275370bd2b1ceb15 (EIP-1967 implementation slot). Its source is verified on Sourcify (CometWithExtendedAssetList, exact match, 0.8.15+commit.e14f2714). (scripts/second_opinion.py: a reader that shares nothing with the scorer, re-run every 6 hours)
Score unchanged since its publication on 2026-10-13; every later move will be a line of the hash-chained log. Methodology changed on 2026-10-13: points before that date come from another method and are not comparable.
# the admin slot of the proxy (EIP-1967): the word is the admin address
curl -s -X POST https://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getStorageAt","params":["0xc3d688b66703497daa19211eedff47f25384cdc3","0xb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d6103","latest"]}'
# owner() on the address the slot returned (a ProxyAdmin): the holder
curl -s -X POST https://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"<address from the slot>","data":"0x8da5cb5b"},"latest"]}'
# delay() on the holder (Compound-style timelock), in seconds
curl -s -X POST https://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x6d903f6003cca6255d85cca4d3b5e5146dc33925","data":"0x6a42b8f8"},"latest"]}'
# the implementation slot of the proxy (EIP-1967): the code behind it, an upgrade changes this word
curl -s -X POST https://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getStorageAt","params":["0xc3d688b66703497daa19211eedff47f25384cdc3","0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc","latest"]}'Each answer is a 32-byte word (an address sits in its last 20 bytes); the admin path is the one scripts/second_opinion.py reports for this contract. read between blocks 26199869 and 26199870 of the chain; this RPC cannot replay the block of the read (it ignores the block tag, or no longer serves old state): the answers are the current ones
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
curl -s -X POST https://ethereum-sepolia-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xB6F8474ccC71AF477c31c2DF663B3942ddfbf906","data":"0xd47875d0000000000000000000000000c3d688b66703497daa19211eedff47f25384cdc3"},"0xb5eb8d"]}'The 6th 32-byte word of the answer is the composite score (79 = 0x4f); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.