Can one person move the money in Uniswap V2 Factory (Base) on Base? The authority score is 85 / 100 (strong): a multisig behind a long delay.
In short. feeToSetter() is an OP-stack cross-domain forwarder (CrossChainAccount) that only forwards calls relayed by the L2CrossDomainMessenger from Uniswap’s Ethereum-mainnet Governance Timelock, which enforces a 2-day delay (172,800s) and is administered by GovernorBravo. It is the same forwarder that owns the V3 Factory’s fee adapter, with no Safe and no bare EOA in the chain.
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 and hours to react not read for this contract (never shown as zero).
feeToSetter() is an OP-stack cross-domain forwarder (CrossChainAccount) that only forwards calls relayed by the L2CrossDomainMessenger from Uniswap’s Ethereum-mainnet Governance Timelock, which enforces a 2-day delay (172,800s) and is administered by GovernorBravo. It is the same forwarder that owns the V3 Factory’s fee adapter, with no Safe and no bare EOA in the chain.
$89.1M Base TVL, same DAO root as V3 and V4
Scope is narrow: per the deployed Factory and Pair source, feeToSetter can only call setFeeTo or setFeeToSetter (the V2 protocol-fee switch), with no pool upgrade and no access to LP principal. crossExposureScore 100 is not a claim of independence: V2, V3 and V4 on Base share this one forwarder and L1 Timelock, but DAO-rooted targets are left out of the signer-overlap score.
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/base-0x8909dc15e40173ff4699343b6eb8132c65e18ec6.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: who holds the admin power: the independent reader could not classify the holder; 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: $96M (DefiLlama), of which $14M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0x8909dc15e40173ff4699343b6eb8132c65e18ec6 on the explorer ↗. Score pushed on-chain on 2026-10-12; stale on the oracle when older than 9 days (the watch re-reads it anyway). Read the score yourself: getScore(0x8909dc15e40173ff4699343b6eb8132c65e18ec6) on the Base oracle, listed in the repository.
Read at block 48160953, methodology 0x0ffe08e65a4a36a2…. 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.
Independent read of the admin: not possible here (no admin slot, owner(), admin(), DEFAULT_ADMIN_ROLE member or authority() answered). (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-12; 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.
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
curl -s -X POST https://sepolia.base.org -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x50840a7667baEa9D05ad4ae3dCeb384724b58720","data":"0xd47875d00000000000000000000000008909dc15e40173ff4699343b6eb8132c65e18ec6"},"0x2dee0b9"]}'The 6th 32-byte word of the answer is the composite score (85 = 0x55); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.