Can one person move the money in DolomiteMargin (verified source) on Arbitrum? The authority score is 40 / 100 (moderate): a multisig without a real delay, the band where Bybit, WazirX and Radiant sat when they were drained.
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 | 35 |
| timelock | 30 |
| price feed | 20 |
| 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).
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 40 is under MIN_SAFE_SCORE 60). Cheapest path to decent (60): admin key from 50 to 100, 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/arbitrum-0x6bd780e7fdf01d77e4d475c821f1e7ae05409072.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); the protocol's total value locked (no DefiLlama match).
Contract: 0x6bd780e7fdf01d77e4d475c821f1e7ae05409072 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(0x6bd780e7fdf01d77e4d475c821f1e7ae05409072) 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.
Read live: admin: a contract the reader cannot classify; delay: unknown.
Independent read of the admin: a contract 0xc2b66e24…de06 via owner(), 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.
# 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":"0x6bd780e7fdf01d77e4d475c821f1e7ae05409072","data":"0x8da5cb5b"},"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":"0xd47875d00000000000000000000000006bd780e7fdf01d77e4d475c821f1e7ae05409072"},"latest"]}'The 6th 32-byte word of the answer is the composite score (40 = 0x28); 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.