wallet

This library was generated with Nx.

Building

Run nx build wallet to build the library.

WalletConnect pairing

prepareWalletconnectPairingUri() starts one real provider pairing with the generic QR modal disabled and resolves only when that provider emits a usable display_uri. It rejects with WalletconnectPairingError on missing config, timeout, cancellation, connection failure, or an unavailable URI. Repeated calls reuse the same pending pairing.

prepareWalletconnectUri(), syncWalletconnectUri(), and getWalletconnectUri() retain their former optional-return behavior as deprecated aliases for one compatibility release. New code should use prepareWalletconnectPairingUri() and getWalletconnectPairingUri().

The Pockie fallback uses this URI and keeps the same provider alive for session approval. Do not create a separate AuthClient or SignClient to manufacture a deeplink URI. After approval, getProviderType() remains pockie for UI and reload identity, while getProviderTransportType() reports walletconnect for transport-specific behavior. Reload recovery restores an existing session silently and never starts a new pairing or opens a deeplink when the session is gone.

Lifecycle

Plain JavaScript consumers retain automatic initialization. Framework adapters that construct during render must pass deferInitialization: true, call initialize() after commit, and call destroy() during teardown. Initialization is idempotent; destruction invalidates pending restores and pairings and removes listeners owned by that Wallet generation without deleting an approved persisted WalletConnect session or shutting down Reown's process-wide Core. Only an explicit disconnect() is user logout and removes the peer session.

A restored WalletConnect session is accepted from SignClient storage even while the relay WebSocket is still reconnecting. If the provider's stored active chain has no approved account, the SDK selects an approved configured chain locally; it does not ask the wallet to switch networks during reload.