Can one person move the money in stHYPE liquid staking (HyperEVM) on Hyperliquid? The authority score is 47 / 100 (moderate): a multisig without a real delay, the band where Bybit, WazirX and Radiant sat when they were drained.
In short. defaultAdmin() and the REBASER_ROLE holder, an intermediary Overseer V1 controller whose owner() was checked live, both resolve to the same 4-of-6 Gnosis Safe. No delay stands in front of it.
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 | 65 |
|---|---|
| multisig | 70 |
| 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: keys not read, 48 h to react.
defaultAdmin() and the REBASER_ROLE holder, an intermediary Overseer V1 controller whose owner() was checked live, both resolve to the same 4-of-6 Gnosis Safe. No delay stands in front of it.
4-of-6 Safe, no delay, composite 47
Pushed on-chain 2026-10-10. Scored 65 / 70 / 0 with an oracle-authority score of 100 and crossExposure 100. The audited token is stHYPE (0xffaa4a3d…6cc1), not wstHYPE, the ERC-4626 wrapper around it. The root Safe was checked for signer overlap with the root Safes of Kinetiq, HyperLend and para, and none was found.
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 47 is under MIN_SAFE_SCORE 60). Cheapest path to decent (60): admin key from 65 to 97, 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 A confirmed delay before changes apply, no bypass (changes can apply with no waiting time).
[](https://realspap.github.io/oracle/p/hyperliquid-0xffaa4a3d97fe9107cef8a3f48c069f577ff76cc1.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); the protocol's total value locked (no DefiLlama match).
Contract: 0xffaa4a3d97fe9107cef8a3f48c069f577ff76cc1. 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(0xffaa4a3d97fe9107cef8a3f48c069f577ff76cc1) on the Hyperliquid oracle, listed in the repository.
Read at block 66993098, methodology 0x36452ea42a84016f…. 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; delay: 48 h on the timelock.
Independent read of the admin: a timelock, 172800s delay 0xc5ded4f7…23d2 via EIP-1967 admin -> ProxyAdmin owner(), disagrees with the published score: the timelock score says no delay (0), the live read finds a timelock of 48 h in the admin path via EIP-1967 admin -> ProxyAdmin owner(). Unchanged since 2026-10-14. Implementation behind the proxy: 0xe71caf5c1fe56d8897c7b604295d23968049e057 (EIP-1967 implementation slot). Its source is verified on Sourcify (stHYPE, exact match, 0.8.28+commit.7893614a). (scripts/second_opinion.py: a reader that shares nothing with the scorer, re-run every 6 hours)
Score over time (2 points, 2026-10-10 to 2026-10-12, from the chained log): 47 to 47 Methodology changed on 2026-10-12: points before that date come from another method and are not comparable.
# the admin slot of the proxy (EIP-1967): the word is the admin address
curl -s -X POST https://rpc.hyperliquid.xyz/evm -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getStorageAt","params":["0xffaa4a3d97fe9107cef8a3f48c069f577ff76cc1","0xb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d6103","latest"]}'
# owner() on the address the slot returned (a ProxyAdmin): the holder
curl -s -X POST https://rpc.hyperliquid.xyz/evm -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"<address from the slot>","data":"0x8da5cb5b"},"latest"]}'
# getMinDelay() on the holder (OpenZeppelin TimelockController), in seconds
curl -s -X POST https://rpc.hyperliquid.xyz/evm -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xc5ded4f7f53919c714059a17d31371ae847e23d2","data":"0xf27a0c92"},"latest"]}'
# the implementation slot of the proxy (EIP-1967): the code behind it, an upgrade changes this word
curl -s -X POST https://rpc.hyperliquid.xyz/evm -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getStorageAt","params":["0xffaa4a3d97fe9107cef8a3f48c069f577ff76cc1","0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc","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.
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
curl -s -X POST https://998.rpc.thirdweb.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x50840a7667baEa9D05ad4ae3dCeb384724b58720","data":"0xd47875d0000000000000000000000000ffaa4a3d97fe9107cef8a3f48c069f577ff76cc1"},"latest"]}'The 6th 32-byte word of the answer is the composite score (47 = 0x2f); 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.