Reference stacks often provide an npm package for wallets. Replace the package and host names in the following with the Lineage or community client you are actually using; the flow (install → configure hosts → create or restore a wallet) stays the same.
Install
# Example only — confirm package name in the repo you use npm install <lineage-or-community-wallet>
Configuration
You typically set at least: a mempool base URL, a storage base URL, and a passphrase to encrypt local keys. Optional: an intercom or coordination host for two-party transactions. All hosts must match a deployment you trust.
The public example bases used in this site’s API documentation are https://mempool.lineage.to, https://storage.lineage.to, and https://miner.lineage.to (see the API overview).
Create or restore a wallet
Common patterns: init new (new seed), from seed (backup phrase), or from encrypted master key (device restore). The SDK returns a seed phrase and encrypted key material; store them with your app’s security model (secure enclave, OS keychain, or hardware, as appropriate).
Offline and limited modes
Some clients allow offline key generation. Network operations will fail until you call a network init with real hosts; that is intentional.
Next
See Send and receive and fetch_balance in the API reference to verify connectivity without a full wallet UI.