Can one person move the money in Morpho Grove x Steakhouse + Steakhouse Turbo USDG vaults on Robinhood Chain? The authority score is 40 / 100 (moderate): a multisig without a real delay, the band where Bybit, WazirX and Radiant sat when they were drained.
In short. Two more Steakhouse-curated Morpho vaults on this chain, found via the curator registry DefiLlama’s own dashboard actually reads from (not the per-protocol page, which 404s) - confirmed live before being added, not trusted from the registry file alone.
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 | 20 |
|---|---|
| multisig | 30 |
| timelock | 75 |
| 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 not read, 24 h to react.
Two more Steakhouse-curated Morpho vaults on this chain, found via the curator registry DefiLlama’s own dashboard actually reads from (not the per-protocol page, which 404s) - confirmed live before being added, not trusted from the registry file alone.
batch 13 - closed a DefiLlama-adapter gap
Both vaults’ curator()/owner()/asset() (USDG) resolved live on two independent RPCs before either was tracked. Same chain-wide zero-delay setOwner/setCurator gap already disclosed for every other Morpho vault on this chain - not a new finding specific to these two.
Exit window: a confirmed delay, bypass paths 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 0 (score 40 is under MIN_SAFE_SCORE 60). Cheapest path to decent (60): admin key from 20 to 70, 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 Admin power is not a bare key (one key, or a tiny group, can change it).
[](https://realspap.github.io/oracle/p/robinhood-0xbeeff039907422219fb367e525954ddc092854d9.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: $525M (DefiLlama), of which $315M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0xbeeff039907422219fb367e525954ddc092854d9 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(0xbeeff039907422219fb367e525954ddc092854d9) 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.
Other hands: curator() is a Safe 2-of-2 (0x622e…c0fc). 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: 24 h on the timelock.
Independent read of the admin: a timelock, 86400s delay 0x5ff98717…9296 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 over time (3 points, 2026-10-10 to 2026-10-13, from the chained log): 44 to 40 to 40 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":"0xbeeff039907422219fb367e525954ddc092854d9","data":"0x8da5cb5b"},"0x55508a0"]}'
# delay() on the holder (Compound-style timelock), 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":"0x5ff98717a18833de1a49e11b498866d6fa1c9296","data":"0x6a42b8f8"},"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":"0xd47875d0000000000000000000000000beeff039907422219fb367e525954ddc092854d9"},"latest"]}'The 6th 32-byte word of the answer is the composite score (40 = 0x28); 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.