XSY: control-plane safety record
1 indexed control-plane surface for XSY, with its controller and timelock state pinned to a canonical Base block over archive JSON-RPC (not EAS-attested; documentation parameters are linked, not compared). Contract: 0xBA515304d8153c4b162dC79f867E152DF9c127eb.
Control-plane scorecard
Observed Chain pinned; docs not assessed
- Upgradeability
- Not determined · Upgradeable; the delay gating the upgrade path is not in the published recordsEvidence: xsy-control-plane: is_eip1967_proxy = true
- Timelock floor
- Not determined · No enforced admin delay in the published records
- Signer quorum
- Strong · Lowest controlling quorum: 3-of-4Evidence: xsy-control-plane: … slot zero. Direct owner() returns Safe 3-of-4 0xB237EB3c71a0f351BD121b0C467248473fbC2ccA.
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Uncompared · Uncompared: documentation not assessed (RPC-observed)
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=0xBA515304d8153c4b162dC79f867E152DF9c127eb"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "base", "address": "0xBA515304d8153c4b162dC79f867E152DF9c127eb"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "base", "address": "0xBA515304d8153c4b162dC79f867E152DF9c127eb"})Provenance
RPC-pinned record: read over public JSON-RPC at the Base block shown below and independently re-read at the same block by a second Pacta seat. It is not EAS-attested: no sprint number, no summary document and no Base EAS UID. Status Observed (RPC-observed baseline): the onchain control plane is pinned at block height; whether it matches the protocol's documented parameters is not assessed here (the documentation is linked for reference). Machine-readable: /api/v1/rpc-pinned.json. The Base-EAS-attested Sprint records are in /api/v1/index.json.
Unity (UTY) · EIP-1967 Proxy & Controller Chain
Observed onchain. Unity (UTY) (0xBA515304d8153c4b162dC79f867E152DF9c127eb) verified on Base Mainnet at canonical block #58,956,515 (122 bytes runtime code). EIP-1967 proxy: implementation 0xF2F6E1a62d3d1f0efB01C28e485f1dC8B173cE2B, admin slot zero. Direct owner() returns Safe 3-of-4 0xB237EB3c71a0f351BD121b0C467248473fbC2ccA.
Documentation (linked, not compared). XSY documentation is linked for reference (https://yieldpoint.io/). This RPC-pinned record does not compare documentation parameters with the on-chain state.
cast call 0xBA515304d8153c4b162dC79f867E152DF9c127eb \ "owner()" \ --block 58956515 --rpc-url "$BASE_RPC_URL" cast block 58956515 --field hash --rpc-url "$BASE_RPC_URL" # expect 0x82af637fd7a689f4ea41c0ecd1a84a407ea93f2622b8e9c06184327d957129d0
Control-plane badge: RPC-Observed
The slate badge states only what Pacta pinned on-chain; it makes no documentation claim until XSY is compared with its documentation and attested on Base.
[](https://pacta.wtf/protocols/xsy/)
<a href="https://pacta.wtf/protocols/xsy/"><img src="https://pacta.wtf/badges/xsy.svg" alt="Pacta Control Plane: RPC-Observed" height="20"></a>
Badge: https://pacta.wtf/badges/xsy.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/xsy.svg.
Maintaining XSY? 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).