Mellow Protocol / Lido Earn: control-plane safety record
1 indexed control-plane surface for Mellow Protocol / Lido Earn, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xe5abcc40196174Ae0d12153dE286F0D8E401769d.
What differs
Changed / discrepant
- Curator Safe Quorum & Lazy Admin Signer Overlap: getThreshold() = 3, getOwners().length = 5 (3-of-5 Gnosis Safe); observed vs lidofinance/docs (earn/deployment-contracts.md line 199) lists 3/6 multisig; documented
Show the full onchain evidence
getThreshold() = 3, getOwners().length = 5 (3-of-5 Gnosis Safe); DEFAULT_ADMIN_ROLE (0x00) on earnETH (0x6a37725ca7f4CE81c004c955f7280d5C704a249e) and earnUSD (0x014e6DA8F283C4aF65B2AA0f201438680A004452) held by 5-of-8 Lazy Vault Admin Safe (0x0Dd73341d6158a72b4D224541f1094188f57076E, Timelock 0x363Ba8843d06BA5968f55C26aB055162eDd62189 getMinDelay = 0s), where all 5 Curator signers are Lazy Vault Admin owners.
Show the full documented text
lidofinance/docs (earn/deployment-contracts.md line 199) lists 3/6 multisig; Mellow Core Vault docs describe bounded curator permissions.
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: controller fact: getMinDelay() = 0s
- Signer quorum
- Strong · Lowest controlling quorum: 3-of-5Evidence: mellow-lido-earn-curator-quorum: getThreshold() = 3, getOwners().length = 5 (3-of-5 Gnosis Safe); DEFAULT_ADMIN_ROLE (0x00) …
- 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=0xe5abcc40196174Ae0d12153dE286F0D8E401769d"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0xe5abcc40196174Ae0d12153dE286F0D8E401769d"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0xe5abcc40196174Ae0d12153dE286F0D8E401769d"})Curator Safe Quorum & Lazy Admin Signer Overlap
Observed onchain. getThreshold() = 3, getOwners().length = 5 (3-of-5 Gnosis Safe); DEFAULT_ADMIN_ROLE (0x00) on earnETH (0x6a37725ca7f4CE81c004c955f7280d5C704a249e) and earnUSD (0x014e6DA8F283C4aF65B2AA0f201438680A004452) held by 5-of-8 Lazy Vault Admin Safe (0x0Dd73341d6158a72b4D224541f1094188f57076E, Timelock 0x363Ba8843d06BA5968f55C26aB055162eDd62189 getMinDelay = 0s), where all 5 Curator signers are Lazy Vault Admin owners.
Documented. lidofinance/docs (earn/deployment-contracts.md line 199) lists 3/6 multisig; Mellow Core Vault docs describe bounded curator permissions.
cast call 0xe5abcc40196174Ae0d12153dE286F0D8E401769d \ "getThreshold()" \ --block 26401312 --rpc-url "$ETH_RPC_URL" cast block 26401312 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x95866ea3ef8f9a0567ce000bc8075f6dc5fb0f1e80cb4e9999ae624a2f0dc109
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Mellow Protocol / Lido Earn 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/mellow-protocol-lido-earn/)
<a href="https://pacta.wtf/protocols/mellow-protocol-lido-earn/"><img src="https://pacta.wtf/badges/mellow-protocol-lido-earn.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/mellow-protocol-lido-earn.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/mellow-protocol-lido-earn.svg.
Maintaining Mellow Protocol / Lido Earn? 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).