Vesper V1: control-plane safety record
1 indexed control-plane surface for Vesper V1, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x9520…807A
What differs
Changed / discrepant
- Pool governor multisig: docs state 3 of 5 signers, the Safe is 3-of-6: Vesper governor Safe 0x9520b477Aa81180E6DdC006Fc09Fb6d3eb4e807A (Ethereum): getThreshold() = 3 of getOwners() = 6 owners (Safe v1.3.0); observed vs 'Multisig is a contract where n people vote on transaction before it gets executed. documented
Show the full onchain evidence
Vesper governor Safe 0x9520b477Aa81180E6DdC006Fc09Fb6d3eb4e807A (Ethereum): getThreshold() = 3 of getOwners() = 6 owners (Safe v1.3.0); governor() of the Vesper pools 0xd1C117319B3595fbc39b471AB1fd485629eb05F2, 0x3aEd4dd0b5ba616156Fa352274670c18D2Ec2A81, 0x025a05f1967521806BB4c8a10Ba4b8c00A794F65 is this Safe, which is also the published controller of the VSP token record.
Show the full documented text
'Multisig is a contract where n people vote on transaction before it gets executed. The Vesper multisig has 5 signers and requires 3 yes votes for a transaction to execute.' (docs.vesper.finance/vesper-pools-and-strategies/vespers-modular-pool-architecture)
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=0x9520b477Aa81180E6DdC006Fc09Fb6d3eb4e807A"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x9520b477Aa81180E6DdC006Fc09Fb6d3eb4e807A"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x9520b477Aa81180E6DdC006Fc09Fb6d3eb4e807A"})Provenance · research credit
Reported by @VB-Blue through the Pacta Wave 2 pool (PR #70, fixture bounties/wave-2/ethereum-vesper.json), merged under the Apache-2.0 commercial grant and paid $1.00 USDC (tx 0xedf2…90ac); credited on vesper-v1-governor-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.
Pool governor multisig: docs state 3 of 5 signers, the Safe is 3-of-6
Observed onchain. Vesper governor Safe 0x9520b477Aa81180E6DdC006Fc09Fb6d3eb4e807A (Ethereum): getThreshold() = 3 of getOwners() = 6 owners (Safe v1.3.0); governor() of the Vesper pools 0xd1C117319B3595fbc39b471AB1fd485629eb05F2, 0x3aEd4dd0b5ba616156Fa352274670c18D2Ec2A81, 0x025a05f1967521806BB4c8a10Ba4b8c00A794F65 is this Safe, which is also the published controller of the VSP token record.
Documented. 'Multisig is a contract where n people vote on transaction before it gets executed. The Vesper multisig has 5 signers and requires 3 yes votes for a transaction to execute.' (docs.vesper.finance/vesper-pools-and-strategies/vespers-modular-pool-architecture)
cast call 0x9520b477Aa81180E6DdC006Fc09Fb6d3eb4e807A \ "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 Vesper V1 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/vesper-v1/)
<a href="https://pacta.wtf/protocols/vesper-v1/"><img src="https://pacta.wtf/badges/vesper-v1.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/vesper-v1.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/vesper-v1.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check Vesper V1 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 Vesper V1? 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).