Skip to main content
The package is deliberately agnostic about where data comes from. You provide three small interfaces:

EmbeddedWalletReadDataSource

The network-facing contract. Implement it against the API or any backend:

EmbeddedWalletStorage

Local persistence for wallet list and transaction data:
A minimal in-memory implementation for testing or prototyping:

EmbeddedWalletBalanceCache

Fast in-memory or persisted cache for live balances:

Failures

All contract methods return Either<EmbeddedFailure, T>. The failure subtypes: All extend EmbeddedFailure, which extends Equatable and carries a message string.

EmbeddedWalletCacheKeys

Static string constants for storage keys — use them if you implement EmbeddedWalletStorage on top of a key-value store: