Can one person move the money in Ekubo Core on Robinhood Chain? The authority score is 100 / 100 (strong): a multisig behind a long delay.
Every check passes.
In short. Verified ownerless by design - source code, official docs, and an on-chain differential revert test all agree: no privileged account exists at all.
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 | 100 |
|---|---|
| multisig | 100 |
| timelock | 100 |
| 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 and hours to react not read for this contract (never shown as zero).
Verified ownerless by design - source code, official docs, and an on-chain differential revert test all agree: no privileged account exists at all.
only perfect score
~$1.92M TVL. Ekubo’s own source (Core.sol / ICore.sol) has zero authority concepts anywhere in its 18-function interface. Ekubo’s own docs state explicitly it’s ownerless on EVM by design, contrasted against Ekubo’s Starknet Core, which is owner-upgradeable. An on-chain differential test confirms it: owner() and a deliberately fake selector both revert with identical empty data, while a real function on the same contract reverts with real, decoded error data - proving the "authority" selectors genuinely don’t exist rather than existing and reverting for some other reason.
Exit window: a confirmed delay, bypass paths checked, 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 80.00% (score 100). Already in the top band.
[](https://realspap.github.io/oracle/p/robinhood-0x00000000000014aa86c5d3c41765bb24e11bd701.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).
Money behind it: $1M (DefiLlama), of which $0k sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0x00000000000014aa86c5d3c41765bb24e11bd701 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(0x00000000000014aa86c5d3c41765bb24e11bd701) 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.
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.testnet.chain.robinhood.com/rpc -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x9BF45734D09bC7CA39238e767B2af9AAc62a7f52","data":"0xd47875d000000000000000000000000000000000000014aa86c5d3c41765bb24e11bd701"},"latest"]}'The 6th 32-byte word of the answer is the composite score (100 = 0x64); 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.