Cowrie Research

bitbanana-primary-sources-2026-05-02

3 min read

BitBanana primary sources — 2026-05-02

Project status in this pass

  • No canonical standalone whitepaper or litepaper surfaced.
  • The clearest current source of truth is BitBanana’s official site, docs, GitHub README, and reproducibility documentation.
  • The official materials consistently frame BitBanana as a remote-control layer for a user’s own Lightning node rather than as a standalone custodial wallet.

Primary-source snapshots

1) Homepage

  • URL: https://bitbanana.app/
  • Key excerpt:
    • The homepage says BitBanana is “100% Self-Custodial with ZERO data collection” and that the app is a “pocket sized remote control for your node.”
    • It lists remote connections to LND, Core Lightning, Nostr Wallet Connect, and LndHub, alongside channel, fee, peer, and watchtower management.
    • It also lists wallet functions such as onchain/offchain payments, Lightning Address, keysend, LNURL, NFC, and Taproot support, which suggests the app is an operational access layer on top of a user-controlled node.

2) Documentation homepage

  • URL: https://docs.bitbanana.app/
  • Key excerpt:
    • The docs explicitly say BitBanana “is not a classical bitcoin lightning wallet” and is “much more like a remote control for your personal lightning node.”
    • The page says the app combines the “full power and control of an always online lightning node with the flexibility of your mobile phone.”
    • That language is the clearest categorization clue in this pass.

3) GitHub README

  • URL: https://raw.githubusercontent.com/michaelWuensch/BitBanana/master/README.md
  • Key excerpt:
    • The README says BitBanana is a native Android app for node operators focused on user experience and ease of use.
    • It says the app is not a wallet on its own and instead works like a remote control that lets users use their node as a wallet wherever they go.
    • The features span remote backend support (LND, Core Lightning, Nostr Wallet Connect, LndHub), node operations (multiple nodes, peers, channels, routing fees, watchtowers), and wallet actions (onchain/offchain send/receive, keysend, Bolt 12 for Core Lightning, LNURL, NFC, transaction labels, and payment-path display).

4) Reproducibility documentation

  • URL: https://raw.githubusercontent.com/michaelWuensch/BitBanana/master/docs/REPRODUCE.md
  • Key excerpt:
    • The reproducibility docs explain that if a distributed app cannot be exactly reproduced from source, malicious code could be embedded and gain access to user data or funds.
    • The page then documents separate verification paths for Play Store versus GitHub/F-Droid releases.
    • This is a strong signal that BitBanana treats build verifiability as part of the product’s security model, not just as a developer nicety.

5) GitHub repository page

  • URL: https://github.com/michaelWuensch/BitBanana
  • Key excerpt:
    • The repo overview repeats the project tagline “Superpowers for you and your bitcoin lightning node” and points users to public releases, docs, regtest guidance, reproducibility instructions, and issue tracking.
    • The page also repeats the self-custodial and zero-data-collection posture.
    • The repo surface reinforces that the project’s real operating stack lives in its open-source code and docs rather than in a proprietary hosted backend.

Working conclusion

BitBanana is best cataloged as mobile Lightning wallet-control-plane and node-operations infrastructure rather than as a simple wallet app. The decisive evidence in this pass was the repeated first-party framing that it is not a classical wallet but a remote control for a personal Lightning node, plus the concrete feature mix of backend interoperability, operational channel/fee/watchtower controls, privacy-heavy self-custody, and reproducible-release verification.

Graph View