Can one person move the money in OAdapter (verified source) on Arbitrum? The authority score is 8 / 100 (critical): one key or a tiny group.
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 | 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: 3 keys, 0 h to react.
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 8 is under MIN_SAFE_SCORE 60). Cheapest path to weak (20): admin key from 20 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/arbitrum-0xffa10065ce1d1c42fabc46e06b84ed8ffeb4bae5.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: 0xffa10065ce1d1c42fabc46e06b84ed8ffeb4bae5 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(0xffa10065ce1d1c42fabc46e06b84ed8ffeb4bae5) on the Arbitrum oracle, listed in the repository.
Read at block 319507783, methodology 0x51163f3cce461201…. 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 0x5f0b…841f has executed 102 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 3-of-3 of 3 plain keys (+1 module); delay: 168 h Zodiac delay (for module-routed calls).
Independent read of the admin: a Safe 3-of-3 0x5f0bc72f…841f via owner(), disagrees with the published score: the multisig score says no real multisig (0), the live read finds a Safe 3-of-3 via owner(). Unchanged since 2026-10-10. 3 keys collude to act; 1 key lost and nobody can act (one lost key freezes this Safe). Signers: 3 plain keys. Safe module enabled: 0x02878d80732759531bcf8b9ce8197eaec58ef1ce (a Zodiac Delay module, cooldown 604800 s (adds a delay), owned by the Safe itself). A module executes through this Safe without the 3-of-3 signatures. (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://arb1.arbitrum.io/rpc -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xffa10065ce1d1c42fabc46e06b84ed8ffeb4bae5","data":"0x8da5cb5b"},"latest"]}'
# getThreshold() on the holder (a Safe)
curl -s -X POST https://arb1.arbitrum.io/rpc -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x5f0bc72fb5952b2f3f2e11404398ed507b25841f","data":"0xe75235b8"},"latest"]}'
# getOwners() on the holder: the signer set (word 2 is the count)
curl -s -X POST https://arb1.arbitrum.io/rpc -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x5f0bc72fb5952b2f3f2e11404398ed507b25841f","data":"0xa0e67e2b"},"latest"]}'
# getModulesPaginated(0x1, 50) on the holder: the modules (a module executes without the signatures)
curl -s -X POST https://arb1.arbitrum.io/rpc -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x5f0bc72fb5952b2f3f2e11404398ed507b25841f","data":"0xcc2f845200000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000032"},"latest"]}'
# the guard slot of the holder (keccak of guard_manager.guard.address)
curl -s -X POST https://arb1.arbitrum.io/rpc -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getStorageAt","params":["0x5f0bc72fb5952b2f3f2e11404398ed507b25841f","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 515148086 and 515148107 of the chain; this RPC cannot replay the block of the read (it ignores the block tag, or no longer serves old state): the answers are the current ones
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
curl -s -X POST https://sepolia-rollup.arbitrum.io/rpc -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x50840a7667baEa9D05ad4ae3dCeb384724b58720","data":"0xd47875d0000000000000000000000000ffa10065ce1d1c42fabc46e06b84ed8ffeb4bae5"},"latest"]}'The 6th 32-byte word of the answer is the composite score (8 = 0x8); 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.