Can one person move the money in Spark USDC Vault (sparkUSDC) on Base? The authority score is 63 / 100 (decent): a multisig and a delay, with gaps.
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 | 60 |
|---|---|
| multisig | 55 |
| timelock | 75 |
| price feed | 52 |
| 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, 240 h to react.
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 52.25% (score 63).
[](https://realspap.github.io/oracle/p/base-0x7bfa7c4f149e7415b73bdedfe609237e29cbf34a.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).
Money behind it: $465M (DefiLlama), of which $172M sits exposed to this setup (TVL × (100 − score) / 100, a weight, not a prediction).
Contract: 0x7bfa7c4f149e7415b73bdedfe609237e29cbf34a 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(0x7bfa7c4f149e7415b73bdedfe609237e29cbf34a) on the Base oracle, listed in the repository.
Read at block 48160953, methodology 0x0ffe08e65a4a36a2…. 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.
Other hands: guardian() is a Safe 2-of-3 (0xf5748bbefa17505b2f7222b23ae11584932c908b); curator() is a Safe 2-of-2 (0x0f963a8a8c01042b69054e787e5763abbb0646a3). A role is named by its getter, what it can do depends on the protocol (in a MetaMorpho vault guardian() can revoke a pending change, it does not move funds). A change is an alert.
Read live: admin: a timelock; delay: 240 h the contract enforces itself.
Independent read of the admin: a timelock, 0s delay 0xf93b7122…f579 via owner(), consistent with the published admin-key score. Unchanged since 2026-10-10. The contract enforces its own timelock of 240 h (timelock()). (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://mainnet.base.org -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x7bfa7c4f149e7415b73bdedfe609237e29cbf34a","data":"0x8da5cb5b"},"0x32362db"]}'
# delay() on the holder (Compound-style timelock), in seconds
curl -s -X POST https://mainnet.base.org -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xf93b7122450a50af3e5a76e1d546e95ac1d0f579","data":"0x6a42b8f8"},"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 52650708 and 52650715 of the chain
Follow this contract: Atom feed of its score moves, alerts and queued operations (nothing else).
curl -s -X POST https://sepolia.base.org -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x50840a7667baEa9D05ad4ae3dCeb384724b58720","data":"0xd47875d00000000000000000000000007bfa7c4f149e7415b73bdedfe609237e29cbf34a"},"0x2dee0b9"]}'The 6th 32-byte word of the answer is the composite score (63 = 0x3f); the 7th is the push timestamp. Same call with "latest" instead of the block gives the current value.