Can one person move the money in USDS (Sky) on Ethereum? The authority score is 81 / 100 (strong): a multisig behind a long delay.
In short. An EIP-1967 upgradeable proxy whose mint and upgrade rights are wards: the Sky governance pause proxy and the UsdsJoin adapter. Nobody else holds one.
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 | 75 |
|---|---|
| multisig | 100 |
| timelock | 70 |
| price feed | 100 |
| shared control | 40 |
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 and hours to react not read for this contract (never shown as zero).
An EIP-1967 upgradeable proxy whose mint and upgrade rights are wards: the Sky governance pause proxy and the UsdsJoin adapter. Nobody else holds one.
Sky governance, 2-day pause, composite 81
Added 2026-10-11. Scored with the Sky pause target's own values (75 / 100 / 70, composite 81). The ward set is replayed from the token's Rely and Deny history on every pass and must be exactly those two; a third ward degrades the score. Shares its root with the Sky pause, SparkLend and DAI.
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 65.75% (score 81). Already in the top band.
[](https://realspap.github.io/oracle/p/ethereum-l1-0xdc035d45d973e3ec169d2276ddab16f1e407384f.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: who holds the admin power: the independent reader could not classify the holder; how many keys it takes to move it; the time anyone has to react; the money behind one key (no money figure, or no key count); the protocol's total value locked (no DefiLlama match).
Contract: 0xdc035d45d973e3ec169d2276ddab16f1e407384f 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(0xdc035d45d973e3ec169d2276ddab16f1e407384f) 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.
Independent read of the admin: not possible here (no admin slot, owner(), admin(), DEFAULT_ADMIN_ROLE member or authority() answered). (scripts/second_opinion.py: a reader that shares nothing with the scorer, re-run every 6 hours)
Score over time (2 points, 2026-10-11 to 2026-10-13, from the chained log): 81 to 81 Methodology changed on 2026-10-13: points before that date come from another method and are not comparable.
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":"0xd47875d0000000000000000000000000dc035d45d973e3ec169d2276ddab16f1e407384f"},"0xb5eb8d"]}'The 6th 32-byte word of the answer is the composite score (81 = 0x51); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.