Stake DAO: control-plane safety record
4 indexed control-plane surfaces for Stake DAO, each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0x2d8BcE1FaE00a959354aCD9eBf9174337A64d4fb, 0xF930EBBd05eF8b25B1797b9b2109DDC9B0d43063, 0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a.
What differs
Changed / discrepant
- Timelock delay: 5 d observed vs 2 d documented
- Executing queued changes: permissioned (EXECUTOR_ROLE held by the governance multisig), not permissionless: ProtocolTimelock 0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a: hasRole(EXECUTOR_ROLE, address(0)) = false, so execution is permissioned, not permissionless; observed vs docs.stakedao.org (timelock, role structure): Executor 'Can execute operations after delay (permissionless)'; documented
Show the full onchain evidence
ProtocolTimelock 0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a: hasRole(EXECUTOR_ROLE, address(0)) = false, so execution is permissioned, not permissionless; the Governance Safe 0xB0552b6860CE5C0202976Db056b5e3Cc4f9CC765 (3-of-5, Safe v1.3.0, 3 modules enabled) holds EXECUTOR_ROLE, PROPOSER_ROLE, CANCELLER_ROLE and GUARDIAN_ROLE; the timelock is its own admin and does not hold EXECUTOR_ROLE (AccessControl without enumeration: other holders are not excluded).
Show the full documented text
docs.stakedao.org (timelock, role structure): Executor 'Can execute operations after delay (permissionless)'; Proposer 'Can schedule operations (governance multisig)'
- Treasury wallet (Ethereum): a 3-of-5 multisig: Treasury Safe 0xF930EBBd05eF8b25B1797b9b2109DDC9B0d43063: 3-of-5 (getThreshold() = 3, getOwners() = 5 owners; Safe v1.3.0, no modules), the same five signers as the Governance Safe … observed vs docs.stakedao.org (treasury): 'All wallets use a 4-of-7 multisig structure.' documented
Show the full onchain evidence
Treasury Safe 0xF930EBBd05eF8b25B1797b9b2109DDC9B0d43063: 3-of-5 (getThreshold() = 3, getOwners() = 5 owners; Safe v1.3.0, no modules), the same five signers as the Governance Safe 0xB0552b6860CE5C0202976Db056b5e3Cc4f9CC765.
Show the full documented text
docs.stakedao.org (treasury): 'All wallets use a 4-of-7 multisig structure.' / 'Ethereum | `0xf930ebbd05ef8b25b1797b9b2109ddc9b0d43063`'
Matched
- ProtocolController owner: the ProtocolTimelock: matches the documentation
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Strong · Immutable or ownership renouncedEvidence: stake-dao-timelock-owns-protocol-controller-s22: … 0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a; pendingOwner() = 0; not a proxy (Sourcify exact match); the timelock's …
- Timelock floor
- Strong · 5d minimum enforced delay across control surfacesEvidence: controller fact: getMinDelay() = 432000s
- Signer quorum
- Strong · Lowest controlling quorum: 3-of-5Evidence: stake-dao-timelock-executor-permissioned-s22: … 0xB0552b6860CE5C0202976Db056b5e3Cc4f9CC765 (3-of-5, Safe v1.3.0, 3 modules enabled) holds …
- 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=0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a"})Provenance · research credit
First reported by @veriton-dev through the Pacta Wave 1 bounty (Slot #1, PR #27), merged under the Apache-2.0 grant and paid $25.00 USDC (tx 0x4520…0ff9 ↗). 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.
Protocol changes wait 5 days, longer than the documented 48 hours
Observed onchain. ProtocolTimelock 0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a: getMinDelay() = 432000s (5 days). It owns the ProtocolController 0x2d8BcE1FaE00a959354aCD9eBf9174337A64d4fb; the Governance Safe 0xB0552b6860CE5C0202976Db056b5e3Cc4f9CC765 holds PROPOSER_ROLE; OpenZeppelin TimelockController (Sourcify exact match).
Documented. docs.stakedao.org (timelock): 'Stake DAO's core contracts are protected by a governance timelock that enforces a 48-hour delay on all protocol changes.' and 'A proposer submits the operation with a minimum 48-hour delay'
cast call 0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a \ "getMinDelay()" \ --block 26429396 --rpc-url "$ETH_RPC_URL" cast block 26429396 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x3fb83aa053c26ac6b98d634858da1b3c23bb65bae7a12f8f14d72d8273e16d71
Executing queued changes: permissioned (EXECUTOR_ROLE held by the governance multisig), not permissionless
Observed onchain. ProtocolTimelock 0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a: hasRole(EXECUTOR_ROLE, address(0)) = false, so execution is permissioned, not permissionless; the Governance Safe 0xB0552b6860CE5C0202976Db056b5e3Cc4f9CC765 (3-of-5, Safe v1.3.0, 3 modules enabled) holds EXECUTOR_ROLE, PROPOSER_ROLE, CANCELLER_ROLE and GUARDIAN_ROLE; the timelock is its own admin and does not hold EXECUTOR_ROLE (AccessControl without enumeration: other holders are not excluded).
Documented. docs.stakedao.org (timelock, role structure): Executor 'Can execute operations after delay (permissionless)'; Proposer 'Can schedule operations (governance multisig)'
cast call 0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a \ "hasRole(bytes32,address)" 0xd8aa0f3194971a2a116679f7c2090f6939c8d4e01a2a8d7e41d55e5351469e63 0x0000000000000000000000000000000000000000 \ --block 26429396 --rpc-url "$ETH_RPC_URL" cast block 26429396 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x3fb83aa053c26ac6b98d634858da1b3c23bb65bae7a12f8f14d72d8273e16d71
ProtocolController owner: the ProtocolTimelock
Observed onchain. ProtocolController 0x2d8BcE1FaE00a959354aCD9eBf9174337A64d4fb: owner() = ProtocolTimelock 0xb27afc7844988948FBd6210AeF4E1362bC2d8E6a; pendingOwner() = 0; not a proxy (Sourcify exact match); the timelock's protocolController() is this contract.
Documented. docs.stakedao.org (timelock): 'The ProtocolTimelock contract owns the ProtocolController and all critical protocol parameters.' / contract addresses: 'PROTOCOL_CONTROLLER | `0x2d8BcE1FaE00a959354aCD9eBf9174337A64d4fb`'
cast call 0x2d8BcE1FaE00a959354aCD9eBf9174337A64d4fb \ "owner()" \ --block 26429396 --rpc-url "$ETH_RPC_URL" cast block 26429396 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x3fb83aa053c26ac6b98d634858da1b3c23bb65bae7a12f8f14d72d8273e16d71
Treasury wallet (Ethereum): a 3-of-5 multisig
Observed onchain. Treasury Safe 0xF930EBBd05eF8b25B1797b9b2109DDC9B0d43063: 3-of-5 (getThreshold() = 3, getOwners() = 5 owners; Safe v1.3.0, no modules), the same five signers as the Governance Safe 0xB0552b6860CE5C0202976Db056b5e3Cc4f9CC765.
Documented. docs.stakedao.org (treasury): 'All wallets use a 4-of-7 multisig structure.' / 'Ethereum | `0xf930ebbd05ef8b25b1797b9b2109ddc9b0d43063`'
cast call 0xF930EBBd05eF8b25B1797b9b2109DDC9B0d43063 \ "getThreshold()" \ --block 26429396 --rpc-url "$ETH_RPC_URL" cast block 26429396 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x3fb83aa053c26ac6b98d634858da1b3c23bb65bae7a12f8f14d72d8273e16d71
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Stake DAO 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/stake-dao/)
<a href="https://pacta.wtf/protocols/stake-dao/"><img src="https://pacta.wtf/badges/stake-dao.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/stake-dao.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/stake-dao.svg.
Maintaining Stake DAO? 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).