Can one person move the money in up v3 Factory on Robinhood Chain? The authority score is 32 / 100 (weak): a small group with little delay.
In short. A real 2-of-4 Gnosis Safe (v1.4.1, no module, guard slot zero, four bare-EOA owners) owns the factory and also holds swapFeeManager and unstakedFeeManager, with no timelock in the path. Simulated calls confirm it can call setOwner, enableTickSpacing and the fee-manager and fee-module setters, and its crossExposureScore is 100, meaning no signer shared with another tracked target.
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 | 50 |
|---|---|
| multisig | 40 |
| 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: 2 keys, 0 h to react.
A real 2-of-4 Gnosis Safe (v1.4.1, no module, guard slot zero, four bare-EOA owners) owns the factory and also holds swapFeeManager and unstakedFeeManager, with no timelock in the path. Simulated calls confirm it can call setOwner, enableTickSpacing and the fee-manager and fee-module setters, and its crossExposureScore is 100, meaning no signer shared with another tracked target.
~$8.4M TVL (DefiLlama)
The same Safe is also the governor, emergency council and epoch governor of the Voter the factory points to, the team address of that Voter’s VotingEscrow and Minter, and the owner of its FactoryRegistry, so its reach extends beyond this one contract and the score covers only the factory’s owner chain. The contracts behind swapFeeModule and unstakedFeeModule were not traced, so any authority they carry of their own is not in the score.
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 32 is under MIN_SAFE_SCORE 60). Cheapest path to moderate (40): admin key from 50 to 69, 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/robinhood-0x1ac9db4a2608ba45d6127b1737949b51bb54b7f3.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: the money behind one key (no money figure, or no key count); the protocol's total value locked (no DefiLlama match).
Contract: 0x1ac9db4a2608ba45d6127b1737949b51bb54b7f3 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(0x1ac9db4a2608ba45d6127b1737949b51bb54b7f3) 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.
Admin Safe activity: the Safe 0x0eea…dfd8 has executed 435 transactions (last seen moving on 2026-10-15). A Safe idle for 14 days or more that executes again, with money behind it, is an alert.
Read live: admin: Safe 2-of-4 of 4 plain keys; delay: none.
Independent read of the admin: a Safe 2-of-4 0x0eea…dfd…dfd8 via owner(), consistent with the published admin-key score. Unchanged since 2026-10-10. 2 keys collude to act; 3 keys lost and nobody can act. Signers: 4 plain keys. (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":"0x1ac9db4a2608ba45d6127b1737949b51bb54b7f3","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":"0xd47875d00000000000000000000000001ac9db4a2608ba45d6127b1737949b51bb54b7f3"},"latest"]}'The 6th 32-byte word of the answer is the composite score (32 = 0x20); 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.