Security deployment options

Combine client-side Shield, server-side Defense Mode, and the standalone binary to match your integration’s security posture.

Shield’s protection scales with how many of its enforcement points you run, not with a separate product tier. Every option below is the same validation engine, run in a different place; combine them to match your integration’s deployment model.

Enforcement points

Option	Where it runs	What it adds
Server-side (Defense Mode)	Inside the Yield API’s transaction pipeline	Runs inside the API in Monitor mode (validate and log) by default; in Block mode, transactions that fail validation are rejected before they’re returned. See Defense Mode.
Client-side, TypeScript library	In your Node.js or browser process, after you receive a transaction	A second, independent check before signing; catches anything altered in transit or by a compromised intermediate layer. See Shield integration.
Client-side, standalone binary	Any language, any environment, including restricted or air-gapped hosts	The same validation logic with no Node.js dependency and no network calls, since the vault registry is embedded in the binary.

Running server-side Defense Mode plus a client-side check (library or binary) gives you two independent checkpoints: one inside the API, one in your own signing flow. Defense Mode needs no code changes on your end; a client-side check adds protection against tampering after the API responds.

Choosing a client-side option

TypeScript / Node.js

Use the @yieldxyz/shield npm package directly in a Node.js backend, a server-side rendering layer, or a browser bundle. This is the simplest path for wallets, web apps, and hosted widget integrations.

Any other language

Use the standalone binary via its JSON-over-stdin/stdout protocol from Go, Python, Rust, or any language that can spawn a subprocess. This is the path for exchanges, custodians, and backends not written in TypeScript.

Restricted or air-gapped

Because the binary is self-contained and validates fully locally, it can run inside compiled backends, locked-down hosts, or air-gapped signing environments with no outbound network access.

For dedicated on-premises deployments or custom policy control beyond the standalone binary, contact the yield.xyz team to scope the setup.

HyperNative

Some integrations also run HyperNative, a separate partner integration for pre-signing simulation, alongside Shield. Shield and HyperNative check different things: Shield validates that a transaction matches an expected structural pattern, HyperNative simulates what the transaction would do. They’re independent layers, not tiers of the same product.

Next steps

Defense Mode

Server-side enforcement, rollout, and rollback

Shield integration

Library, standalone binary, and language guides

HyperNative

Pre-signing simulation, as a separate partner integration

Security overview

How every piece fits together