Muun

• Name: Muun
• URL: https://muun.com/
• Category: recovery-heavy Bitcoin wallet / one-balance Lightning payment abstraction
• Tags: bitcoin-ecosystem
• Summary: Muun is still worth keeping as the product-layer note because the wallet surface is real: one-balance Bitcoin-and-Lightning abstraction, 2-of-2 multisig recovery, fee-estimation behavior, and the software layer that hides the rail split. But the named operator boundary around official app-store distribution, recovery-ceremony packaging, privacy policy, telemetry disclosures, and the canonical official wallet claim now lives separately in muun.
• What it does:
  • Provides a self-custodial mobile wallet for Bitcoin and Lightning payments on iOS and Android
  • Presents on-chain and Lightning spending through a single-balance wallet UX while emphasizing low-fee instant payments on Lightning
  • Uses a 2-of-2 multisig model in which the phone holds one key and the user’s Emergency Kit contains both keys needed for recovery
  • Offers backup and recovery paths such as a Cold Recovery Code and multi-factor recovery, plus a separate open-source recovery tool for moving funds out of a Muun account
  • Publishes first-party Android, iOS, libwallet, and recovery-tool repositories through the Muun GitHub organization
• Key claims:
  • The homepage says Muun is a self-custodial wallet for bitcoin and lightning and emphasizes a single-balance UX for on-chain and off-chain payments
  • The site’s product copy says Muun’s mempool-based estimator is designed to get transactions confirmed quickly without overpaying fees, which is a useful signal that fee management is part of the core product surface rather than a hidden implementation detail
  • The site also says Muun is a 2-of-2 multisignature wallet, that the Emergency Kit contains both keys while the phone contains only one, and that this is part of how the wallet handles phone compromise risk
  • The Android and iOS repository READMEs both describe Muun as a non-custodial 2-of-2 multisig wallet with a strong focus on security and ease of use, which helps confirm that the custody and signing model is a core design choice across clients
  • The recovery-tool README is especially high-signal because it explicitly says users can transfer funds out of a Muun account with no collaboration from Muun, reinforcing that the recovery path is intended to preserve user control even if the company is unavailable
  • The GitHub organization surface is notable because it exposes separate Android, iOS, shared wallet-logic, and recovery repos rather than only shipping a closed mobile app
• Whitepaper: No canonical Muun whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official homepage plus the Android, iOS, and recovery-tool repositories in the Muun GitHub organization; see ../whitepapers/muun-primary-sources-2026-05-01.md.
• Sources:
  • https://muun.com/
  • https://raw.githubusercontent.com/muun/apollo/master/README.md
  • https://raw.githubusercontent.com/muun/falcon/master/README.md
  • https://raw.githubusercontent.com/muun/recovery/master/README.md
  • https://github.com/muun

Internal linkages

• Company boundary for official binaries, recovery-ceremony packaging, privacy policy, and telemetry disclosures: muun.
• Strongest mobile-Lightning comparison point: phoenix-wallet.
• Recovery-heavy Bitcoin self-custody contrast: bitkey.

Protocol / company boundary

• Keep this note on the wallet and product surface: one-balance Bitcoin / Lightning UX, 2-of-2 multisig design, Emergency Kit and Recovery Code behavior, fee-estimation posture, and the practical software abstraction around rail choice.
• Use muun when the useful question is who ships the official binaries, defines the canonical recovery ceremony, publishes the privacy and telemetry perimeter, and controls the support / security-contact shell users actually inherit.
• That split matters because how does Muun work? and which named operator defines the official Muun trust boundary around that wallet? are related but not identical questions.

Control surface

• At the product layer, practical leverage still sits in recovery ceremony design, fee-estimation defaults, and the one-balance abstraction that decides when the app is really doing Lightning work versus falling back to plain onchain behavior.

• For the named operator boundary above that product layer — official binaries, recovery-tool stewardship, privacy and telemetry policy, and support workflow — read muun.

• Read Muun as a recovery-and-abstraction wallet note first, not as a neutral Lightning control-plane baseline and not as the whole company story by itself.

• Last reviewed: 2026-08-11 UTC