PACTAby Fractal Neurons
Request a dossier
Delta-neutral synthetic dollar backed by hedged positions (Base)

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: 0xBA51…27eb

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: Not determinedSigner quorum: StrongEmergency / freeze scope: Not determinedDocs-vs-chain parity: Uncompared

Observed Chain pinned; docs not assessed

Aligned means the docs are accurate, not that the protocol is low-risk. The rosette rates the controls themselves.
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
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=base&address=0xBA515304d8153c4b162dC79f867E152DF9c127eb"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "base", "address": "0xBA515304d8153c4b162dC79f867E152DF9c127eb"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
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

Status
Observed
Target
Unity (UTY) 0xBA51…27eb · Basescan
Pinned block
Base #60,070,202 · Basescan · RPC-pinned, not EAS-attested
Block hash
0x01b3f5dc…ab4a20
Controller
3-of-4 Safe 0xB237…2ccA

Observed onchain. Unity (UTY) (0xBA515304d8153c4b162dC79f867E152DF9c127eb) verified on Base Mainnet at canonical block #60,070,202 (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.

Reproduce on any archive node
cast call 0xBA515304d8153c4b162dC79f867E152DF9c127eb \
  "owner()" \
  --block 60070202 --rpc-url "$BASE_RPC_URL"
cast block 60070202 --field hash --rpc-url "$BASE_RPC_URL"
# expect 0x01b3f5dcecb67c63ba33350ec6942563f6b8a0d8ca9b4f69a752844a5bab4a20

Control-plane badge: RPC-Observed

Pacta Control Plane: 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.

Markdown
[![Pacta Control Plane](https://pacta.wtf/badges/xsy.svg)](https://pacta.wtf/protocols/xsy/)
HTML
<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.

For maintainers and issuers

Fixed this gap? 24h mainnet re-verification ($99 intro)

A maintainer and an independent verifier re-check XSY 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 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).

Read-only onchain analysis. Not investment advice. Exploit-sensitive vulnerabilities are never published here; they go through Immunefi or Cantina bounty programmes.Request a dossier (24h SLA)