BlueWallet

• Name: BlueWallet
• URL: https://bluewallet.io/
• Category: bitcoin wallet-control-plane / watch-only and PSBT hardware-wallet infrastructure / optional self-hosted Lightning-and-node connectivity stack
• Tags: bitcoin-ecosystem
• Summary: BlueWallet is mobile Bitcoin wallet-ops software, not a category anchor. The keepers are watch-only coordination, PSBT and hardware-wallet handling, multisig vaults, own-node connectivity, and optional LNDhub-based Lightning. For the named operator collective around releases, notifications, docs, and the broader BlueWallet / LNDhub packaging shell, use bluewallet.
• What it does:
  • Provides self-custodial Bitcoin and Lightning wallets for iOS and Android, with private keys staying on-device
  • Supports watch-only wallets by importing public addresses, xpubs, or ypubs so users can monitor cold storage without exposing spending keys
  • Exposes multisig vault and PSBT-centered hardware-wallet workflows, including explicit Coldcard and Cobo Vault support plus generic hardware-wallet mode
  • Lets users connect BlueWallet to their own Bitcoin full-node stack through Electrum Personal Server, ElectrumX, or Electrs instead of relying only on public infrastructure
  • Supports a Lightning setup tied to the user’s own node through LNDhub, which BlueWallet positions as useful for family wallets, small communities, or groups running their own node
  • Adds advanced wallet-operations features such as coin control, Payjoin, custom entropy, multiple encrypted storages, plausible deniability, and LNURL support
• Key claims:
  • The homepage says BlueWallet offers watch-only wallets, multisig vaults, Lightning wallets, notifications, plausible deniability, and transaction controls such as fee choice, bumping, cancelling, and batching
  • The README says BlueWallet is a “Thin Bitcoin Wallet” built with React Native and Electrum, that private keys never leave the device, and that Lightning, SegWit, Replace-By-Fee, encryption, and plausible deniability are all supported
  • The watch-only page says users can import a public address, xpub, or ypub and monitor cold storage or a paper wallet without touching the private key
  • The Lightning page says BlueWallet can connect to a user’s own node via LNDhub, with Lightning accounts associated to that node, and explicitly frames that setup as useful for families, communities, or groups running their own node
  • The features page says BlueWallet supports coin control, Payjoin, plugging into a user’s own Bitcoin full node through EPS / ElectrumX / Electrs, PSBT-based hardware-wallet workflows, multiple encrypted storages, LNURL, a Lightning browser, and a marketplace of Lightning-enabled apps
  • The support docs taxonomy shows BlueWallet maintains first-party guides for offline signing, Coldcard integrations, Cobo Vault, multisig vault creation and spending, and self-hosted LNDhub deployment on Ubuntu, macOS, and RaspiBolt
• Whitepaper: No canonical standalone BlueWallet whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, feature pages, support taxonomy, and public repository; see ../whitepapers/bluewallet-primary-sources-2026-05-01.md.
• Sources:
  • https://bluewallet.io/
  • https://bluewallet.io/features/
  • https://bluewallet.io/watch-only/
  • https://bluewallet.io/lightning/
  • https://bluewallet.io/docs/create-multisig-wallet/
  • https://raw.githubusercontent.com/BlueWallet/BlueWallet/master/README.md
  • https://github.com/BlueWallet/BlueWallet

Internal linkages

• Company / operator boundary for release stewardship, notification posture, docs, and the broader BlueWallet / LNDhub packaging shell: bluewallet.
• Best upward comparison points: sparrow-wallet and nunchuk.
• Keep BlueWallet pointed at those stronger wallet-ops and collaborative-custody reads rather than sideways across generic mobile-wallet peers.

Protocol / company boundary

• Keep this note on the product surface: watch-only coordination, PSBT and hardware-wallet handling, multisig vaults, self-hosted node connectivity, and optional Lightning access through LNDhub-backed setups.
• Use bluewallet when the sharper question is who publishes releases, curates docs and community workflow, steers private-notification and own-node guidance, and keeps the BlueWallet operator story coherent over time.
• That split matters because what features does BlueWallet expose? and which named operator keeps those features shipped, documented, and socially legible? are related but not identical questions.

Control surface

• At the product layer, practical leverage sits in which wallet modes BlueWallet keeps polished: watch-only coordination, PSBT and hardware-wallet flows, self-hosted node connectivity, and optional LNDhub-based Lightning.

• At the company layer, the practical leverage now sits with bluewallet through release publication, notification posture, documentation stewardship, and the contribution / support surfaces that shape how users actually live with the wallet.

• Read it as a thinner mobile wallet-control-plane product, not a broad Bitcoin wallet center.

• Last reviewed: 2026-08-10 UTC