Can one person move the money in Uniswap v4 PoolManager on Monad? The authority score is 80 / 100 (strong): a multisig behind a long delay.
In short. The best-governed target found on Monad: owned via a Wormhole message relay by Uniswap’s own UNI-token-holder-governed Ethereum Timelock - a real 2-day delay, not a Monad-local 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 | 80 |
|---|---|
| multisig | 100 |
| timelock | 60 |
| 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: keys and hours to react not read for this contract (never shown as zero).
The best-governed target found on Monad: owned via a Wormhole message relay by Uniswap’s own UNI-token-holder-governed Ethereum Timelock - a real 2-day delay, not a Monad-local multisig.
composite 80 - strongest target on this chain
PoolManager.owner() resolves to a Monad-side “Uniswap Wormhole Message Receiver” that only relays messages from a trusted Ethereum-mainnet sender, whose own owner is Etherscan-labeled “Uniswap V2: UNI Timelock” - the same address that owns Ethereum mainnet’s own PoolManager directly. protocolFeeController() currently reads the zero address - no protocol fee is active on this deployment yet.
Exit window: a confirmed delay, bypass paths not all checked, 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 65.00% (score 80). Already in the top band.
[](https://realspap.github.io/oracle/p/monad-0x188d586ddcf52439676ca21a244753fa19f9ea8e.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: $31M (DefiLlama), of which $6M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0x188d586ddcf52439676ca21a244753fa19f9ea8e 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(0x188d586ddcf52439676ca21a244753fa19f9ea8e) 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 contract the reader cannot classify; delay: unknown.
Independent read of the admin: a contract 0xe783de89…ebad 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://rpc.monad.xyz -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x188d586ddcf52439676ca21a244753fa19f9ea8e","data":"0x8da5cb5b"},"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":"0xd47875d0000000000000000000000000188d586ddcf52439676ca21a244753fa19f9ea8e"},"0x4405f9e"]}'The 6th 32-byte word of the answer is the composite score (80 = 0x50); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.