Can one person move the money in Aave V3 Pool on Plasma? The authority score is 71 / 100 (decent): a multisig and a delay, with gaps.
In short. Same BGD Labs Aave Governance V3 pattern already tracked on Ethereum L1/Arbitrum/Base, real 1-day delay - and a THIRD chain sharing the identical 9-signer, 5-of-9 guardian committee already found on Arbitrum and Base.
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 | 100 |
| timelock | 50 |
| price feed | 52 |
| shared control | 80 |
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).
Same BGD Labs Aave Governance V3 pattern already tracked on Ethereum L1/Arbitrum/Base, real 1-day delay - and a THIRD chain sharing the identical 9-signer, 5-of-9 guardian committee already found on Arbitrum and Base.
cross-exposure: 80 - shared committee, now 3 chains
~$496M TVL, ~87% of all of Plasma’s DeFi TVL - the dominant lender on this chain. The guardian Safe’s owner set was independently re-derived live and matches Arbitrum’s and Base’s own guardian committees exactly, byte for byte - the same 9 people can now cancel the emergency path on three separate chains.
Exit window: a delay with a bypass, or one not ruled out, 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 58.25% (score 71). Cheapest path to strong (80): admin key from 65 to 87, 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/plasma-0x061d8e131f26512348ee5fa42e2df1ba9d6505e9.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 time anyone has to react; the money behind one key (no money figure, or no key count).
Money behind it: $490M (DefiLlama), of which $142M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0x061d8e131f26512348ee5fa42e2df1ba9d6505e9 on the explorer ↗. 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(0x061d8e131f26512348ee5fa42e2df1ba9d6505e9) on the Plasma oracle, listed in the repository.
Read at block 36260964, methodology 0x026c7c3b27bb926e…. 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 contract the reader cannot classify; delay: unknown.
Independent read of the admin: a contract 0x47aadaae…4d6a via owner() -> owner() of the holder (contract), consistent with the published admin-key score. Unchanged since 2026-10-10. Behind the holder, its owner() is another contract 0xe76eb348e65ef163d85ce282125ff5a7f5712a1d: that is the hand. (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-12; 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.
# owner() on the contract: the holder
curl -s -X POST https://rpc.plasma.to -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x061d8e131f26512348ee5fa42e2df1ba9d6505e9","data":"0x8da5cb5b"},"0x21856af"]}'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 35149475 and 35149487 of the chain
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
curl -s -X POST https://testnet-rpc.plasma.to -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x50840a7667baEa9D05ad4ae3dCeb384724b58720","data":"0xd47875d0000000000000000000000000061d8e131f26512348ee5fa42e2df1ba9d6505e9"},"0x2294c64"]}'The 6th 32-byte word of the answer is the composite score (71 = 0x47); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.