PACTAby Fractal Neurons
Request a dossier
Liquid Staking & Restaking

Mantle Liquid Staking (mETH / cmETH): control-plane safety record

1 indexed control-plane surface for Mantle Liquid Staking (mETH / cmETH), pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xc26016f1166bE7b6c5611AAB104122E0f6c2aCE2.

What differs

Changed / discrepant

  • Timelock delay: 3 d observed vs 0 s (no delay) documented

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: StrongSigner quorum: StrongEmergency / freeze scope: Not determinedDocs-vs-chain parity: Strong

Protective Chain stronger than documented

Aligned means the docs are accurate, not that the protocol is low-risk. The rosette rates the controls themselves.
Upgradeability
Not determined · Upgrade path not in the published records
Timelock floor
Strong · 3d minimum enforced delay across control surfacesEvidence: controller fact: getMinDelay() = 259200s
Signer quorum
Strong · Lowest controlling quorum: 6-of-14Evidence: mantle-lsp-meth-upgrade-timelock: … (3 days) and PROPOSER_ROLE held by 6-of-14 Security Council Safe (0x4e59e778a0fb77fBb305637435C62FaeD9aED40f); …
Emergency / freeze scope
Not determined · No pause / freeze authority in the published records
Docs-vs-chain parity
Strong · Chain matches or is stronger than the documentation

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
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0xc26016f1166bE7b6c5611AAB104122E0f6c2aCE2"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0xc26016f1166bE7b6c5611AAB104122E0f6c2aCE2"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0xc26016f1166bE7b6c5611AAB104122E0f6c2aCE2"})

Core Proxy EIP-1967 Admin Slot & 3-Day UpgradeTimelock

Status
Protective
Target
Mantle UpgradeTimelock 0xc260…aCE2 · Etherscan
Pinned block
Ethereum #26,403,121 · Etherscan · sprint 10
Block hash
0x71acee23…ef9d1c
Attestation
Base EAS attestation 0xfdd8…0e6c

Observed onchain. mETH (0xd5F7838F5C461fefF7FE49ea5ebaF7728bB0ADfa) & Staking (0xe3cBd06D7dadB3F4e6557bAb7EdD924CD1489E8f) EIP-1967 admin slots point to UpgradeTimelock (0xc26016f1166bE7b6c5611AAB104122E0f6c2aCE2) with getMinDelay() = 259200s (3 days) and PROPOSER_ROLE held by 6-of-14 Security Council Safe (0x4e59e778a0fb77fBb305637435C62FaeD9aED40f); mETH totalSupply = 217,256.94 mETH.

Documented. docs.mantle.xyz/meth/concepts/risk-management/upgradability-and-timelock.md previously noted 'The timelock is configured with a default delay of 0' (live deployment enforces stricter 3-day UpgradeTimelock).

Reproduce on any archive node
cast call 0xc26016f1166bE7b6c5611AAB104122E0f6c2aCE2 \
  "getMinDelay()" \
  --block 26403121 --rpc-url "$ETH_RPC_URL"
cast block 26403121 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0x71acee2313a2c8eacd7d2c87667dc505310b3e9224d84eaebb71d5a890ef9d1c

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

This badge is amber because at least one Base-EAS-attested surface of Mantle Liquid Staking (mETH / cmETH) 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.

Submit updated docs

Embed this badge (it updates when the status changes):

Markdown
[![Pacta Control Plane](https://pacta.wtf/badges/mantle-liquid-staking-meth-cmeth.svg)](https://pacta.wtf/protocols/mantle-liquid-staking-meth-cmeth/)
HTML
<a href="https://pacta.wtf/protocols/mantle-liquid-staking-meth-cmeth/"><img src="https://pacta.wtf/badges/mantle-liquid-staking-meth-cmeth.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>

Badge: https://pacta.wtf/badges/mantle-liquid-staking-meth-cmeth.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/mantle-liquid-staking-meth-cmeth.svg.

For issuers and maintainers

Maintaining Mantle Liquid Staking (mETH / cmETH)? 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).

Read-only onchain analysis. Not investment advice. Exploit-sensitive vulnerabilities are never published here; they go through Immunefi or Cantina bounty programmes.Request a dossier (24h SLA)