Can one person move the money in PYUSD (Paxos) on Ethereum? The authority score is 2 / 100 (critical): one key or a tiny group.
In short. The proxy admin and the owner are accounts with no code. Either can replace the token's logic or act as the owner, with no delay.
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 | 5 |
|---|---|
| multisig | 0 |
| timelock | 0 |
| price feed | 100 |
| shared control | 100 |
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: 1 key, 0 h to react.
The proxy admin and the owner are accounts with no code. Either can replace the token's logic or act as the owner, with no delay.
accounts with no code, no timelock, composite 2
Added 2026-10-11. Scored 5 / 0 / 0 (composite 2). Read: the proxy admin, owner(), defaultAdmin() and supplyControl() (the mint authority, a contract whose owner is followed); all four lead to accounts with no code, three of them to the same one. Whether one key, an HSM or an MPC service holds an account with no code cannot be observed on chain; the score treats it as a bare EOA, the methodology's convention.
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 2 is under MIN_SAFE_SCORE 60). Cheapest path to weak (20): admin key from 5 to 49, 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/ethereum-l1-0x6c3ea9036406852006290770bedfcaba0e23a0e8.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: the money behind one key (no money figure, or no key count); the protocol's total value locked (no DefiLlama match).
Contract: 0x6c3ea9036406852006290770bedfcaba0e23a0e8 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(0x6c3ea9036406852006290770bedfcaba0e23a0e8) 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.
Read live: admin: a plain key, 425 transactions sent; delay: none.
Independent read of the admin: a plain key (bare EOA) 0x3af3…024…024b via owner(), consistent with the published admin-key score. Unchanged since 2026-10-11. This key has sent 425 transactions. (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): 2 to 2 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://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x6c3ea9036406852006290770bedfcaba0e23a0e8","data":"0x8da5cb5b"},"latest"]}'
# eth_getCode on the holder: 0x means a plain key
curl -s -X POST https://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getCode","params":["<holder>","latest"]}'
# eth_getTransactionCount on the holder: how many transactions this key has sent (425 at the read)
curl -s -X POST https://ethereum-rpc.publicnode.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionCount","params":["<holder>","latest"]}'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 26199869 and 26199870 of the chain; this RPC cannot replay the block of the read (it ignores the block tag, or no longer serves old state): the answers are the current ones
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
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":"0xd47875d00000000000000000000000006c3ea9036406852006290770bedfcaba0e23a0e8"},"0xb5eb8d"]}'The 6th 32-byte word of the answer is the composite score (2 = 0x2); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.