DeFi Saver: control-plane safety record
1 indexed control-plane surface for DeFi Saver, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xBc84…6F00
What differs
Changed / discrepant
- AdminVault Owner multisig: docs state 3/5, the Safe is 3-of-6: DFSRegistry 0x287778F121F134C66212FB16c9b53eC991D32f5b adminVault() = AdminVault 0xCCf3d848e08b94478Ed8f46fFead3008faF581fD; observed vs 'Automation contracts are upgradeable, with any upgrades being locked behind a 24h timelock which can be activated by a 2/3 multisig (Admin) with actual upgrades initiable by a different 3/5 multisig … documented
Show the full onchain evidence
DFSRegistry 0x287778F121F134C66212FB16c9b53eC991D32f5b adminVault() = AdminVault 0xCCf3d848e08b94478Ed8f46fFead3008faF581fD; AdminVault.owner() = Safe 0xBc841B0dE0b93205e912CFBBd1D0c160A1ec6F00 (Ethereum) with getThreshold() = 3 of getOwners() = 6 owners (Safe v1.3.0).
Show the full documented text
'Automation contracts are upgradeable, with any upgrades being locked behind a 24h timelock which can be activated by a 2/3 multisig (Admin) with actual upgrades initiable by a different 3/5 multisig (Owner).' (docs.defisaver.com/protocol/security-and-audits/admin-access-control)
Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Not determined · Upgrade path not in the published records
- Timelock floor
- Not determined · No enforced admin delay in the published records
- Signer quorum
- Strong · Lowest controlling quorum: 3-of-6Evidence: controller fact: Safe getThreshold()
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Weak · Documentation differs from the chain (parameter delta)
Each slice is derived only from the pinned records on this page and their controller facts (/api/v1/scorecards.json). A hollow slice is not determined by the published evidence (never a guess); docs-vs-chain parity is uncompared for RPC-observed protocols. How to read it.
Check it live (free)
The pre-flight API re-reads the controller, proxy and capabilities of one contract at the latest block. No key, no wallet. The score rates that single contract, not the whole protocol.
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0xBc841B0dE0b93205e912CFBBd1D0c160A1ec6F00"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0xBc841B0dE0b93205e912CFBBd1D0c160A1ec6F00"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0xBc841B0dE0b93205e912CFBBd1D0c160A1ec6F00"})Provenance · research credit
Reported by @VB-Blue through the Pacta Wave 2 pool (PR #71, fixture bounties/wave-2/ethereum-defi-saver.json), merged under the Apache-2.0 commercial grant and paid $1.00 USDC (tx 0xb605…432d); credited on defi-saver-adminvault-owner-safe-s28. Pacta then re-read every value below on two independent RPCs at its own Sprint pin and compared it with the documentation; the classifications and the Base EAS attestation are Pacta's. See the leaderboard.
AdminVault Owner multisig: docs state 3/5, the Safe is 3-of-6
Observed onchain. DFSRegistry 0x287778F121F134C66212FB16c9b53eC991D32f5b adminVault() = AdminVault 0xCCf3d848e08b94478Ed8f46fFead3008faF581fD; AdminVault.owner() = Safe 0xBc841B0dE0b93205e912CFBBd1D0c160A1ec6F00 (Ethereum) with getThreshold() = 3 of getOwners() = 6 owners (Safe v1.3.0).
Documented. 'Automation contracts are upgradeable, with any upgrades being locked behind a 24h timelock which can be activated by a 2/3 multisig (Admin) with actual upgrades initiable by a different 3/5 multisig (Owner).' (docs.defisaver.com/protocol/security-and-audits/admin-access-control)
cast call 0xBc841B0dE0b93205e912CFBBd1D0c160A1ec6F00 \ "getThreshold()" \ --block 26441165 --rpc-url "$ETH_RPC_URL" cast block 26441165 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x5182be2c61af5f48ed2ec43d3c177dedad257c4e966a7e384120829de73901d9
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of DeFi Saver differs from what the protocol documents. It turns to the neutral Aligned · Base EAS shield only when the on-chain state or the documentation changes and the two match at a new finalized block, whoever requests the re-check.
Embed this badge (it updates when the status changes):
[](https://pacta.wtf/protocols/defi-saver/)
<a href="https://pacta.wtf/protocols/defi-saver/"><img src="https://pacta.wtf/badges/defi-saver.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/defi-saver.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/defi-saver.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check DeFi Saver on mainnet within 24h and attest the result on Base. The fee pays for the 24-hour mainnet re-verification work, never the grade: your attestation reads Aligned when on-chain controls match the published documentation, and Delta when they do not.
Maintaining DeFi Saver? Verify and reconcile the record
Two paths, both public. A free doc-update notice asks the maintainers to correct the documentation or the onchain parameter; anyone can send it. A Full Control-Plane Dossier ($2,500–$5,000 USDC, 24h SLA) re-reads the multisig and timelock control planes on archive RPCs and prepares an upstream docs reconciliation PR. Either way the classification changes only when the onchain state or the documentation aligns at a new finalized block.
Need procurement paperwork? Request a commercial invoice (PDF).