Can one person move the money in Uniswap v2 + v3 + v4 + UniswapX on Robinhood Chain? The authority score is 85 / 100 (strong): a multisig behind a long delay.
In short. RESOLVED 2026-09-17: the address controlling v3 Factory, v4 PoolManager, the UniswapX reactor, and v2’s feeToSetter is the real Uniswap L1 Governance Timelock’s Arbitrum bridge alias, not a vanity-ground key. Re-scored to 85/100, independently re-confirming the L1 Timelock and GovernorBravo live on every run.
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 | 75 |
| 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 not read, 48 h to react.
RESOLVED 2026-09-17: the address controlling v3 Factory, v4 PoolManager, the UniswapX reactor, and v2’s feeToSetter is the real Uniswap L1 Governance Timelock’s Arbitrum bridge alias, not a vanity-ground key. Re-scored to 85/100, independently re-confirming the L1 Timelock and GovernorBravo live on every run.
1 identity, 4 surfaces - external L1 DAO via bridge alias
0x2BAD8182C09F50c8318d769245beA52C32Be46CD is the LEGITIMATE Arbitrum L1→L2 alias of Uniswap’s real Ethereum-mainnet Governance Timelock (0x1a9C8182C09F50c8318d769245bEA52c32BE35BC) - re-derived by exact arithmetic (alias = L1 address + 0x1111000000000000000000000000000000001111, mod 2^160, deterministic) and re-confirmed live: the L1 address has real deployed bytecode, the L2 alias has none, which is expected for a bridge alias (a sender identity materialized by the canonical bridge, never itself a deployed contract) - not evidence of vanity-mining or a leaked key. This was previously published here as “vanity-ground to impersonate governance”, which was wrong. It does not mean zero risk: the true authority is Uniswap’s real L1 Governor Bravo + Timelock (DAO vote + a real ~2-day delay), reached via the bridge with no Robinhood-Chain-native control of its own - a different risk shape than a single unprotected key. As of 2026-09-17 this is reflected in the score: 85/100, using the same external-L1-DAO-via-bridge-alias convention already applied to this project’s Base sibling scorer, re-verifying the L1 Timelock’s real 172,800s delay and GovernorBravo’s real 40M-UNI quorum live on every run rather than trusting the correction alone. Added 2026-09-20: this same Timelock is the root of 11 tracked Uniswap targets on 5 ecosystems (Ethereum L1, Arbitrum, Base, Robinhood Chain, Monad), so their cross-exposure reads 80, not 100 (see data/finding_2026-09-20-uniswap-one-timelock-eleven-targets.md).
Exit window: a confirmed delay, bypass paths 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 68.75% (score 85). Already in the top band.
[](https://realspap.github.io/oracle/p/robinhood-0x1f7d7550b1b028f7571e69a784071f0205fd2efa.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 money behind one key (no money figure, or no key count).
Money behind it: $51M (DefiLlama), of which $8M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0x1f7d7550b1b028f7571e69a784071f0205fd2efa 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(0x1f7d7550b1b028f7571e69a784071f0205fd2efa) 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 timelock behind a bare contract; delay: 48 h on the timelock.
Independent read of the admin: a contract 0x05c420bc…aa25 via owner() -> owner() of the holder (timelock 172800s), consistent with the published admin-key score. Unchanged since 2026-10-10. Behind the holder, its owner() is a timelock of 48 h: that is the hand. (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.mainnet.chain.robinhood.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x1f7d7550b1b028f7571e69a784071f0205fd2efa","data":"0x8da5cb5b"},"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":"0xd47875d00000000000000000000000001f7d7550b1b028f7571e69a784071f0205fd2efa"},"latest"]}'The 6th 32-byte word of the answer is the composite score (85 = 0x55); 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.