ether.fi Core (eETH / weETH): control-plane safety record
2 indexed control-plane surfaces for ether.fi Core (eETH / weETH), each pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x9f26d4C958fD811A1F59B01B86Be7dFFc9d20761.
What differs
Changed / discrepant
- Core Upgrade Timelock (10d) — queued LayerZero V2 setDelegate to Timelock: getMinDelay() = 864000s (10d); observed vs Public pre-execution brief https://pacta.wtf/briefs/etherfi-op-0x244e/ (decoded calldata, storage-layout and delegate trace). documented
Matched
- Sampled Upgrade & Operating Timelock Delays: matches the documentation
Control-plane scorecard
Protective Chain stronger than documented
- Upgradeability
- Not determined · Upgrade path not in the published records
- Timelock floor
- Strong · 2d minimum enforced delay across control surfacesEvidence: etherfi-core-timelocks: … (0xcD425f44758a08BaAB3C4908f3e3dE5776e45d7a) getMinDelay() = 172800s (2 days); LiquidityPool (0x308861A430be4cce5502d0A12724771Fc6DaF216) …
- 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
- 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 -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0x9f26d4C958fD811A1F59B01B86Be7dFFc9d20761"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x9f26d4C958fD811A1F59B01B86Be7dFFc9d20761"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x9f26d4C958fD811A1F59B01B86Be7dFFc9d20761"})Sampled Upgrade & Operating Timelock Delays
Observed onchain. Upgrade Timelock getMinDelay() = 864000s (10 days); Operating Timelock (0xcD425f44758a08BaAB3C4908f3e3dE5776e45d7a) getMinDelay() = 172800s (2 days); LiquidityPool (0x308861A430be4cce5502d0A12724771Fc6DaF216) getTotalPooledEther = 2,276,605.53 ETH.
Documented. Sampled Upgrade (10d) and Operating (2d) TimelockController delays verified at block 26401638.
cast call 0x9f26d4C958fD811A1F59B01B86Be7dFFc9d20761 \ "getMinDelay()" \ --block 26401638 --rpc-url "$ETH_RPC_URL" cast block 26401638 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xe62ad2969617ad07c23bec298c3d5e197ea7c3084f7f66c90d2eb51d04c6273e
Core Upgrade Timelock (10d) — queued LayerZero V2 setDelegate to Timelock
Observed onchain. getMinDelay() = 864000s (10d); operation 0x244e3f…71359f: isOperationPending() = true, getTimestamp() = 1795193651 (2026-11-20 16:54:11 UTC). The scheduled call EtherfiL1SyncPoolETH (0xD789870beA40D056A4d26055d0bEFcC8755DA146).setDelegate(EtherFiTimelock) puts the LayerZero V2 endpoint delegate behind the 10-day timelock.
Documented. Public pre-execution brief https://pacta.wtf/briefs/etherfi-op-0x244e/ (decoded calldata, storage-layout and delegate trace).
cast call 0x9f26d4C958fD811A1F59B01B86Be7dFFc9d20761 \ "getMinDelay()" \ --block 26405302 --rpc-url "$ETH_RPC_URL" cast block 26405302 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xe05f4fd5698556131e7514b3a8eb24960962a768f8e0bfe0e99e3f1681127f65
Queued timelock operations
ether.fi — LayerZero V2 delegate moved behind the 10-day timelock. EtherfiL1SyncPoolETH.setDelegate(EtherFiTimelock): protective hardening of the OApp's messaging configuration.
Timelock 0x9f26…0761 · 10d minimum delay · Pre-execution brief
0x244e3f6c3df722246c471cee58804dd34c7703fce9cee1eadc1c5a85f171359f· ETA 2026-11-20 16:54:11 UTC · PENDING
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of ether.fi Core (eETH / weETH) 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/ether-fi-core-eeth-weeth/)
<a href="https://pacta.wtf/protocols/ether-fi-core-eeth-weeth/"><img src="https://pacta.wtf/badges/ether-fi-core-eeth-weeth.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/ether-fi-core-eeth-weeth.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/ether-fi-core-eeth-weeth.svg.
Maintaining ether.fi Core (eETH / weETH)? 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).