Summary: BitBanana is a small Android remote for someone else’s Lightning stack, not a wallet stack of its own. That is the point. It puts channels, peers, fees, watchtowers, and ordinary send/receive flows on a phone while leaving authority in LND, Core Lightning, Nostr Wallet Connect, or LndHub. Useful little tool; wrong note to treat as wallet infrastructure.
What it does:
Connects an Android client to remote Lightning backends including LND, Core Lightning, Nostr Wallet Connect, and LndHub
Lets users handle both routine wallet actions and operator tasks such as channel management, peer management, routing-fee changes, watchtowers, and multiple-node control
Supports Lightning Address, keysend, LNURL, NFC, Taproot, and Core Lightning Bolt 12 flows inside the same mobile control surface
Emphasizes operator privacy and verification through Tor, stealth mode, emergency access controls, balance masking, coin control, self-hosted providers, and reproducible releases
Key claims:
The homepage calls BitBanana a “pocket sized remote control for your node” and stresses that it is 100% self-custodial with zero data collection
The docs homepage says BitBanana is not a classical Bitcoin Lightning wallet and is better understood as a remote control for a personal Lightning node
The README describes it as a native Android app for node operators rather than a wallet on its own
The official materials consistently list LND, Core Lightning, Nostr Wallet Connect, and LndHub support, which makes clear that BitBanana is a frontend over existing backends rather than a closed wallet system
The project publishes reproducibility guidance and explicit open-source setup material, which matters because the app is meant to hold real node authority on a phone
Whitepaper: No canonical standalone BitBanana whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, docs, GitHub README, and reproducibility documentation; see ../whitepapers/bitbanana-primary-sources-2026-05-02.md.