PACTAby Fractal Neurons
Request a dossier
Stablecoin / Credit

Cap: control-plane safety record

4 indexed control-plane surfaces for Cap, each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0x7731…c683, 0xD823…29ab

What differs

Changed / discrepant

  • Access-control admin: the Timelock, not the multisig directly: AccessControl 0x7731129a10d51e18cDE607C5C115F26503D2c683: the only DEFAULT_ADMIN_ROLE member, and the only grantAccess / revokeAccess holder, is the Timelock … observed vs docs.cap.app (access controls): 'Roles are managed by the Access Control admin, currently set to Cap's multisig address' documented
    Show the full onchain evidence

    AccessControl 0x7731129a10d51e18cDE607C5C115F26503D2c683: the only DEFAULT_ADMIN_ROLE member, and the only grantAccess / revokeAccess holder, is the Timelock 0xD8236031d8279d82E615aF2BFab5FC0127A329ab; the Developer multisig 0xb8FC49402dF3ee4f8587268FB89fda4d621a8793 does not hold DEFAULT_ADMIN_ROLE, so role changes wait the 1-day delay.

Matched

  • TimelockController minimum delay: 1 day: matches the documentation
  • cUSD upgrade role (bytes4(0)) holder: the Timelock only: matches the documentation
  • Timelock operation 0x740e26ef: executed since #26,425,374; getMinDelay() still 86,400 s: matches the documentation

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: ModerateSigner 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
Moderate · 1d minimum enforced delay across control surfacesEvidence: cap-1d-timelock-min-delay-s20: observed_delay_seconds = 86400
Signer quorum
Strong · Lowest controlling quorum: 3-of-5Evidence: cap-1d-timelock-min-delay-s20: … 0xb8FC49402dF3ee4f8587268FB89fda4d621a8793 (3-of-5 Safe); the timelock is its own admin.
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=0xD8236031d8279d82E615aF2BFab5FC0127A329ab"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0xD8236031d8279d82E615aF2BFab5FC0127A329ab"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0xD8236031d8279d82E615aF2BFab5FC0127A329ab"})

Provenance · research credit

