Lagoon: control-plane safety record
1 indexed control-plane surface for Lagoon, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x707D…6A27
What differs
Changed / discrepant
- Timelock delay: 0 s (no delay) observed vs 1 d documented
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
- Weak · 0s minimum enforced delay across control surfacesEvidence: lagoon-vault-beacon-upgrade-delay-s29: observed_delay_seconds = 0
- Signer quorum
- Not determined · No signer quorum in the published records
- 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=0x707D622cdA4b5459e7DcEe8Ba8E429F154f96A27"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x707D622cdA4b5459e7DcEe8Ba8E429F154f96A27"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x707D622cdA4b5459e7DcEe8Ba8E429F154f96A27"})Provenance · research credit
Reported by @VB-Blue through the Pacta Wave 2 pool (PR #82, fixture bounties/wave-2/ethereum-lagoon.json), merged under the Apache-2.0 commercial grant and paid $1.00 USDC (tx 0xae39…0016); credited on lagoon-vault-beacon-upgrade-delay-s29. 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.
cbBTC vault upgrades: docs require a 24 h to 30 day wait; the vault's beacon owner is a 3-of-6 Safe with no delay
Observed onchain. Lagoon cbBTC vault 0xB09F761Cb13baCa8eC087Ac476647361b6314F98 (Ethereum) is an EIP-1967 BeaconProxy: beacon slot = UpgradeableBeacon 0x707D622cdA4b5459e7DcEe8Ba8E429F154f96A27 (implementation() = 0x6C77c47FB8168E22976C3B0338CB1769c952249f), admin slot empty. The beacon's owner() = Safe 0x6D46e28aB34622d9A39d0F306a37a8dC270951aF with getThreshold() = 3 of getOwners() = 6 owners (Safe v1.3.0), no Safe guard; the beacon exposes no delay(). An upgrade of the beacon applies to the vault at once.
Documented. 'Every upgrade is subject to a mandatory waiting period before it takes effect. This gives investors time to evaluate the incoming change and exit the vault if needed.' and 'The delay window is configurable by the vault admin , within the protocol bounds of 24 hours (minimum) to 30 days (maximum).' (docs.lagoon.finance/vault/upgradability-and-opt-in-proxy)
cast call 0x707D622cdA4b5459e7DcEe8Ba8E429F154f96A27 \ "owner()" \ --block 26448221 --rpc-url "$ETH_RPC_URL" cast block 26448221 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa7818c0e1b8807aac0c999c2dc9aeeea40b91b4f19b1b76a62ad02d8d17607c8
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Lagoon 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/lagoon/)
<a href="https://pacta.wtf/protocols/lagoon/"><img src="https://pacta.wtf/badges/lagoon.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/lagoon.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/lagoon.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check Lagoon 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 Lagoon? 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).