Can one person move the money in Fables PoolRegistry on Robinhood Chain? The authority score is 2 / 100 (critical): one key or a tiny group.
In short. A hook-native ve(3,3) DEX on Uniswap v4. A full RoleGranted/RoleRevoked replay from genesis finds exactly one ADMIN_ROLE holder, ever - an EIP-7702-delegated EOA with 470 real transactions, not a multisig.
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 | 5 |
|---|---|
| multisig | 0 |
| 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: keys and hours to react not read for this contract (never shown as zero).
A hook-native ve(3,3) DEX on Uniswap v4. A full RoleGranted/RoleRevoked replay from genesis finds exactly one ADMIN_ROLE holder, ever - an EIP-7702-delegated EOA with 470 real transactions, not a multisig.
~$21.8M TVL
EIP-7702 delegation gives the address code (a smart-account implementation), but does not itself imply multi-party signing - no owners/threshold interface resolves at this address. Scored as a real, active bare-EOA equivalent: sole control, no delay on register/deregister/setAuthority.
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 2 is under MIN_SAFE_SCORE 60). Cheapest path to weak (20): admin key from 5 to 49, 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-0x159a113e012593d9b3cc63ad45e30f0467e13ef3.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: $36M (DefiLlama), of which $35M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0x159a113e012593d9b3cc63ad45e30f0467e13ef3 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(0x159a113e012593d9b3cc63ad45e30f0467e13ef3) 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 contract the reader cannot classify; delay: unknown.
Independent read of the admin: a contract 0xa362d98b…4f30 via authority() (AccessManaged: the AccessManager holds every role), 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.
# authority() on the contract (AccessManaged): the AccessManager that holds every role
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":"0x159a113e012593d9b3cc63ad45e30f0467e13ef3","data":"0xbf7e214f"},"0x55508a0"]}'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":"0xd47875d0000000000000000000000000159a113e012593d9b3cc63ad45e30f0467e13ef3"},"latest"]}'The 6th 32-byte word of the answer is the composite score (2 = 0x2); 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.