Can one person move the money in pathUSD on Tempo? The authority score is 9 / 100 (critical): one key or a tiny group.
In short. One bare EOA, delegated to a contract through EIP-7702, is the only DEFAULT_ADMIN of the upgradeable bridge controller that holds ISSUER_ROLE on pathUSD, USDB and DLUSD, so a single key can replace the minting logic of all three.
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 | 15 |
| timelock | 0 |
| price feed | 100 |
| shared control | 60 |
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).
One bare EOA, delegated to a contract through EIP-7702, is the only DEFAULT_ADMIN of the upgradeable bridge controller that holds ISSUER_ROLE on pathUSD, USDB and DLUSD, so a single key can replace the minting logic of all three.
composite 9, the lowest on Tempo: about $132M of combined supply under one key
Traced live on 2026-09-20 on two RPCs: the ISSUER_ROLE holder is the UUPS AccessControlEnumerable controller 0x8354D80E…9058, which has exactly one DEFAULT_ADMIN member, 0x79C6631F…4a4E (code is an EIP-7702 delegation designator, 7 transactions), with no timelock and no Safe in front of it. pathUSD is also the token the chain itself runs on for gas. The 10/15/0 score is therefore not a placeholder: it is what a single uncontested bare key scores. Supply read on 2026-09-20: pathUSD about $50.4M, USDB about $78.1M, DLUSD about $3.5M. USDB (idx 4) and DLUSD (idx 7) share the same controller and key, which is why cross-exposure reads 60.
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 9 is under MIN_SAFE_SCORE 60). Cheapest path to weak (20): admin key from 10 to 38, 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/tempo-0x20c0000000000000000000000000000000000000.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: 0x20c0000000000000000000000000000000000000 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(0x20c0000000000000000000000000000000000000) on the Tempo oracle, listed in the repository.
Read at block 39731343, methodology 0x0a3df5ccf0492a80…. 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-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.
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
curl -s -X POST https://rpc.moderato.tempo.xyz -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x50840a7667baEa9D05ad4ae3dCeb384724b58720","data":"0xd47875d000000000000000000000000020c0000000000000000000000000000000000000"},"0x25e408f"]}'The 6th 32-byte word of the answer is the composite score (9 = 0x9); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.