Can one person move the money in Longbow on Robinhood Chain? The authority score is 33 / 100 (weak): a small group with little delay.
In short. Owner and curator are two separately-deployed Safes with the identical 3 signers and 2-of-3 threshold - no real separation of duties.
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 | 40 |
|---|---|
| multisig | 40 |
| timelock | 15 |
| 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: 2 keys, 0 h to react, about $46k behind one key.
Owner and curator are two separately-deployed Safes with the identical 3 signers and 2-of-3 threshold - no real separation of duties.
$3.83M chain TVL, invisible to Morpho’s own vaultV2s API since Longbow creates 55 isolated markets directly on the shared Morpho Blue singleton - resolved via Longbow’s own production API instead, every address independently re-verified on-chain. setOwner/setCurator/setIsSentinel timelocks confirmed at 0 on all three vaults, the same chain-wide gap as every other Morpho vault; addAdapter (3 days) and removeAdapter (7 days) carry a real delay that doesn’t cover what matters.
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 33 is under MIN_SAFE_SCORE 60). Cheapest path to moderate (40): admin key from 40 to 58, 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-0x026df18fbd2a7639089d0a16293383ec687a5ca1.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: shared control: the score says no key is shared, but this contract's own independent read lists another tracked contract with the same admin (unresolved, 12/10: do not read "no key shared" as established).
Money behind it: $3M (DefiLlama), of which $2M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0x026df18fbd2a7639089d0a16293383ec687a5ca1 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(0x026df18fbd2a7639089d0a16293383ec687a5ca1) 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-3 (0xe600…a4bb). 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.
Admin Safe activity: the Safe 0x396a…3ed4 has executed 2 transactions (this watch has read that number since 2026-10-10; it has not seen it move). A Safe idle for 14 days or more that executes again, with money behind it, is an alert.
Read live: admin: Safe 2-of-3 of 3 plain keys; delay: none.
Independent read of the admin: a Safe 2-of-3 0x396a…3ed…3ed4 via owner(), consistent with the published admin-key score. Unchanged since 2026-10-10. The attacker's question: 2 keys move this contract, no delay to react, $46k behind each key ($92k of USDG held by this contract, totalAssets() read live). 2 keys collude to act; 2 keys lost and nobody can act. Signers: 3 plain keys. This holder also governs 2 other tracked contracts (about $3M behind all of them, DefiLlama): 0x65dc90cd… on Robinhood Chain, 0xe129d4cb… on Robinhood Chain. (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":"0x026df18fbd2a7639089d0a16293383ec687a5ca1","data":"0x8da5cb5b"},"0x55508a0"]}'
# getThreshold() on the holder (a Safe)
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":"<holder>","data":"0xe75235b8"},"latest"]}'
# getOwners() on the holder: the signer set (word 2 is the count)
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":"<holder>","data":"0xa0e67e2b"},"latest"]}'
# getModulesPaginated(0x1, 50) on the holder: the modules (a module executes without the signatures)
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":"<holder>","data":"0xcc2f845200000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000032"},"latest"]}'
# the guard slot of the holder (keccak of guard_manager.guard.address)
curl -s -X POST https://rpc.mainnet.chain.robinhood.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getStorageAt","params":["<holder>","0x4a204f620c8c5ccdca3fd54d003badd85ba500436a431f0cbda4f558c93c34c8","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":"0xd47875d0000000000000000000000000026df18fbd2a7639089d0a16293383ec687a5ca1"},"latest"]}'The 6th 32-byte word of the answer is the composite score (33 = 0x21); 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.