Can one person move the money in T3tris Finance WBTC vault on Robinhood Chain? The authority score is 2 / 100 (critical): one key or a tiny group.
In short. One bare EOA is the sole DEFAULT_ADMIN_ROLE holder on this WBTC vault and also holds 46 of its 47 narrower roles, with no Safe and no timelock among any role holder.
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, about $593k behind one key.
One bare EOA is the sole DEFAULT_ADMIN_ROLE holder on this WBTC vault and also holds 46 of its 47 narrower roles, with no Safe and no timelock among any role holder.
~$610k gross TVL (7.49 WBTC)
DEFAULT_ADMIN_ROLE was granted once, at deployment, and never revoked (a log replay on one RPC, hasRole confirmed on two). The 47th narrower role belongs to a second bare EOA and is administered by itself, so the DEFAULT_ADMIN key cannot revoke it. T3tris publishes no vault source, so what any role can do is not read from source.
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/robinhood-0xd5c6c79692715145098a65d1eb1f2a10c524f8e8.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.
Money behind it: $804k (DefiLlama), of which $788k sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0xd5c6c79692715145098a65d1eb1f2a10c524f8e8 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(0xd5c6c79692715145098a65d1eb1f2a10c524f8e8) on the Robinhood Chain oracle, listed in the repository.
Read at block 136039274, methodology 0x667dc486af9557a8…. 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, 81 transactions sent; delay: none.
Independent read of the admin: a plain key (bare EOA) 0x65d0…e57…e57f via DEFAULT_ADMIN_ROLE member 1 of 1 (AccessControl), consistent with the published admin-key score. Unchanged since 2026-10-10. This key has sent 81 transactions. The attacker's question: 1 key moves this contract, no delay to react, $593k behind each key ($593k of WBTC held by this contract, totalAssets() read live). Implementation behind the proxy: 0x0000000000ac46824e664881581f0e105bb5e492 (EIP-1967 implementation slot). No verified source on Sourcify for the code behind this proxy (this watch asks Sourcify only; an explorer of the chain may hold one). (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.
# getRoleMember(DEFAULT_ADMIN_ROLE, 0) on the contract (AccessControl, enumerable): the holder
curl -s -X POST https://rpc.mainnet.chain.robinhood.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xd5c6c79692715145098a65d1eb1f2a10c524f8e8","data":"0x9010d07c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"},"0x55508a0"]}'
# eth_getCode on the holder: 0x means a plain key
curl -s -X POST https://rpc.mainnet.chain.robinhood.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getCode","params":["<holder>","latest"]}'
# the implementation slot of the proxy (EIP-1967): the code behind it, an upgrade changes this word
curl -s -X POST https://rpc.mainnet.chain.robinhood.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getStorageAt","params":["0xd5c6c79692715145098a65d1eb1f2a10c524f8e8","0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc","latest"]}'
# eth_getTransactionCount on the holder: how many transactions this key has sent (81 at the read)
curl -s -X POST https://rpc.mainnet.chain.robinhood.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionCount","params":["<holder>","0x55508a0"]}'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 89458462 and 89458848 of the chain
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
curl -s -X POST https://rpc.testnet.chain.robinhood.com/rpc -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x9BF45734D09bC7CA39238e767B2af9AAc62a7f52","data":"0xd47875d0000000000000000000000000d5c6c79692715145098a65d1eb1f2a10c524f8e8"},"latest"]}'The 6th 32-byte word of the answer is the composite score (2 = 0x2); 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.