Transaction Signing

Chain-specific guides for signing transactions with popular libraries

Overview

Yield.xyz returns unsigned transactions from its API — your application is responsible for signing and broadcasting them. This section covers how to sign transactions across every supported chain family using the most popular libraries.

Yield.xyz is non-custodial. Private keys never leave your environment; the API only returns unsigned transaction payloads for you to sign client-side or via your custody provider.

---

Supported Chains

EVM

Sign with ethers.js, viem, or wagmi on Ethereum, Polygon, Arbitrum, and all EVM-compatible networks.

Solana

Sign with @solana/web3.js or Anchor on Solana mainnet and devnet.

Cosmos (Coming Soon)

Sign with CosmJS across Cosmos Hub, Osmosis, and other Cosmos SDK chains.

Tron (Coming Soon)

Sign with TronWeb on the Tron network.

---

General Flow

1. Get unsigned transaction

   Call the Yield.xyz API (e.g. enter / exit a position) to receive an unsigned transaction payload.

2. Sign the transaction

   Use one of the chain-specific libraries documented in this section to sign the payload with your private key or wallet.

3. Broadcast

   Submit the signed transaction to the network via the library’s provider or an RPC endpoint.