Skip to main content
The wallet client runs the user-facing actions (create, send, recover) against your backend. Approving happens on the user’s device; Meru completes the transfer and covers the fee.

Construct

Cross-device: always call status() first

The wallet key never leaves the device, so signing in on a new phone does not copy it. status() combines “does this user have a wallet?” with “does this device have its key?” and tells you the one right action.
On a second device, calling enroll() instead of recover() would start a separate wallet. Always branch on status().
  • Receiving works on any device right away — the wallet address is public.
  • Sending from a new device needs recover() once. It restores this device to the user’s existing wallet (same wallet, same address) through Meru’s recovery service, authorized by the user’s login.

Methods

Send

Logout

Remove the device’s key and clear the session. Losing the key is fine — the wallet is recoverable by signing in again.