SDK state can be populated manually for tutorials, but production applications load domain data from trusted services and chain sync. This page separates the two.
Seed state blocks in Deposit, Withdraw, and Transfer how-to guides are documentation fixtures. They exist so examples run in isolation. Do not ship them as user onboarding flows.

​
Production data flow

Your application orchestrates these writes before users submit operations, keeping prepare reliable.

​
SDK method × typical source

​
What runs automatically on execute

After a successful operation, the SDK updates local state without manual calls:
  • mark spent records as consumed
  • insert output and change records
  • refresh pool commitment snapshot
  • record delivery metadata when configured
Label these updates SDK auto in your mental model — not fixtures and not backend-fed.

​
Stellar preset examples

For the shipped Stellar preset, production wiring typically looks like:
How-to Seed state sections use example G... and stpl1... addresses and static hex commitments. Treat them as copy-paste fixtures for docs only.

​
Minimal Stellar production checklist

  • Asset catalog synced from backend before showing balances
  • Pool Merkle state kept current via scanner or post-tx sync
  • Wallet private-address and scalar created through wallet UX, not hardcoded
  • Registry status fetched before registered-recipient transfers
  • Deliveries indexer populates upsertPrivateRecords for incoming notes
  • Environment variables set for pool, registry, application ID, audit public key

Domain model

What each state entity represents.

Operations

Which entities each operation consumes.

Deposit how-to

Fixture seed state example.

State integration

Adapter libraries for persisting SDK state.