PACTAby Fractal Neurons
Request a dossier
Yield Aggregation Vaults

Yearn V3: control-plane safety record

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

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: controller fact: getMinDelay() = 604800s
Signer quorum
Strong · Lowest controlling quorum: 3-of-6Evidence: yearn-v3-role-manager-timelock: … 0x16388463d60FFE0661Cf7F1f31a7D658aC790ff7 (3-of-6 Safe).
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=0xb3bd6B2E61753C311EFbCF0111f75D29706D9a41"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0xb3bd6B2E61753C311EFbCF0111f75D29706D9a41"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0xb3bd6B2E61753C311EFbCF0111f75D29706D9a41"})

Sampled RoleManager.governance() Timelock Wiring

Status
Protective
Target
RoleManager 0xb3bd…9a41 · Etherscan
Pinned block
Ethereum #26,401,725 · Etherscan · sprint 8
Block hash
0xec3820f0…2ad7a1
Attestation
Base EAS attestation 0xfd7c…a6c2

Observed onchain. governance() = 0x88Ba032be87d5EF1fbE87336B7090767F367BF73 (TimelockController, getMinDelay() = 604800s / 7 days); getDaddy() = 0xFEB4acf3df3cDEA7399794D0869ef76A6EfAff52 (6-of-9 ychad.eth Safe); getBrain() = 0x16388463d60FFE0661Cf7F1f31a7D658aC790ff7 (3-of-6 Safe).

Documented. yearn-devdocs security overview previously noted governance was not behind a timelock (live deployment enforces stricter 7-day TimelockController).

Reproduce on any archive node
cast call 0xb3bd6B2E61753C311EFbCF0111f75D29706D9a41 \
  "governance()" \
  --block 26401725 --rpc-url "$ETH_RPC_URL"
cast block 26401725 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0xec3820f0a9db32c01728e66f78dc1958e410269e1077fd1db53df4fbce2ad7a1

Queued timelock operations

Yearn V3 — 8 new strategies added to 6 vaults with max-debt caps. One 16-call batch: add_strategy(strategy, add_to_queue=false) then update_max_debt_for_strategy on yvUSDC-1, yvUSD, yvWETH-1, yvWETH-2, yvFlexUSDC and yvFlexWETH (Flex siUSD and wstETH lenders / loopers, USDC-to-yvUSDS-1 depositors). Caps range from 10,000 WETH to 10B USDC (yvFlexUSDC, effectively uncapped).

Timelock 0x88Ba…BF73 · 7d minimum delay · Pre-execution brief

  • 0x2a14e386ce3da63615778466602757ea8dc25e8157aaee660213827a15efb5cf · ETA 2026-11-23 16:39:11 UTC · PENDING

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

This badge is amber because at least one Base-EAS-attested surface of Yearn V3 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/yearn-v3.svg)](https://pacta.wtf/protocols/yearn-v3/)
HTML
<a href="https://pacta.wtf/protocols/yearn-v3/"><img src="https://pacta.wtf/badges/yearn-v3.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>

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

For issuers and maintainers

Maintaining Yearn V3? 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)