BlueWallet

• Name: BlueWallet
• URL: https://bluewallet.io/about/
• Category: bitcoin wallet operator collective / self-custody release-and-support boundary / mobile wallet and optional node-connectivity control plane
• Tags: bitcoin-ecosystem
• Summary: BlueWallet clears the bar for an entity note even though the official site describes it as a collective of developers and designers rather than foregrounding a formal corporate shell. The useful question is not only what can the wallet do? but who publishes the mobile releases, curates the docs and contribution path, steers private-notification and own-node defaults, and keeps the BlueWallet / LNDhub operating story coherent for users and small node operators? That practical authority sits with the BlueWallet operator boundary more cleanly than with a neutral wallet label alone.
• What it does:
  • Operates BlueWallet as an open-source Bitcoin and Lightning wallet for iOS and Android with self-custodial key handling
  • Maintains the official website, feature pages, about page, community / contribution surface, and public contact path for the wallet ecosystem
  • Packages watch-only wallets, PSBT and hardware-wallet workflows, own-node connectivity, and optional Lightning account flows tied to LNDhub-backed nodes
  • Publishes and maintains the public GitHub organization that holds the main wallet repo plus adjacent site and support tooling repositories
  • Shapes how users encounter wallet updates, notifications, contribution workflow, and self-hosted-node guidance rather than leaving those flows to a neutral protocol body
• Key claims:
  • The official about page says BlueWallet is a collective of developers and designers focused on self-sovereignty, personal property, security, and privacy, which is the clearest first-party statement that there is a named operator boundary above the wallet code itself
  • The homepage and README both say private keys never leave the device and frame BlueWallet as a Bitcoin and Lightning wallet for iOS and Android, which matters because the release and distribution shell still sits with the BlueWallet maintainers even when custody stays local
  • The features page says BlueWallet supports push notifications, multiple encrypted storages, hardware wallets, PSBT workflows, and plugging into a user’s own Bitcoin node through EPS, ElectrumX, or Electrs, showing that the maintainers decide which operational-security paths stay polished and easy
  • The Lightning page says BlueWallet can connect to a user’s own node and uses LNDhub to power that connection for family wallets, small communities, or groups running their own nodes, which makes the operator boundary relevant beyond a simple single-user mobile wallet app
  • The community surface says BlueWallet is built in public by a community, links contribution and donation paths, and highlights product-release posts such as BlueWallet v8.0.1 is Out: Liquid Glass, Private Notifications and More, which is useful evidence that the named maintainers shape release cadence and user-facing trust signals over time
  • The public GitHub organization exposes not only the main wallet repository but also website and related support repos, reinforcing that BlueWallet is an active operator-maintained stack rather than just a static app binary
• Whitepaper: No classic standalone BlueWallet company whitepaper is the point here. The strongest current primary materials are the official homepage, about page, features and Lightning pages, the community surface, the public GitHub organization, and the existing source bundle in ../whitepapers/bluewallet-primary-sources-2026-05-01.md updated by the live primary pages cited below.
• Sources:
  • https://bluewallet.io/
  • https://bluewallet.io/about/
  • https://bluewallet.io/features/
  • https://bluewallet.io/lightning/
  • https://bluewallet.io/watch-only/
  • https://github.com/BlueWallet
  • https://raw.githubusercontent.com/BlueWallet/BlueWallet/master/README.md

Internal linkages

• Project-layer note: bluewallet.
• Useful adjacent company reads where operator workflow shapes self-custody practice: cake-labs, foundation-devices, and onekey.
• Reusable lens: even open-source wallets can justify an entity note when release stewardship, notification plumbing, community workflow, and node-connectivity guidance sit with one named operator group.

Protocol / company boundary

• bluewallet should stay focused on the product surface: watch-only coordination, PSBT and hardware-wallet handling, self-hosted node connectivity, and optional Lightning access through LNDhub-backed setups.
• This entity note is for the operator collective above that product surface: release cadence, app-store and GitHub distribution, notification and community workflow, documentation stewardship, and the narrative that makes BlueWallet feel like the default front end for certain self-hosted Bitcoin and Lightning setups.
• That split matters because the dependency users inherit is not only a wallet with these features; it is also the BlueWallet maintainers' release, support, and infrastructure choices around those features.

Control surface

• Practical leverage sits in release publication, app-store and GitHub distribution, push-notification posture, documentation and contribution workflow, own-node and LNDhub guidance, and the specific wallet and hardware-signer flows BlueWallet keeps easy for users.

• Even when keys stay on-device, the maintainers still shape which privacy and self-hosting practices are normalized, how quickly wallet changes reach users, and which support or community surfaces people trust when something breaks.

• Read BlueWallet as an operator collective around a serious Bitcoin wallet-control-plane product, not as a neutral protocol primitive and not only as a mobile-app brand.

• Last reviewed: 2026-08-10 UTC