PACTAby Fractal Neurons
Request a dossier
Yield on ApeCoin deposits matched with BAYC and MAYC collections (Ethereum)

BendDAO APE Staking: control-plane safety record

1 indexed control-plane surface for BendDAO APE Staking, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x4e4C…2B6e

What differs

Changed / discrepant

  • Timelock delay: 1 d observed vs 7 d documented

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

Control-plane scorecard

Upgradeability: ModerateTimelock floor: ModerateSigner quorum: Not determinedEmergency / 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
Moderate · Upgradeable behind a 1h–47h delay (1d)Evidence: benddao-timelock-7d-reads-1d-s32: BEND token 0x0d02755a5700414B26FF040e1dE35D337DF56218 (Ethereum): EIP-1967 proxy, implementation 0x02863C14603C3b157379999F567DDECE151e9153, admin slot = …
Timelock floor
Moderate · 1d minimum enforced delay across control surfacesEvidence: benddao-timelock-7d-reads-1d-s32: BEND token 0x0d02755a5700414B26FF040e1dE35D337DF56218 (Ethereum): EIP-1967 proxy, implementation 0x02863C14603C3b157379999F567DDECE151e9153, admin slot = …
Signer quorum
Not determined · No signer quorum in the published records
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=0x4e4C314E2391A58775be6a15d7A05419ba7D2B6e"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0x4e4C314E2391A58775be6a15d7A05419ba7D2B6e"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0x4e4C314E2391A58775be6a15d7A05419ba7D2B6e"})

BEND ProxyAdmin owner: BendDAO Timelock 7D, getMinDelay() 86,400 s

Status
Delta
Target
BendDAO Timelock 7D (owner of the Incentive ProxyAdmin) 0x4e4C…2B6e · Etherscan
Pinned block
Ethereum #26,451,608 · Etherscan · sprint 32
Block hash
0x0266af5b…217a17
Attestation
Base EAS attestation 0x0968…bddc

Observed onchain. BEND token 0x0d02755a5700414B26FF040e1dE35D337DF56218 (Ethereum): EIP-1967 proxy, implementation 0x02863C14603C3b157379999F567DDECE151e9153, admin slot = ProxyAdmin 0x859f6e05410893fe64BC84d92BdA773fF798cf66 (the docs' 'Incentive' Proxy Admin). ProxyAdmin owner() = 0x4e4C314E2391A58775be6a15d7A05419ba7D2B6e, the docs' 'BendDAO Timelock 7D', an OpenZeppelin TimelockController (verified source): getMinDelay() = 86,400 s at this pin; the security page lists it at 7 days.

Documented. '| Incentive | 7 Days Timelock | 0x859f6e05410893fe64BC84d92BdA773fF798cf66 |' (raw.githubusercontent.com/BendDAO/bend-gitbook-portal/HEAD/risk/security-and-audits.md)

Reproduce on any archive node
cast call 0x4e4C314E2391A58775be6a15d7A05419ba7D2B6e \
  "getMinDelay()" \
  --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 BendDAO APE Staking 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/benddao-ape-staking.svg)](https://pacta.wtf/protocols/benddao-ape-staking/)
HTML
<a href="https://pacta.wtf/protocols/benddao-ape-staking/"><img src="https://pacta.wtf/badges/benddao-ape-staking.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>

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

For maintainers and issuers

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

A maintainer and an independent verifier re-check BendDAO APE Staking 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 BendDAO APE Staking? 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)