Can one person move the money in Beefy: SPY-WETH vault (representative) on Robinhood Chain? The authority score is 50 / 100 (moderate): a multisig without a real delay, the band where Bybit, WazirX and Radiant sat when they were drained.
In short. Vault and strategy each sit behind a separate real TimelockController, both governed by the identical 3-of-6 Safe - the vault-level delay is 0, but the strategy-swap path (the highest-value action) carries a real 6h delay two ways over.
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 | 65 |
|---|---|
| multisig | 60 |
| timelock | 20 |
| 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).
Vault and strategy each sit behind a separate real TimelockController, both governed by the identical 3-of-6 Safe - the vault-level delay is 0, but the strategy-swap path (the highest-value action) carries a real 6h delay two ways over.
~$2.57M TVL across ~14 vaults, one sampled
The deployer’s own TIMELOCK_ADMIN_ROLE was revoked one block after deployment on both Timelocks - each self-administers now. Same Safe holds PROPOSER_ROLE and CANCELLER_ROLE on both, so there is no independent veto path, the same limitation already scored this way for this chain’s own L1 rollup authority.
Exit window: a delay with a bypass, or one not ruled out, 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 50 is under MIN_SAFE_SCORE 60). Cheapest path to decent (60): admin key from 65 to 89, 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 A confirmed delay before changes apply, no bypass (changes can apply with no waiting time).
[](https://realspap.github.io/oracle/p/robinhood-0x87673a619fc4f3fc08068a0bb04f60aa2d04ca62.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 time anyone has to react; the money behind one key (no money figure, or no key count).
Money behind it: $3M (DefiLlama), of which $1M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0x87673a619fc4f3fc08068a0bb04f60aa2d04ca62 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(0x87673a619fc4f3fc08068a0bb04f60aa2d04ca62) on the Robinhood Chain oracle, listed in the repository.
Read at block 136039274, methodology 0x667dc486af9557a8…. 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.
Read live: admin: a timelock; delay: none.
Independent read of the admin: a timelock, 0s delay 0x03193ef8…4cbc via owner(), consistent with the published admin-key score. Unchanged since 2026-10-10. (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.
# owner() on the contract: the holder
curl -s -X POST https://rpc.mainnet.chain.robinhood.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x87673a619fc4f3fc08068a0bb04f60aa2d04ca62","data":"0x8da5cb5b"},"0x55508a0"]}'
# getMinDelay() on the holder (OpenZeppelin TimelockController), in seconds
curl -s -X POST https://rpc.mainnet.chain.robinhood.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x03193ef8c3f75c22faf2995540602399cdcd4cbc","data":"0xf27a0c92"},"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 89458462 and 89458848 of the chain
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
curl -s -X POST https://rpc.testnet.chain.robinhood.com/rpc -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x9BF45734D09bC7CA39238e767B2af9AAc62a7f52","data":"0xd47875d000000000000000000000000087673a619fc4f3fc08068a0bb04f60aa2d04ca62"},"latest"]}'The 6th 32-byte word of the answer is the composite score (50 = 0x32); the 7th is the push timestamp. This RPC cannot replay the block of the build (it ignores the block tag, or no longer serves old state), so the value is the current one: compare the composite and the push timestamp with this page.