PACTAby Fractal Neurons
Request a dossier
Auto-compounding LP yield aggregator with dill staking (Ethereum)

Pickle: control-plane safety record

1 indexed control-plane surface for Pickle, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xbD17…4b0d

What differs

Changed / discrepant

  • MasterChef admin: owner is a 2-of-6 Safe, the documented 24 h timelock is not in the path: Pickle MasterChef 0xbD17B1ce622d73bD438b9E658acA5996dc394b0d (Ethereum, not a proxy): its verified source makes add, set, setPicklePerBlock, setBonusEndBlock, setDevFundDivRate and the PICKLE mint … observed vs 'All key admin functions on the MasterChef contract, which controls the emission of PICKLEs to the Farms are controlled by a 24 hour timelock contract' … documented
    Show the full onchain evidence

    Pickle MasterChef 0xbD17B1ce622d73bD438b9E658acA5996dc394b0d (Ethereum, not a proxy): its verified source makes add, set, setPicklePerBlock, setBonusEndBlock, setDevFundDivRate and the PICKLE mint path onlyOwner; MasterChef is owner() of the PICKLE token 0x429881672B9AE42b8EbA0E26cD9C73711b891Ca5. MasterChef owner() = 0x9d074E37d408542FD38be78848e8814AFB38db17, a 2-of-6 Safe (the page calls it a 2/5 multisig). The 24-hour Timelock the page links, 0x0040E05CE9A5fc9C0aBF89889f7b60c2fC278416 (delay() = 86,400 s, admin() = the same Safe), does not own MasterChef.

    Show the full documented text

    'All key admin functions on the MasterChef contract, which controls the emission of PICKLEs to the Farms are controlled by a 24 hour timelock contract' (docs.pickle.finance/security/audits-and-timelock/timelocks-and-multisig)

Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h

Control-plane scorecard

Upgradeability: StrongTimelock floor: ModerateSigner 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
Strong · Immutable or ownership renouncedEvidence: pickle-masterchef-owner-safe-no-timelock-s32: … 0xbD17B1ce622d73bD438b9E658acA5996dc394b0d (Ethereum, not a proxy): its verified source makes add, set, …
Timelock floor
Moderate · 1d minimum enforced delay across control surfacesEvidence: pickle-masterchef-owner-safe-no-timelock-s32: … 0x0040E05CE9A5fc9C0aBF89889f7b60c2fC278416 (delay() = 86,400 s, admin() = the same Safe), does not …
Signer quorum
Moderate · Lowest controlling quorum: 2-of-6Evidence: pickle-masterchef-owner-safe-no-timelock-s32: … 0x9d074E37d408542FD38be78848e8814AFB38db17, a 2-of-6 Safe (the page calls it a 2/5 multisig). …
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=0xbD17B1ce622d73bD438b9E658acA5996dc394b0d"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0xbD17B1ce622d73bD438b9E658acA5996dc394b0d"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0xbD17B1ce622d73bD438b9E658acA5996dc394b0d"})

MasterChef admin: owner is a 2-of-6 Safe, the documented 24 h timelock is not in the path

Status
Delta
Target
Pickle MasterChef 0xbD17…4b0d · Etherscan
Pinned block
Ethereum #26,451,608 · Etherscan · sprint 32
Block hash
0x0266af5b…217a17
Attestation
Base EAS attestation 0x0968…bddc

Observed onchain. Pickle MasterChef 0xbD17B1ce622d73bD438b9E658acA5996dc394b0d (Ethereum, not a proxy): its verified source makes add, set, setPicklePerBlock, setBonusEndBlock, setDevFundDivRate and the PICKLE mint path onlyOwner; MasterChef is owner() of the PICKLE token 0x429881672B9AE42b8EbA0E26cD9C73711b891Ca5. MasterChef owner() = 0x9d074E37d408542FD38be78848e8814AFB38db17, a 2-of-6 Safe (the page calls it a 2/5 multisig). The 24-hour Timelock the page links, 0x0040E05CE9A5fc9C0aBF89889f7b60c2fC278416 (delay() = 86,400 s, admin() = the same Safe), does not own MasterChef.

Documented. 'All key admin functions on the MasterChef contract, which controls the emission of PICKLEs to the Farms are controlled by a 24 hour timelock contract' (docs.pickle.finance/security/audits-and-timelock/timelocks-and-multisig)

Reproduce on any archive node
cast call 0xbD17B1ce622d73bD438b9E658acA5996dc394b0d \
  "owner()" \
  --block 26451608 --rpc-url "$ETH_RPC_URL"
cast block 26451608 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0x0266af5bcad519d93b3be78e41b76a62985e22fbe4feef043ac3225f6f217a17

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

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

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

For maintainers and issuers

Fixed this gap? 24h mainnet re-verification ($99 intro)

A maintainer and an independent verifier re-check Pickle on mainnet within 24h and attest the result on Base. The fee pays for the 24-hour mainnet re-verification work, never the grade: your attestation reads Aligned when on-chain controls match the published documentation, and Delta when they do not.

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