Can one person move the money in Rocket Pool RocketStorage on Ethereum? The authority score is 22 / 100 (weak): a small group with little delay.
In short. The guardian is a bare EOA, but its blanket write access is closed (getDeployedStatus is true) and the protocol DAO’s bootstrap mode is disabled. What is left to that key is the guardian handover itself, with no delay in that path.
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 | 55 |
|---|---|
| multisig | 0 |
| timelock | 0 |
| price feed | 100 |
| shared control | 100 |
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).
The guardian is a bare EOA, but its blanket write access is closed (getDeployedStatus is true) and the protocol DAO’s bootstrap mode is disabled. What is left to that key is the guardian handover itself, with no delay in that path.
$1.36B TVL, bare-EOA guardian with retired powers, composite 22
Pushed on-chain 2026-09-20 as target index 18 (same transaction). Scored 55 / 0 / 0: the admin score is not the 2 to 10 of a live bare-EOA admin because the powers are confirmed retired, and it is not a DAO score because an EOA still holds a named role. See score_rocketpool_storage().
Exit window: none: a change applies at once, 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 0 (score 22 is under MIN_SAFE_SCORE 60). Cheapest path to moderate (40): admin key from 55 to 99, that is a stronger admin setup (admin power spread beyond one key, or checked by others), 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 At least a 3-of-5 multisig (too few people need to agree).
[](https://realspap.github.io/oracle/p/ethereum-l1-0x1d8f8f00cfa6758d7be78336684788fb0ee0fa46.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).
Money behind it: $1.3B (DefiLlama), of which $996M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0x1d8f8f00cfa6758d7be78336684788fb0ee0fa46 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(0x1d8f8f00cfa6758d7be78336684788fb0ee0fa46) 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 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.
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":"0xd47875d00000000000000000000000001d8f8f00cfa6758d7be78336684788fb0ee0fa46"},"0xb5eb8d"]}'The 6th 32-byte word of the answer is the composite score (22 = 0x16); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.