Skip to main content
yield.xyz never holds funds, keys or signing authority. Every action returns an unsigned transaction: we build it, Shield verifies it, and your wallet, custodian or user signs it. Security on the platform is organized around that handoff.

Your keys, your crypto

yield.xyz never has access to user private keys. The APIs only return unsigned transactions for you to sign and broadcast.

​
The life of a transaction

1

Craft: we build the transaction

Your app requests an action, such as enter, exit or manage. Audited integrations assemble the exact deposit, unstake or redemption, with parameters, routing and gas.
2

Verify: Shield decodes and checks it

Shield decodes the transaction, simulates the state change and checks it against a verified pattern for that yield: correct contract, function, parameters and receiver. It runs inside the API (Defense Mode) and, optionally, again in your own stack before signing. Anything that fails is blocked.
3

Sign: only you can execute it

Your app signs with the user’s wallet or your custody solution and broadcasts to the chain. yield.xyz is never in this step.

​
Controls

SOC 2 Type II

Controls are examined continuously, not once. Reports are available on the Trust Center.

Independent audits

Every contract and integration is audited before it goes live.

Live monitoring

Every deployment is watched 24/7. Sentinel Vaults add Hypernative and Blockaid monitoring with a pre-signed pause.

On-prem Shield

For regulated environments, Shield verification can run inside your own perimeter.

Compliance tooling

API-level geoblocking maintained by yield.xyz, based on IP and wallet addresses.

Enterprise SLA

99.9% read and 99.5% write availability, up to 1,000 requests per second, and a 30 minute Sev 1 response, 24/7.

​
What Shield covers

Shield

Decodes every unsigned transaction and validates it against a verified pattern for the specific yield. Runs as a TypeScript library or a standalone binary, so it is usable from any language.

Defense Mode

Shield running server-side, inside the API’s own transaction pipeline. A project can run it in Monitor mode (log only) or Block mode (reject failed transactions before they are returned).

HyperNative

A partner integration for pre-signing simulation and protocol monitoring.

Security deployment options

How to combine server-side Defense Mode with a client-side check for two independent checkpoints.
Shield’s checks are structural: it does not evaluate whether the underlying protocol itself is safe, and it does not claim to catch every possible attack. See Defense Mode for what it does and does not mitigate.

​
Report a vulnerability

Email security@yield.xyz with a description, steps to reproduce and the potential impact. We acknowledge reports within 24 hours. See the Security notice for the full disclosure process.

​
Next steps

Audits & compliance

SOC 2 Type II, audit reports and due diligence material.

Trust Center

Security posture and trust artifacts at trust.yield.xyz.