The same screen can hide different responsibilities
Two apps can both show a Lightning balance and a pay button while working very differently. One may represent money held by a service. Another may run a node on your phone. A third may control a node somewhere else. Start with where the spending authority lives, then consider convenience.
Write a one-sentence description of your setup before funding it. Include who holds the keys, which device needs to be available and what you would need after losing that device. If that sentence is difficult to write, spend more time with the project documentation.
A remote control is not the node
ZEUS supports several connection types, including remote LND and Core Lightning connections as well as local wallet options. When it controls a separate node, losing the phone does not mean the node itself has vanished. Conversely, saving the phone configuration is not a replacement for maintaining the node and its recovery material.
Treat connection credentials as sensitive. A QR code used to connect a wallet may grant capabilities, not merely identify a server. Before sending a screenshot for help, establish what it contains and redact anything that could authorise access.
An embedded wallet brings the node with you
Blixt describes itself as a Lightning node on the device, rather than a remote control for a home node. Its documentation distinguishes on-chain funds from channel funds and sets out specific backup and migration procedures. Read those procedures before treating a phone replacement like an ordinary app reinstall.
Do not run a casual recovery rehearsal by cloning an active Lightning wallet onto another device. Follow the implementation’s documented migration or disaster-recovery path. A generic phone backup is not evidence that channel state can safely be restored.
Backup instructions belong to the implementation
ZEUS documents different recovery paths even within one app. Embedded LND disaster recovery uses the seed and recovery data to force-close channels and recover on-chain funds; its separate planned migration flow can preserve live channels. LDK uses Versioned Storage Service for channel state. Identify the wallet mode and backup type before restoring, and never run two active copies.
Record the wallet mode, backup method and any server configuration required for recovery. Keep those notes separate from public troubleshooting messages. Review them after a major change or migration, rather than assuming a seed phrase makes every Lightning implementation interchangeable.
Usable balance is a practical question
ZEUS explains that its displayed Lightning balance can differ from sending capacity because channel reserves and channel status matter. A failed payment is not automatically a loss of funds. It can indicate routing, capacity, connectivity or fee-budget constraints.
Before paying, read the invoice amount, recipient information available in the wallet and the maximum fee. If a payment fails, inspect its status before trying again. Do not create a second payment while the first remains unresolved merely because the interface feels slow.
Choose for the next six months
Use a small working balance while learning. Test receiving as well as sending, because an app that pays successfully may still need a different arrangement to receive the amounts you expect. Observe what happens when the phone has been offline and when a payment cannot find a route.
Choose the setup whose maintenance you can explain and perform. Someone who enjoys running a node may value control over liquidity and connectivity. Someone else may prefer a managed experience and its stated dependencies. There is no benefit in adopting a more demanding configuration and then neglecting its backups.
- Name the custody model.
- Identify the exact wallet mode.
- Read the matching recovery procedure.
- Understand receiving and sending constraints.
- Recheck fees and service conditions at the point of use.
