CIAN Yield Layer: control-plane safety record
1 indexed control-plane surface for CIAN Yield Layer, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xB13a…775d
What differs
Changed / discrepant
- Fund allocation setters: owner is a 3-of-4 Safe, the documented TimeLock is not in the path: CIAN stETH Yield Layer vault 0xB13aa2d0345b0439b064f26B82D8dCf3f508775d (Ethereum): EIP-1967 proxy, implementation 0xA1Dc0B6A02AB091580DC57bDd5Fe8a9E577E0842; in its verified source the strategy … observed vs 'Fund allocation parameters are made transparent through multi-signature and time-lock mechanisms.' documented
Show the full onchain evidence
CIAN stETH Yield Layer vault 0xB13aa2d0345b0439b064f26B82D8dCf3f508775d (Ethereum): EIP-1967 proxy, implementation 0xA1Dc0B6A02AB091580DC57bDd5Fe8a9E577E0842; in its verified source the strategy position limits, market capacity, fee rates, rebalancer and fee receiver setters are onlyOwner. owner() = 0x261090afE1E7305474F4e3eEFCAca9964eBffFf5, a 3-of-4 Safe; the vault's ProxyAdmin 0xf24955E9D0a05222373d4555f8831f7A05e83F62 is owned by the same Safe. The TimeLock its contract table lists, 0x0CBee811C47C3A5cb4637f1E58d98B0Abbb4c54f (delay() = 86,400 s, admin() = 0x261090afE1E7305474F4e3eEFCAca9964eBffFf5), owns neither.
Show the full documented text
'Fund allocation parameters are made transparent through multi-signature and time-lock mechanisms.' (docs.cian.app/llms-full.txt)
Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Not determined · Upgradeable; the delay gating the upgrade path is not in the published recordsEvidence: cian-yield-layer-allocation-no-timelock-s31: the vault's ProxyAdmin 0xf24955E9D0a05222373d4555f8831f7A05e83F62 is owned by the same Safe. The TimeLock its contract table lists …
- Timelock floor
- Moderate · 1d minimum enforced delay across control surfacesEvidence: cian-yield-layer-allocation-no-timelock-s31: … 0x0CBee811C47C3A5cb4637f1E58d98B0Abbb4c54f (delay() = 86,400 s, admin() = 0x261090afE1E7305474F4e3eEFCAca9964eBffFf5), …
- Signer quorum
- Strong · Lowest controlling quorum: 3-of-4Evidence: cian-yield-layer-allocation-no-timelock-s31: … 0x261090afE1E7305474F4e3eEFCAca9964eBffFf5, a 3-of-4 Safe; the vault's ProxyAdmin 0xf24955E9D0a05222373d4555f8831f7A05e83F62 …
- 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=0xB13aa2d0345b0439b064f26B82D8dCf3f508775d"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0xB13aa2d0345b0439b064f26B82D8dCf3f508775d"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0xB13aa2d0345b0439b064f26B82D8dCf3f508775d"})Fund allocation setters: owner is a 3-of-4 Safe, the documented TimeLock is not in the path
Observed onchain. CIAN stETH Yield Layer vault 0xB13aa2d0345b0439b064f26B82D8dCf3f508775d (Ethereum): EIP-1967 proxy, implementation 0xA1Dc0B6A02AB091580DC57bDd5Fe8a9E577E0842; in its verified source the strategy position limits, market capacity, fee rates, rebalancer and fee receiver setters are onlyOwner. owner() = 0x261090afE1E7305474F4e3eEFCAca9964eBffFf5, a 3-of-4 Safe; the vault's ProxyAdmin 0xf24955E9D0a05222373d4555f8831f7A05e83F62 is owned by the same Safe. The TimeLock its contract table lists, 0x0CBee811C47C3A5cb4637f1E58d98B0Abbb4c54f (delay() = 86,400 s, admin() = 0x261090afE1E7305474F4e3eEFCAca9964eBffFf5), owns neither.
Documented. 'Fund allocation parameters are made transparent through multi-signature and time-lock mechanisms.' (docs.cian.app/llms-full.txt)
cast call 0xB13aa2d0345b0439b064f26B82D8dCf3f508775d \ "owner()" \ --block 26450616 --rpc-url "$ETH_RPC_URL" cast block 26450616 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xd2df7ccb74a6772b51a5597c8f144f5cfae362efeabf193ecfc7c80f8ff37c35
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of CIAN Yield Layer 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.
Embed this badge (it updates when the status changes):
[](https://pacta.wtf/protocols/cian-yield-layer/)
<a href="https://pacta.wtf/protocols/cian-yield-layer/"><img src="https://pacta.wtf/badges/cian-yield-layer.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/cian-yield-layer.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/cian-yield-layer.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check CIAN Yield Layer 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 CIAN Yield Layer? 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).