YO Protocol: control-plane safety record
3 indexed control-plane surfaces for YO Protocol, each pinned to a canonical Base block and compared with what the protocol documents. Contracts: 0x38cE5e45D0f5d03E83863bb19B3b1A272C186F48, 0xB4b3F5C964A360bBd7201f72a55D0c48B8aD7021, 0xd460CF1f5D764acAD1c3276c549EE5f1BB671473.
What differs
Changed / discrepant
- Timelock delay: 0 s (no delay) observed vs 2 d documented
Matched
- Upgrade timelock: 48 hours, scheduled by the 4-of-6 Admin Multisig: matches the documentation
- yoETH and yoUSD upgrades: ProxyAdmins owned by the YO Timelock: matches the documentation
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Strong · Upgradeable behind a ≥48h delay (2d)Evidence: yo-protocol-vault-upgrades-behind-timelock-s22: yoETH 0x3A43AEC53490CB9Fa922847385D82fe25d0E9De7: EIP-1967 admin = ProxyAdmin 0xd460CF1f5D764acAD1c3276c549EE5f1BB671473, owner() = YO Timelock …
- Timelock floor
- Weak · 0s minimum enforced delay across control surfacesEvidence: yo-protocol-approval-registry-owner-admin-safe-s22: observed_delay_seconds = 0
- Signer quorum
- Strong · Lowest controlling quorum: 4-of-6Evidence: yo-protocol-approval-registry-owner-admin-safe-s22: … 0x67b6F699F1c8040414032a3C2C88a54db144FCd2 (4-of-6 Safe, v1.4.1, no modules), not the …
- 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=base&address=0xB4b3F5C964A360bBd7201f72a55D0c48B8aD7021"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "base", "address": "0xB4b3F5C964A360bBd7201f72a55D0c48B8aD7021"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "base", "address": "0xB4b3F5C964A360bBd7201f72a55D0c48B8aD7021"})Provenance · research credit
First reported by @kinshu7777 through the Pacta Wave 1 bounty (Slot #3, PR #29), merged under the Apache-2.0 grant and paid $25.00 USDC (tx 0x1909…6a9c ↗). 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.
Approval Registry owner: the Admin Multisig directly, not the 48-hour timelock
Observed onchain. YoApprovalRegistry 0xB4b3F5C964A360bBd7201f72a55D0c48B8aD7021: owner() = YO Admin Multisig 0x67b6F699F1c8040414032a3C2C88a54db144FCd2 (4-of-6 Safe, v1.4.1, no modules), not the YO Timelock 0x38cE5e45D0f5d03E83863bb19B3b1A272C186F48; pendingOwner() = 0; not a proxy (Sourcify exact match). It is the approvalRegistry() of yoETH 0x3A43AEC53490CB9Fa922847385D82fe25d0E9De7 and yoUSD 0x0000000f2eB9f69274678c76222B35eEc7588a65; the Pool, BridgeRoute, MorphoMarket, SwapPair and ERC4626Vault registries are also owned directly by the Admin Multisig.
Documented. docs.yo.xyz (YO V2 Security Framework): 'Approval Registry: Onchain, timelocked caps on how much of each asset a vault may approve to each contract' and 'Every path a dollar can take is written into immutable adapters and timelocked registries'
cast call 0xB4b3F5C964A360bBd7201f72a55D0c48B8aD7021 \ "owner()" \ --block 58315414 --rpc-url "$BASE_RPC_URL" cast block 58315414 --field hash --rpc-url "$BASE_RPC_URL" # expect 0x5092b494a9f8555faecfaa0f49202536e0edcf26f2bdc6e25a563442258119cd
Upgrade timelock: 48 hours, scheduled by the 4-of-6 Admin Multisig
Observed onchain. YO Timelock 0x38cE5e45D0f5d03E83863bb19B3b1A272C186F48: getMinDelay() = 172800s (48 hours); the YO Admin Multisig 0x67b6F699F1c8040414032a3C2C88a54db144FCd2 (4-of-6) holds PROPOSER_ROLE, EXECUTOR_ROLE and CANCELLER_ROLE; the timelock is its own admin (Sourcify match).
Documented. docs.yo.xyz (YO V2 Security Framework): '... with a mandatory 48-hour delay and sign-off from a 4-of-6 multi-sig of geographically distributed signers.' / contract addresses: 'YO Timelock 0x38cE5e45D0f5d03E83863bb19B3b1A272C186F48 EVMs Authority that gates contracts upgrades behind a 48 hr timelock.'
cast call 0x38cE5e45D0f5d03E83863bb19B3b1A272C186F48 \ "getMinDelay()" \ --block 58315414 --rpc-url "$BASE_RPC_URL" cast block 58315414 --field hash --rpc-url "$BASE_RPC_URL" # expect 0x5092b494a9f8555faecfaa0f49202536e0edcf26f2bdc6e25a563442258119cd
yoETH and yoUSD upgrades: ProxyAdmins owned by the YO Timelock
Observed onchain. yoETH 0x3A43AEC53490CB9Fa922847385D82fe25d0E9De7: EIP-1967 admin = ProxyAdmin 0xd460CF1f5D764acAD1c3276c549EE5f1BB671473, owner() = YO Timelock 0x38cE5e45D0f5d03E83863bb19B3b1A272C186F48; yoUSD 0x0000000f2eB9f69274678c76222B35eEc7588a65: ProxyAdmin 0x12E81209d180fF0b3FBFbfe8fA9fFdb5990e1073, owner() = the same Timelock; both use implementation 0xc84a6E01BFF58996540F1ABC22355A9DFE0d78DC; the vaults' owner() is the Admin Multisig 0x67b6F699F1c8040414032a3C2C88a54db144FCd2.
Documented. docs.yo.xyz (contract addresses): 'YO Timelock 0x38cE5e45D0f5d03E83863bb19B3b1A272C186F48 EVMs Authority that gates contracts upgrades behind a 48 hr timelock.' and 'YO Admin Multisig 0x67b6F699F1c8040414032a3C2C88a54db144FCd2 EVMs Overall manager for all yoVaults, including contract upgrades, and whitelisting new protocols and pools.'
cast call 0xd460CF1f5D764acAD1c3276c549EE5f1BB671473 \ "owner()" \ --block 58315414 --rpc-url "$BASE_RPC_URL" cast block 58315414 --field hash --rpc-url "$BASE_RPC_URL" # expect 0x5092b494a9f8555faecfaa0f49202536e0edcf26f2bdc6e25a563442258119cd
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of YO Protocol 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/yo-protocol/)
<a href="https://pacta.wtf/protocols/yo-protocol/"><img src="https://pacta.wtf/badges/yo-protocol.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/yo-protocol.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/yo-protocol.svg.
Maintaining YO Protocol? 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).