Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

SDK Documentation Spark
Request API Key

Server-side configuration

How the SDK is configured on a server depends on whose wallets it holds.

Multi-userTreasury
Wallets per processmany, one per userone, owned by the service
SDK instancebuilt per request, disconnected after itone, long lived
Background tasksoff: the host drives sync, claiming and event deliveryon
Config presetdefault_server_configdefault_server_configdefaultServerConfigdefaultServerConfigdefaultServerConfigdefaultServerConfigdefaultServerConfigDefaultServerConfigDefaultServerConfigdefault_configdefault_configdefaultConfigdefaultConfigdefaultConfigdefaultConfigdefaultConfigDefaultConfigDefaultConfig

Multi-user configuration is for a service that holds a wallet per user. The SDK is used as a library: an instance is built for one operation and disconnected, and the host decides when sync, claiming and event delivery happen.

Treasury configuration is for a single wallet the service itself owns, such as a float or a settlement account. It is a standard deployment with a few defaults worth changing.

A service can run both, as separate SDK instances with separate configs.