# ZEUS mobile wallet setup for Bitcoin and Lightning

> ZEUS is a self-custodial Bitcoin and Lightning wallet for Android and iOS that can manage remote LND or Core Lightning nodes. Its broad protocol support comes with substantial setup requirements and unfinished features.

**ZeusLN/zeus** — A mobile Bitcoin wallet fit for the gods. ⚡️ Est. 563345

- Repository: https://github.com/ZeusLN/zeus
- Website: https://ZeusLN.com
- Stars: 1,408 · Forks: 258
- Language: TypeScript
- License: NOASSERTION
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/zeusln-zeus

## Why ZEUS targets self-custodial mobile Bitcoin

ZEUS addresses a specific tension in Bitcoin wallet use: a phone should remain usable without requiring a full node to run continuously on the device. It combines a Bitcoin wallet with Lightning functionality and acts as a remote node manager for LND and Core Lightning. The README describes connections to LNDHub instances as well as direct control of remote nodes, so the intended audience includes people who already operate or can access compatible Lightning infrastructure.

The application supports Android and iOS and is written in TypeScript with React Native. It is Bitcoin only, self-custodial, and listed as requiring no KYC. Those properties make it relevant to users who place custody control ahead of account-based convenience. They also shift responsibility toward the operator. A self-custodial wallet does not by itself remove the need for safe storage, correct node authentication, encrypted local access, and an understanding of on-chain versus Lightning funds.

ZEUS also serves payment-oriented use cases beyond basic sends and receives. The README lists NFC requests and payments, Lightning addresses, LNURL operations, keysend, SegWit, Taproot, and Nostr Wallet Connect roles. It can act as a Nostr Wallet Connect service or client, and ZEUS Pay provides a self-custodial Lightning address. These are useful when a user wants one mobile interface across ordinary Bitcoin transactions, Lightning payments, and service integrations.

That breadth creates a meaningful adoption boundary. ZEUS is not merely a lightweight on-chain wallet. Its Lightning channel, routing, account, external signer, watch-only, and remote connection features assume a more deliberate setup. A user who only wants a simple receive address, or who cannot operate remote infrastructure, should not assume that installing the app removes the relevant operational work.

## How ZEUS separates the mobile app from Lightning nodes

Based on the repository layout, the React Native interface lives at the top level and under `components/`, `views/`, `hooks/`, `stores/`, and `models/`. Platform implementations are separated into `android/` and `ios/`. Bitcoin-facing and protocol-specific code also has dedicated areas, including `cashu-cdk/`, `ldknode/`, `lndmobile/`, `backends/`, and `proto/`. This structure is consistent with an application that can present one wallet while adapting its operations to different Lightning implementations.

The README explicitly names LND and Core Lightning as supported remote node types. It also lists LNDHub connections, Lightning Node Connect, Tor connections, watch-only accounts, and external signer support. The repository links remote node setup to `docs/RemoteConnections.md` and directs users to the ZEUS documentation site for current connection guides. The README does not expose connection fields, protocols, credentials, or a universal setup sequence for every node type, so those details cannot be inferred from the feature list.

Payment features follow several distinct data paths. On-chain functions include SegWit, Taproot, coin control, message signing, and batch transactions. Lightning functions include invoices, channels, routing reports, routing fees, MPP and AMP, keysend, LNURL, Lightning addresses, and ZEUS Pay. ZEUS therefore does not collapse all funds into one abstraction. Channel management, for example, affects Lightning node state rather than only a local wallet database.

Local protection is documented through PIN or passphrase encryption and a privacy mode that hides sensitive data. Tor support is available for connections, while Nostr Wallet Connect provides an additional integration route. These features expand the connection and security surface. They also make configuration errors more consequential, particularly when a node connection, external signer, watch-only account, or NWC service is added.

## Installing ZEUS for an Android development build

Existing users can obtain ZEUS from the application distribution links in the README. Android builds are listed on Google Play, F-Droid, and Zapstore. The README does not document a command-line installation procedure for a store release, and it does not specify device backup steps for that workflow. Developers can instead follow the native Android build sequence after installing Node.js and the React Native prerequisites.

