Skip to main content
Prepare wallet movements from a trusted server. The SDK returns unsigned transactions; signing stays in application-owned wallet or custody code.

Start from a wallet handle

TypeScript
The authority shape may also be secp256k1 or secp256r1. The SDK uses the public authority value to prepare the correct request; it never accesses the corresponding private key or authenticator.

SOL transfer

TypeScript

Token transfer

Token transfers are owner-based. The backend derives the token program, source associated token account, destination associated token account, and any destination account creation it needs.
TypeScript

Continue the flow

For threshold-authorized SOL or token transfers, follow the Participant Sets flow for role creation, approval collection, and compilation. A scoped SOL-transfer role carries both System Program access and a SOL spending limit. Use the requester authority and the serialized transaction’s required signer set to coordinate signing in your application. For secp256r1 and secp256k1, also process every signatureRequests / signature_requests record. The optional signing helpers can adapt application-provided signatures. Return the signed base64 transaction to the server, then use Sponsor & Submit or your own RPC path. For Jupiter swaps and multi-operation preparation, continue to Swaps and Batches.