SDK guide

The existing SDK/API integration pattern remains: read state, prepare a transaction, ask the customer's wallet to sign, and track settlement. The proposed Stellar package wraps official Stellar JavaScript SDK XDR and RPC functions plus a tested account adapter. Rust contracts use a pinned Soroban SDK.

Adapter boundary

The adapter accepts explicit network configuration and exposes account linking, decimal-safe parsing, event reads, prepare action, wallet authorization, relay submission, and receipt polling. Its types distinguish Stellar G and C accounts from EVM addresses, and XDR from hex calldata. The proposed package name and final method names are published only with a tagged, tested release.

Wallet support

Our current Rift integration does not support Stellar. We plan to operate our own wallet layer for onboarding, authorization, relaying and recovery, and expose it through the SDK. A classic G-account connector will support early tests and customers who already have a Stellar wallet.

We will also evaluate Rift adding Stellar support and the providers Blux, Privy and Dfns. We will test passkey signing, contract authorization and recovery against our protocol before choosing an account implementation. Application login, wallet signing and partner API credentials will remain separate. See wallet infrastructure for the selection criteria and primary sources.

Integration examples and releases

Each release includes a payment, event creation, hedge purchase, LP deposit, claim, and receipt example tested from a clean checkout. Compare Rust and TypeScript serialization and payoff vectors. Pin the network passphrase, CLI and SDK versions, contract hashes, and supported account model. An unsigned builder response is reviewed before a signature, not trusted solely because it came from the API.

Reference: Stellar SDK catalog.