The repository requires Node.js `^22.13`, `^24.3`, or `>= 26`, and `package.json` states the same engine constraint. If a USB device is used, the README first calls for Developer mode and USB debugging, followed by checking the connected device. Install JavaScript dependencies with the following command from the repository root:

```bash
yarn
```

This is not a lightweight dependency install because `package.json` defines a `postinstall` script that applies patches, runs `rn-nodeify`, fetches libraries, and invokes `pod-install`. The README does not describe every side effect of that script, so contributors should expect the native and fetched components to be involved rather than only installing packages from the registry.

Start the React Native development server with:

```bash
npx react-native start
```

With the emulator open or a phone connected, build and launch the Android application through:

```bash
npx react-native run-android
```

The command should build the native Android application and launch it on the selected target. The README does not document the first-launch onboarding sequence, account recovery flow, or exact node connection controls, so completing a payment requires the current ZEUS documentation rather than assumptions about the app screens.

## Running ZEUS on iOS after installing CocoaPods dependencies

The iOS path also starts from the native React Native environment. A developer needs Node.js, the platform dependencies described under React Native's "Building Projects with Native Code" instructions, and the dependencies installed through `yarn`. After dependency setup, the README directs contributors to install CocoaPods dependencies from the `ios` directory:

```bash
cd ios && pod install
```

This command runs from the repository context and enters the iOS project directory before invoking `pod install`. Unlike a release installed from the Apple App Store, this route requires Xcode and creates a local development build. The README gives no command for launching the iOS target from the terminal. Its documented final action is to open `ios/zeus.xcworkspace` in Xcode and select Run.

The distinction between `.xcworkspace` and the platform project matters because CocoaPods dependencies must be represented correctly in the workspace. The repository contains a dedicated `ios/` directory, and the README names this exact workspace path. No simulator model, deployment target, signing configuration, or device provisioning procedure appears in the README, so those items remain unconfirmed.

ZEUS exposes package aliases for running iOS and Android through `yarn ios`, `yarn ri`, `yarn android`, and `yarn ra`, as defined in `package.json`. The README's native setup sequence, however, uses `npx react-native` commands directly. Contributors should follow the README during initial environment setup and inspect `package.json` before relying on a shorter alias.

## ZEUS feature coverage and incomplete protocol work

The strongest part of ZEUS is its concentration of Lightning controls in a mobile application. The feature list includes channel management, routing reports, configurable routing fees, LNURL pay, withdraw, auth, and channel operations, plus MPP and AMP. Account support covers Lightning and on-chain accounts, while batch channel opens can help node operators prepare Lightning capacity. ZEUS can manage multiple Lightning nodes at once, which directly serves operators rather than casual payment users.

The wallet also includes useful receiving and automation features. A self-custodial Lightning address is available through ZEUS Pay, Nostr contacts can be imported, and ZEUS can participate in Nostr Wallet Connect as either a service or client. Point of Sale support includes a standalone mode and Square integration. NFC, fiat currency displays, multiple languages, and contact lists are also listed. These capabilities make the project broader than its core wallet and node-management description.

Not every roadmap item is complete. The README marks PayJoin and an advanced security center as unfinished with unchecked boxes. Users who require PayJoin cannot adopt it as a ZEUS capability based on this repository description. The unchecked security center also means that the feature list should not be read as a description of a centralized security-management implementation.

The repository identifies AGPLv3 licensing and points to `LICENSE` for details and exceptions. Repository metadata classifies the license as custom because the file includes exceptions not captured by GitHub's standard classification. Users who intend to modify, redistribute, embed, or operate ZEUS should inspect that file directly. The README does not explain the scope of each exception, so no broad conclusion about licensing consequences can be drawn from the AGPL label alone.

## ZEUS maintenance, verification, and upgrade costs

