Can one person move the money in Chainlink Price Feed Admin (Robinhood Chain) on Robinhood Chain? The authority score is 52 / 100 (moderate): a multisig without a real delay, the band where Bybit, WazirX and Radiant sat when they were drained.
In short. Not a protocol consuming an oracle - the oracle’s own governance. One Safe is owner() on every Chainlink feed sampled on this chain, including 3 already-tracked stock-token feeds.
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 | 85 |
| timelock | 0 |
| price feed | 52 |
| 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).
Not a protocol consuming an oracle - the oracle’s own governance. One Safe is owner() on every Chainlink feed sampled on this chain, including 3 already-tracked stock-token feeds.
new in batch 8
owner() was called live on 7 independently-sampled Chainlink aggregator proxies - the Robinhood TSLA/AMZN/AMD stock feeds already tracked above, plus LINK/USD, ETH/USD and USDG/USD - and all 7 resolve to the identical address, confirmed a real 4-of-9 Gnosis Safe. Chainlink is the only officially confirmed price-oracle provider on this chain (57 feeds in Chainlink’s own dataset); every protocol here that reads a Chainlink price, tracked by this oracle or not, inherits whatever controls this one Safe. No timelock layer was identified above it this pass - absence of evidence isn’t scored as evidence of one.
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 52 is under MIN_SAFE_SCORE 60). Cheapest path to decent (60): admin key from 65 to 85, 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-0xee27d5ae494300902d90454e8630a3f1c68c9c52.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: 0xee27d5ae494300902d90454e8630a3f1c68c9c52 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(0xee27d5ae494300902d90454e8630a3f1c68c9c52) 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.
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://rpc.testnet.chain.robinhood.com/rpc -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x9BF45734D09bC7CA39238e767B2af9AAc62a7f52","data":"0xd47875d0000000000000000000000000ee27d5ae494300902d90454e8630a3f1c68c9c52"},"latest"]}'The 6th 32-byte word of the answer is the composite score (52 = 0x34); 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.