Puffer Finance (pufETH): control-plane safety record
3 indexed control-plane surfaces for Puffer Finance (pufETH), each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0x3C28B7c7Ba1A1f55c9Ce66b263B33B204f2126eA, 0x446d4d6b26815f9bA78B5D454E303315D586Cb2a, 0xC0896ab1A8cae8c2C1d27d011eb955Cca955580d.
What differs
Changed / discrepant
- Community Multisig threshold: 3-of-7: Safe 0x446d4d6b26815f9bA78B5D454E303315D586Cb2a (= Timelock COMMUNITY_MULTISIG()): getThreshold() = 3 with 7 owners (v1.3.0); observed vs docs.puffer.fi (multisig): 'Puffer's Community Multisig is a 3-of-6 multisig composed of reputable and aligned Ethereum community members and auditing firms.' documented
Show the full onchain evidence
Safe 0x446d4d6b26815f9bA78B5D454E303315D586Cb2a (= Timelock COMMUNITY_MULTISIG()): getThreshold() = 3 with 7 owners (v1.3.0); holds AccessManager role 1 (upgrader) with execution delay 0.
Matched
- Timelock delay: 7 days: matches the documentation
- Operations Multisig threshold: 3-of-6: matches the documentation
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Strong · Upgradeable behind a ≥48h delay (168h)Evidence: puffer-7d-timelock-delay-s20: ACCESS_MANAGER() = 0x8c1686069474410E6243425f4a10177a94EBEE11, the authority() of PufferVault 0xD9A442856C234a39a81a089C06451EBAa4306a72, where upgradeToAndCall …
- Timelock floor
- Strong · 168h minimum enforced delay across control surfacesEvidence: puffer-7d-timelock-delay-s20: ACCESS_MANAGER() = 0x8c1686069474410E6243425f4a10177a94EBEE11, the authority() of PufferVault 0xD9A442856C234a39a81a089C06451EBAa4306a72, where upgradeToAndCall …
- Signer quorum
- Strong · Lowest controlling quorum: 3-of-6Evidence: 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 -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0x3C28B7c7Ba1A1f55c9Ce66b263B33B204f2126eA"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x3C28B7c7Ba1A1f55c9Ce66b263B33B204f2126eA"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x3C28B7c7Ba1A1f55c9Ce66b263B33B204f2126eA"})Timelock delay: 7 days
Observed onchain. Timelock 0x3C28B7c7Ba1A1f55c9Ce66b263B33B204f2126eA: delay() = 604801, MINIMUM_DELAY() = 604800 (the verified source accepts only delays above the minimum); ACCESS_MANAGER() = 0x8c1686069474410E6243425f4a10177a94EBEE11, the authority() of PufferVault 0xD9A442856C234a39a81a089C06451EBAa4306a72, where upgradeToAndCall maps to role 0, held by the Timelock.
Documented. docs.puffer.fi (multisig): 'The timelock enforces that important function calls and upgrades must go through a 7-day delay before being executed.'
cast call 0x3C28B7c7Ba1A1f55c9Ce66b263B33B204f2126eA \ "delay()" \ --block 26425374 --rpc-url "$ETH_RPC_URL" cast block 26425374 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xfa22e277760f1df7134b0af20499d6305ee4e017219a917a61a78aa76e89382d
Community Multisig threshold: 3-of-7
Observed onchain. Safe 0x446d4d6b26815f9bA78B5D454E303315D586Cb2a (= Timelock COMMUNITY_MULTISIG()): getThreshold() = 3 with 7 owners (v1.3.0); holds AccessManager role 1 (upgrader) with execution delay 0.
Documented. docs.puffer.fi (multisig): 'Puffer's Community Multisig is a 3-of-6 multisig composed of reputable and aligned Ethereum community members and auditing firms.'
cast call 0x446d4d6b26815f9bA78B5D454E303315D586Cb2a \ "getThreshold()" \ --block 26425374 --rpc-url "$ETH_RPC_URL" cast block 26425374 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xfa22e277760f1df7134b0af20499d6305ee4e017219a917a61a78aa76e89382d
Operations Multisig threshold: 3-of-6
Observed onchain. Safe 0xC0896ab1A8cae8c2C1d27d011eb955Cca955580d (= Timelock OPERATIONS_MULTISIG()): getThreshold() = 3 with 6 owners (v1.3.0); holds AccessManager roles 22 and 77, not roles 0 or 1.
Documented. docs.puffer.fi (multisig): 'Puffer's Operations Multisig is a 3-of-6 multisig operated by the team.'
cast call 0xC0896ab1A8cae8c2C1d27d011eb955Cca955580d \ "getThreshold()" \ --block 26425374 --rpc-url "$ETH_RPC_URL" cast block 26425374 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xfa22e277760f1df7134b0af20499d6305ee4e017219a917a61a78aa76e89382d
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Puffer Finance (pufETH) 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/puffer-finance-pufeth/)
<a href="https://pacta.wtf/protocols/puffer-finance-pufeth/"><img src="https://pacta.wtf/badges/puffer-finance-pufeth.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/puffer-finance-pufeth.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/puffer-finance-pufeth.svg.
Maintaining Puffer Finance (pufETH)? 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).