Can one person move the money in Curve Finance StableSwap Factory on Monad? The authority score is 4 / 100 (critical): one key or a tiny group.
In short. The weakest authority shape found on any chain this project tracks: admin is a single bare EOA - not a Safe, not a timelock.
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 | 10 |
|---|---|
| multisig | 0 |
| timelock | 0 |
| price feed | 100 |
| shared control | 80 |
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: 1 key, 0 h to react, about $10M behind one key.
The weakest authority shape found on any chain this project tracks: admin is a single bare EOA - not a Safe, not a timelock.
composite 4 - lowest on Monad
Curve’s own deployment repo says so explicitly: “deployer as admin until DAO ownership transfer.” Confirmed live (the address has zero contract bytecode) and confirmed actively exercised - on-chain history already shows this key calling Set_new_fee and Ramp_A on a live, ~$2.4M-TVL pool.
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 4 is under MIN_SAFE_SCORE 60). Cheapest path to weak (20): admin key from 10 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/monad-0x8271e06e5887fe5ba05234f5315c19f3ec90e8ad.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.
Money behind it: $10M (DefiLlama), of which $10M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0x8271e06e5887fe5ba05234f5315c19f3ec90e8ad 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(0x8271e06e5887fe5ba05234f5315c19f3ec90e8ad) on the Monad oracle, listed in the repository.
Read at block 71327646, methodology 0x4988d9ca0f320921…. 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 plain key, 2 transactions sent; delay: none.
Independent read of the admin: a plain key (bare EOA) 0xabc3…1cb…1cbf via admin(), consistent with the published admin-key score. Unchanged since 2026-10-10. This key has sent 2 transactions. The attacker's question: 1 key moves this contract, no delay to react, $10M behind each key (the protocol's TVL, not this contract's balance). This holder also governs 1 other tracked contract (about $11M behind all of them, DefiLlama): 0x8271e06e… 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.
# admin() on the contract: the holder
curl -s -X POST https://rpc.monad.xyz -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x8271e06e5887fe5ba05234f5315c19f3ec90e8ad","data":"0xf851a440"},"0x6c6c938"]}'
# eth_getCode on the holder: 0x means a plain key
curl -s -X POST https://rpc.monad.xyz -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getCode","params":["<holder>","latest"]}'
# eth_getTransactionCount on the holder: how many transactions this key has sent (2 at the read)
curl -s -X POST https://rpc.monad.xyz -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionCount","params":["<holder>","0x6c6c938"]}'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 113690920 and 113690936 of the chain
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
curl -s -X POST https://testnet-rpc.monad.xyz/ -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x50840a7667baEa9D05ad4ae3dCeb384724b58720","data":"0xd47875d00000000000000000000000008271e06e5887fe5ba05234f5315c19f3ec90e8ad"},"0x4405f9e"]}'The 6th 32-byte word of the answer is the composite score (4 = 0x4); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.