The Trustware SDK emits typed events as users move through the deposit flow. You can subscribe to these events to track progress, update your own UI state, or send analytics without polling or manual state management.Documentation Index
Fetch the complete documentation index at: https://docs.trustware.io/llms.txt
Use this file to discover all available pages before exploring further.
The TrustwareEvent type
All events share a discriminated union type called TrustwareEvent. Each variant has a type string field you can use to narrow the event in a handler.
Event types
type | When it fires | Additional fields |
|---|---|---|
error | Any SDK error (includes API key validation, tx failures, etc.) | error: TrustwareError |
transaction_started | Wallet opens with the transaction prompt | none |
transaction_success | Tx confirmed on-chain; carries txHash and optional Transaction record | txHash: string, transaction?: Transaction |
wallet_connected | Wallet attached; carries address | address: string |
token_page_loaded | Token list page fetched (with pagination metadata) | chainRef: string, count: number, hasNextPage: boolean, query?: string, cursor?: string |
token_page_error | Token list fetch failed | chainRef: string, message: string, query?: string, cursor?: string |
balance_stream_chunk | Wallet balance scan chunk received | address: string, chunkSize: number |
balance_stream_fallback | Balance scan fell back to a slower method | address: string, message: string |
token_page_loaded, token_page_error, balance_stream_chunk, and balance_stream_fallback are gated by the tokensPagination and balanceStreaming feature flags. Both are enabled by default; set either flag to false in features to suppress the corresponding events.How to subscribe
Pass anonEvent callback in your TrustwareConfigOptions. This works whether you are using TrustwareProvider or calling Trustware.init() directly in the headless core.
event to the correct shape inside each if branch, so accessing event.txHash is fully type-safe.
The onSuccess shortcut
For the common case of reacting to a completed deposit, you can use onSuccess instead of filtering inside onEvent. It receives the Transaction object directly.
onSuccess and onEvent are independent; you can use both at the same time.
Example: tracking deposit completion
The following example shows how to useonEvent to display a success notification when a deposit completes, and log any errors to an external service.