ZEUS is not archived, and the last push was on 2026-10-17. Recent releases include `v13.2.3-alpha1`, `v13.2.3-rc1`, and `v13.2.3`, while `package.json` reports version `13.2.4-alpha`. These facts indicate recent repository and release work, but they do not document the amount of manual work involved in upgrading an installed wallet.

Mobile wallet upgrades require more care than replacing an ordinary read-only application. ZEUS supports encrypted PIN or passphrase access, on-chain accounts, Lightning accounts, external signers, and remote nodes. The README does not document migration behavior, backup compatibility, recovery testing, channel state handling during upgrades, or rollback procedures. It also does not describe whether a ZEUS upgrade can affect the remote LND or Core Lightning node. Those questions must be answered before an operational upgrade rather than inferred from the release cadence.

Release integrity has an additional project-specific mechanism. The README says that all releases and maintainer commits from October 20, 2021 onward are signed with key `AAC48DE8AB8DEE84`. It publishes that key in `PGP.txt` and on the ZeusLN.com website. The repository also documents reproducible builds in `docs/ReproducibleBuilds.md`. Contributors can verify commit signatures and review reproducible-build instructions before distributing a modified build.

The automated `verify` script in `package.json` runs tests, formatting checks, TypeScript compilation, and linting together. This is useful before contributing, but it does not replace device testing or Lightning-node validation. Neither the README nor `package.json` documents commands for backing up ZEUS, testing recovery, or validating Lightning invoices on a target device.

## Choosing ZEUS against a simpler wallet or node console

ZEUS's closest functional alternative is a separate workflow rather than a single competing product: use a basic Bitcoin wallet for on-chain activity and administer LND or Core Lightning through a desktop node interface. That approach separates payment simplicity from node operations. It may reduce the amount of Lightning configuration presented on a phone, but it requires moving between applications and does not provide ZEUS's unified NFC payments, LNURL workflow, channel controls, Lightning addresses, or Nostr Wallet Connect features.

Another practical alternative is an embedded or custodial Lightning account accessed through LNDHub. ZEUS documents LNDHub support, but connecting to an LNDHub instance changes the custody and administration model compared with controlling a personal remote node. The README does not document authentication or security trade-offs for each connection method, so the choice cannot be reduced to a blanket recommendation. Operators need to compare who controls the node, where credentials are stored, and which services can request payments.

ZEUS is therefore most convincing for users who already value Lightning node control but want a mobile interface. It is a weaker fit for someone seeking only a simple Bitcoin on-chain wallet, especially because PayJoin is unfinished and the advertised feature set includes remote node administration. It may also fit poorly for organizations that need documented backup, migration, rollback, or compliance processes, since the README does not cover those procedures.

## Conclusion

ZEUS fits mobile users who need Bitcoin, Lightning, LND, or Core Lightning control from Android or iOS, especially those prepared to configure remote nodes. It is less suitable for users wanting a zero-configuration custodial wallet or PayJoin support. Check the custom `LICENSE` file, confirm that your intended node connection is supported, and verify mobile build, backup, and recovery procedures before moving meaningful funds.

## FAQ

### Which platforms does the ZEUS mobile wallet support?

ZEUS supports Android and iOS. The README links Android builds through Google Play, F-Droid, and Zapstore, and an iOS build through the Apple App Store.

### Can ZEUS manage an LND or Core Lightning node?

Yes. ZEUS is documented as a remote node manager for LND and Core Lightning, with additional support for LNDHub instances and Lightning Node Connect.

### Does ZEUS support PayJoin?

Not at present according to the README. PayJoin appears as an unchecked feature, while Taproot is listed as supported.

### What Node.js versions does the ZEUS source build require?

The project accepts Node.js `^22.13`, `^24.3`, or `>= 26`. The README and `package.json` state the same engine constraints.

## Sources

- [Issues](https://github.com/ZeusLN/zeus/issues)
- [Project website](https://ZeusLN.com)
- [README](https://github.com/ZeusLN/zeus/blob/master/README.md)
- [Releases](https://github.com/ZeusLN/zeus/releases)
- [ZeusLN/zeus on GitHub](https://github.com/ZeusLN/zeus)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/zeusln-zeus