WETH9 (Wrapped Ether) · authority risk 100/100, strong

Can one person move the money in WETH9 (Wrapped Ether) on Ethereum? The authority score is 100 / 100 (strong): a multisig behind a long delay.

Every check passes.

In short. Nobody can change it: no owner, no admin, no proxy slot, and no DELEGATECALL, CALLCODE or SELFDESTRUCT in the code it can execute. The code is pinned by hash.

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

The five readings

admin key100
multisig100
timelock100
price feed100
shared control100

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).

Why this score

Nobody can change it: no owner, no admin, no proxy slot, and no DELEGATECALL, CALLCODE or SELFDESTRUCT in the code it can execute. The code is pinned by hash.

immutable, composite 100

Added 2026-10-11 so that the most widely held tokens are covered. Scored 100 / 100 / 100: the three dimensions are not applicable to a contract nobody controls. The check is re-run on every scoring pass; a different code at this address, a proxy slot or an owner would degrade the score instead of keeping it.

6 of 6 requirements met

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 80.00% (score 100). Already in the top band.

Show this score in your README
[![authority risk: WETH9 (Wrapped Ether)](https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2FRealSpap%2Fauthority-risk-oracle-showcase%2Fwatch-data%2Fbadge%2Fethereum-l1-sepolia%2F0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2.json)](https://realspap.github.io/oracle/p/ethereum-l1-0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2.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); the protocol's total value locked (no DefiLlama match).

Contract: 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 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(0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2) on the Ethereum oracle, listed in the repository.

Read at block 11922317, methodology 0x46a1a85b619e7db0…. 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 over time (2 points, 2026-10-11 to 2026-10-13, from the chained log): 2026-10-11: 1002026-10-13: 100 100 to 100 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).

Reproduce this read yourself (block 11922317, public RPC, no key)
curl -s -X POST https://ethereum-sepolia-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xB6F8474ccC71AF477c31c2DF663B3942ddfbf906","data":"0xd47875d0000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2"},"0xb5eb8d"]}'

The 6th 32-byte word of the answer is the composite score (100 = 0x64); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.