The same interface can hide different custody
A custodial Lightning wallet records a balance in the provider's system and the provider controls the channels and keys used to pay. It can offer simple recovery and immediate use, while retaining counterparty, account-freeze and service-failure risk. The balance is not self-custodial merely because payments use Lightning.
A self-custodial wallet controls keys and enforces channel claims for the user. Some wallets automate channel opening, liquidity and connectivity through a service provider while leaving spending keys with the user. Ask separately who can sign, who operates the node, and what happens if the company disappears.
Channel recovery is not an ordinary balance snapshot
A channel changes state after payments. Restoring an obsolete state as if it were current can conflict with the peer and protocol protections. Depending on the implementation, a seed restores on-chain keys while an additional channel backup, monitor data or recovery service is needed to locate peers and safely close channels.
A static channel backup is commonly a route to request channel closure and recover on-chain funds, not a copy that recreates the exact open channel for continued use. Details differ materially among wallets. Use only the documented backup method, keep it updated when required, and never assume twelve words cover every Lightning implementation.
- identify whether custody is delegated
- record the exact wallet-specific recovery method
- test recovery with a small balance before relying on it
A force-close is an on-chain safety path
If peers cannot cooperate, one side can publish a commitment transaction. Funds may then wait through protocol time locks, and pending HTLCs may require additional on-chain transactions. Confirmation speed and recovered amount can be affected by on-chain fees and channel details.
A force-close is not automatically theft or permanent loss; it is a slower, more expensive enforcement route. Keep the wallet available as its instructions require, update software cautiously and retain some on-chain bitcoin if the setup may need channel or fee management.
Treat Lightning as a spending wallet first
Start with an amount suitable for routine payments. Before paying, check the invoice amount, recipient context and expiry, and confirm whether the wallet shows routing or service fees. Receiving capacity can change even while the displayed total balance does not.
For larger reserves, compare the Lightning convenience with the recovery and availability model. A small custodial wallet can be a deliberate pocket-money choice; a larger self-custodial balance demands tested backups and an understanding of channel closure. Neither label removes operational risk.