PACTAby Fractal Neurons
Request a dossier
On-chain Asset Management

Enzyme Finance: control-plane safety record

1 indexed control-plane surface for Enzyme Finance, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xC3DC853dD716bd5754f421ef94fdCbac3902ab32.

What differs

Changed / discrepant

  • Timelock delay: 7 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 · 7d minimum enforced delay across control surfacesEvidence: enzyme-dispatcher-7d-migration-timelock-s18: observed_delay_seconds = 604800
Signer quorum
Strong · Lowest controlling quorum: 3-of-5Evidence: enzyme-dispatcher-7d-migration-timelock-s18: … + migrationTimelock). getOwner() = 3-of-5 Safe 0xb270FE91e8E4b80452fBF1b4704208792A350f53 …
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=0xC3DC853dD716bd5754f421ef94fdCbac3902ab32"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0xC3DC853dD716bd5754f421ef94fdCbac3902ab32"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0xC3DC853dD716bd5754f421ef94fdCbac3902ab32"})

Dispatcher migration timelock = 7 days (specs: 'no longer used and is set to 0')

Status
Protective
Target
Enzyme Dispatcher 0xC3DC…ab32 · Etherscan ↗
Pinned block
Ethereum #26,421,541 · Etherscan ↗ · sprint 18
Block hash
0xfc2e93c5…17150d

Observed onchain. Dispatcher (0xC3DC853dD716bd5754f421ef94fdCbac3902ab32, Sourcify exact_match) getMigrationTimelock() = 604800s (7d), enforced by signalMigration (executableTimestamp = block.timestamp + migrationTimelock). getOwner() = 3-of-5 Safe 0xb270FE91e8E4b80452fBF1b4704208792A350f53 (getNominatedOwner() = 0), which also owns the live FundDeployer 0x4f1C53F096533C04d8157EFB6Bca3eb22ddC6360 (getCurrentFundDeployer()); setCurrentFundDeployer and setMigrationTimelock are onlyOwner with no delay.

Documented. specs.enzyme.finance (fund lifecycle): 'MigratorA waits for the `migrationTimelock` defined on the `Dispatcher` to pass. [NOTE: This is no longer used and is set to `0`]'; access-control handoff: 'The owner is already the Enzyme Council.' (no Council address or threshold is published).

Reproduce on any archive node
cast call 0xC3DC853dD716bd5754f421ef94fdCbac3902ab32 \
  "getMigrationTimelock()" \
  --block 26421541 --rpc-url "$ETH_RPC_URL"
cast block 26421541 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0xfc2e93c53812cd390b29924a4e217bd4f75d77725bd2882968fb5b087a17150d

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

This badge is amber because at least one Base-EAS-attested surface of Enzyme Finance differs from what the protocol documents. It turns to the emerald 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/enzyme-finance.svg)](https://pacta.wtf/protocols/enzyme-finance/)
HTML
<a href="https://pacta.wtf/protocols/enzyme-finance/"><img src="https://pacta.wtf/badges/enzyme-finance.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>

Badge: https://pacta.wtf/badges/enzyme-finance.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/enzyme-finance.svg.

For issuers and maintainers

Maintaining Enzyme Finance? 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) →