dYdX V3: control-plane safety record
1 indexed control-plane surface for dYdX V3, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x64c7…c6dc
Control-plane scorecard
Aligned Docs and chain match
- Upgradeability
- Not determined · Upgrade path not in the published records
- Timelock floor
- Moderate · 1d minimum enforced delay across control surfacesEvidence: dydx-ethdydx-owner-short-timelock-2d-s32: … (verified source): getDelay() = 172,800 s, MINIMUM_DELAY() = 86,400 s, MAXIMUM_DELAY() = 604,800 s, GRACE_PERIOD() …
- 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
- 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=0x64c7d40c07EFAbec2AafdC243bF59eaF2195c6dc"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x64c7d40c07EFAbec2AafdC243bF59eaF2195c6dc"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x64c7d40c07EFAbec2AafdC243bF59eaF2195c6dc"})ethDYDX owner: the Short Timelock Executor, getDelay() 172,800 s
Observed onchain. ethDYDX 0x92D6C1e31e14520e676a687F0a93788B716BEff5 (Ethereum) owner() = 0x64c7d40c07EFAbec2AafdC243bF59eaF2195c6dc, an Executor (verified source): getDelay() = 172,800 s, MINIMUM_DELAY() = 86,400 s, MAXIMUM_DELAY() = 604,800 s, GRACE_PERIOD() = 604,800 s, the documented Short Timelock Executor column (the Long Timelock column is 7 / 5 / 21 days).
Documented. 'Parameter Description Short Timelock Executor Merkle-Pauser Executor Long Timelock Executor Starkware Executor Timelock Delay* After a proposal passes and is queued, delay before the proposal is executed 2 days 0 days 7 days 2-9 days' (docs.dydx.community/dydx-governance/voting-and-governance/dip-proposal-lifecycle); 'Owner Can mint ethDYDX tokens after mint restriction Short Timelock' (docs.dydx.community/dydx-governance/voting-and-governance/governance-parameters)
cast call 0x64c7d40c07EFAbec2AafdC243bF59eaF2195c6dc \ "getDelay()" \ --block 26451608 --rpc-url "$ETH_RPC_URL" cast block 26451608 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x0266af5bcad519d93b3be78e41b76a62985e22fbe4feef043ac3225f6f217a17
Embed Live Control-Plane Badge
Show dYdX V3's Base-EAS-attested Aligned control-plane status in a README, docs page or forum post. The badge links back to this record.
[](https://pacta.wtf/protocols/dydx-v3/)
<a href="https://pacta.wtf/protocols/dydx-v3/"><img src="https://pacta.wtf/badges/dydx-v3.svg" alt="Pacta Control Plane: Aligned · Base EAS" height="20"></a>
Static badge: https://pacta.wtf/badges/dydx-v3.svg (rebuilt with the site). Live edge badge: https://pacta-x402.pacta.workers.dev/v1/badges/dydx-v3.svg (5-minute cache).
Operating dYdX V3? Add Continuous Control-Plane Monitoring
Continuous Control-Plane Monitoring ($1,500 USDC / month) re-checks your control plane after governance proposals, signer rotations and timelock upgrades, and refreshes the dossier and attestation. It does not buy a status: the result can still be Delta whenever docs and chain diverge.