Reported by @random-solver through the Pacta Wave 2 pool (PR #110, fixture bounties/wave-2/ethereum-cap-timelock-op-0x740e-post-pin.json), merged under the Apache-2.0 commercial grant and paid $1.00 USDC (tx 0xc732…28f4); credited on cap-timelock-op-0x740e-executed-s32. Pacta then re-read every value below on two independent RPCs at its own Sprint pin and compared it with the documentation; the classifications and the Base EAS attestation are Pacta's. See the leaderboard.

TimelockController minimum delay: 1 day

Status
Aligned
Target
Cap TimelockController (Developer multisig proposer) 0xD823…29ab · Etherscan
Pinned block
Ethereum #26,425,374 · Etherscan · sprint 20
Block hash
0xfa22e277…89382d
Attestation
Base EAS attestation 0xe712…2eb7

Observed onchain. Timelock 0xD8236031d8279d82E615aF2BFab5FC0127A329ab: getMinDelay() = 86400 (1 day); PROPOSER / EXECUTOR / CANCELLER = Developer multisig 0xb8FC49402dF3ee4f8587268FB89fda4d621a8793 (3-of-5 Safe); the timelock is its own admin.

Documented. docs.cap.app (access controls): 'Critical administrative operations are routed through an OpenZeppelin TimelockController with a 1-day minimum delay (86,400 seconds).'

Reproduce on any archive node
cast call 0xD8236031d8279d82E615aF2BFab5FC0127A329ab \
  "getMinDelay()" \
  --block 26425374 --rpc-url "$ETH_RPC_URL"
cast block 26425374 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0xfa22e277760f1df7134b0af20499d6305ee4e017219a917a61a78aa76e89382d

Access-control admin: the Timelock, not the multisig directly

Status
Protective
Target
Cap AccessControl registry 0x7731…c683 · Etherscan
Pinned block
Ethereum #26,425,374 · Etherscan · sprint 20
Block hash
0xfa22e277…89382d
Attestation
Base EAS attestation 0xe712…2eb7

Observed onchain. AccessControl 0x7731129a10d51e18cDE607C5C115F26503D2c683: the only DEFAULT_ADMIN_ROLE member, and the only grantAccess / revokeAccess holder, is the Timelock 0xD8236031d8279d82E615aF2BFab5FC0127A329ab; the Developer multisig 0xb8FC49402dF3ee4f8587268FB89fda4d621a8793 does not hold DEFAULT_ADMIN_ROLE, so role changes wait the 1-day delay.

Documented. docs.cap.app (access controls): 'Roles are managed by the Access Control admin, currently set to Cap's multisig address'

Reproduce on any archive node
cast call 0x7731129a10d51e18cDE607C5C115F26503D2c683 \
  "getRoleMember(bytes32,uint256)" 0x0000000000000000000000000000000000000000000000000000000000000000 0x0 \
  --block 26425374 --rpc-url "$ETH_RPC_URL"
cast block 26425374 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0xfa22e277760f1df7134b0af20499d6305ee4e017219a917a61a78aa76e89382d

cUSD upgrade role (bytes4(0)) holder: the Timelock only

Status
Aligned
Target
Cap AccessControl registry 0x7731…c683 · Etherscan
Pinned block
Ethereum #26,425,374 · Etherscan · sprint 20
Block hash
0xfa22e277…89382d
Attestation
Base EAS attestation 0xe712…2eb7

Observed onchain. getRoleMemberCount(bytes4(0) | cUSD 0xcCcc62962d17b8914c62D74FfB843d73B2a3cccC) = 1, member 0 = the Timelock 0xD8236031d8279d82E615aF2BFab5FC0127A329ab; the Developer multisig does not hold it; the same single holder for stcUSD, AccessControl, Lender, Delegation, Oracle and FeeAuction.

Documented. docs.cap.app (contracts, access controls): 'The `bytes4(0)` selector is conventionally used for UUPS upgrade authorization (`_authorizeUpgrade`) across all upgradeable Cap contracts.'

Reproduce on any archive node
cast call 0x7731129a10d51e18cDE607C5C115F26503D2c683 \
  "getRoleMemberCount(bytes32)" 0x000000000000000000000000cccc62962d17b8914c62d74ffb843d73b2a3cccc \
  --block 26425374 --rpc-url "$ETH_RPC_URL"
cast block 26425374 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0xfa22e277760f1df7134b0af20499d6305ee4e017219a917a61a78aa76e89382d

Timelock operation 0x740e26ef: executed since #26,425,374; getMinDelay() still 86,400 s

Status
Aligned
Target
Cap TimelockController 0xD823…29ab · Etherscan
Pinned block
Ethereum #26,451,608 · Etherscan · sprint 32
Block hash
0x0266af5b…217a17
Attestation
Base EAS attestation 0x0968…bddc

Observed onchain. Cap TimelockController 0xD8236031d8279d82E615aF2BFab5FC0127A329ab (Ethereum): isOperationDone(0x740e26…0b20ea) = true and isOperationPending = false at this pin; pending at Pacta's published pin #26,425,374 (record cap-1d-timelock-min-delay-s20). getMinDelay() = 86,400 s at both pins.

Documented. 'The Timelock enforces a mandatory waiting period between when an operation is proposed and when it can be executed, giving participants time to react to parameter changes.' (docs.cap.app/concepts/access-controls)

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

Queued timelock operations

Cap — EigenLayer service-manager upgrade: slashes paid out only after EigenLayer's resolution delay. upgradeToAndCall (no initializer) on Cap's EigenServiceManager (UUPS): a slash now queues the payout, valued at slash time, and anyone completes it once EigenLayer's slash resolution delay has passed (completeSlash); rewards become USDC-only and USDC can no longer be registered as collateral. Storage is appended only (pendingSlashes).

Timelock 0xD823…29ab · 1d minimum delay · Pre-execution brief

  • 0x3397c542581a354278c3bfd01e0b9e853ec74e6c7a6ea1ec36e1d6e6cf7ab94a · executed onchain (isOperationDone = true) · EXECUTED

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

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

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

For maintainers and issuers

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

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