Use these methods when connecting your application’s account data and storage to the SDK. For the setup sequence, start with Frontend integration or Backend integration.

​
Assets and balances

A local balance reflects the records loaded into the SDK. Restore the account’s records and process incoming deliveries before treating it as complete. Asset metadata comes from your integration’s catalog; it is not inferred from a symbol such as USDC.

​
Pool and recipient lookups

Prefer the network lookup methods for a standard integration. The write methods accept data; they do not fetch or independently establish its freshness.

​
Private addresses

These methods store values produced by the wallet’s private-address setup. They do not generate the values. Keep private scalars out of source code, logs, and shared configuration.

​
Updates after a transaction

Execution writes operation results into SDK state. See Transaction lifecycle for the storage stage. Preserving those changes across reloads remains part of your application’s storage integration.

​
Environment configuration

Use Set up the SDK for application IDs, audit keys, network contracts, and service configuration. An environment’s pool, registry, application, and services must be compatible; do not mix frontend and backend demo values.

​
Isolated examples

Some operation guides include a Seed state block with fixture addresses and records. Those blocks illustrate method inputs; replace them with account setup, network lookups, and restored records for a live integration.