Cap: control-plane safety record
3 indexed control-plane surfaces for Cap, each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0x7731129a10d51e18cDE607C5C115F26503D2c683, 0xD8236031d8279d82E615aF2BFab5FC0127A329ab.
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
Control-plane scorecard
Protective Chain stronger than documented
- 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 -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0xD8236031d8279d82E615aF2BFab5FC0127A329ab"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0xD8236031d8279d82E615aF2BFab5FC0127A329ab"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0xD8236031d8279d82E615aF2BFab5FC0127A329ab"})TimelockController minimum delay: 1 day
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).'
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
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'
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
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.'
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
Control-plane badge: 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 emerald 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/cap/)
<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.
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).