PACTAby Fractal Neurons
Request a dossier
Liquid Restaking Vaults (Ethereum)

YieldNest: control-plane safety record

2 indexed control-plane surfaces for YieldNest, each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0xDF51B7843817F76220C0970eF58Ba726630028eF, 0xfcad670592a3b24869C0b51a6c6FDED4F95D6975.

What differs

Changed / discrepant

  • YNDelegator (delegates the eigenpods to the operators): docs state 2-of-3, the Safe is 2-of-4: YNDelegator Safe 0xDF51B7843817F76220C0970eF58Ba726630028eF (Ethereum): getThreshold() = 2 of getOwners() = 4 owners (Safe v1.3.0). observed vs 'YNDelegator 2/3 0xDF51B7843817F76220C0970eF58Ba726630028eF' / 'Delegates the EigenPods to the operators' (docs.yieldnest.finance/security/roles.md) documented

Matched

  • YNSecurityCouncil (contract upgrades, role admin): 3-of-5 Safe, as documented: matches the documentation

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: Not determinedSigner quorum: ModerateEmergency / freeze scope: Not determinedDocs-vs-chain parity: Weak

Delta Docs and chain differ

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
Not determined · No enforced admin delay in the published records
Signer quorum
Moderate · Lowest controlling quorum: 2-of-4Evidence: controller fact: Safe getThreshold()
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
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0xDF51B7843817F76220C0970eF58Ba726630028eF"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0xDF51B7843817F76220C0970eF58Ba726630028eF"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0xDF51B7843817F76220C0970eF58Ba726630028eF"})

YNDelegator (delegates the eigenpods to the operators): docs state 2-of-3, the Safe is 2-of-4

Status
Delta
Target
YNDelegator Safe 0xDF51…28eF · Etherscan
Pinned block
Ethereum #26,438,867 · Etherscan · sprint 26
Block hash
0x6c477521…3458ff
Attestation
Base EAS attestation 0x6692…3a08

Observed onchain. YNDelegator Safe 0xDF51B7843817F76220C0970eF58Ba726630028eF (Ethereum): getThreshold() = 2 of getOwners() = 4 owners (Safe v1.3.0).

Documented. 'YNDelegator 2/3 0xDF51B7843817F76220C0970eF58Ba726630028eF' / 'Delegates the EigenPods to the operators' (docs.yieldnest.finance/security/roles.md)

Reproduce on any archive node
cast call 0xDF51B7843817F76220C0970eF58Ba726630028eF \
  "getThreshold()" \
  --block 26438867 --rpc-url "$ETH_RPC_URL"
cast block 26438867 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0x6c477521320837df8611249a255cb7142052874937cddb9fe568f685763458ff

YNSecurityCouncil (contract upgrades, role admin): 3-of-5 Safe, as documented

Status
Aligned
Target
YNSecurityCouncil Safe 0xfcad…6975 · Etherscan
Pinned block
Ethereum #26,438,867 · Etherscan · sprint 26
Block hash
0x6c477521…3458ff
Attestation
Base EAS attestation 0x6692…3a08

Observed onchain. YNSecurityCouncil Safe 0xfcad670592a3b24869C0b51a6c6FDED4F95D6975 (Ethereum): getThreshold() = 3 of getOwners() = 5 owners (Safe v1.3.0).

Documented. 'YNSecurityCouncil 3/5 0xfcad670592a3b24869C0b51a6c6FDED4F95D6975' / 'Contract Upgrades, role admin.' (docs.yieldnest.finance/security/roles.md)

Reproduce on any archive node
cast call 0xfcad670592a3b24869C0b51a6c6FDED4F95D6975 \
  "getThreshold()" \
  --block 26438867 --rpc-url "$ETH_RPC_URL"
cast block 26438867 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0x6c477521320837df8611249a255cb7142052874937cddb9fe568f685763458ff

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

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

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

For issuers and maintainers

Maintaining YieldNest? 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)