Bitkit

• Name: Bitkit
• URL: https://bitkit.to/
• Category: mobile Lightning wallet / Blocktank-shaped self-custody app stack
• Tags: bitcoin-ecosystem
• Summary: Bitkit is Blocktank-shaped wallet software, not a generic Bitcoin mobile app. The app layer is real, but the useful read is the combination of bought inbound liquidity, Synonym-shaped defaults, and the hardware / Electrum escape hatches wrapped around them. The named operator boundary above that packaging now lives in synonym.
• What it does:
  • Ships as a self-custodial mobile wallet for Bitcoin onchain and Lightning payments
  • Splits the product across native iOS and Android apps that share a Rust core via FFI rather than a single thin cross-platform shell
  • Implements payment decoding and wallet flows around BOLT-11, BIP21, LNURL, Lightning Address invoicing, LNURL-auth, and LNURL withdraw / channel-request handling
  • Exposes Blocktank-backed Lightning Service Provider flows for order creation, channel opening and management, just-in-time channel creation, and gift-code redemption in the shared core
  • Supports Trezor hardware-wallet deep linking plus Electrum-backed account, address, UTXO, and transaction-signing workflows
  • Keeps explicit regtest, testnet, and mainnet build flavors for development, E2E testing, and production release work
• Key claims:
  • The official site positions Bitkit as a Bitcoin and Lightning wallet for Android and iOS and frames the product around self-custody rather than custodial convenience
  • The umbrella repository says Bitkit ships as native iOS and Android apps sharing a Rust core via FFI and points to the production repos for the app and core layers
  • The shared-core README shows scanner, LNURL, onchain, activity, Blocktank, and Trezor modules, which is much broader than a simple send / receive wallet surface
  • The core README explicitly lists support for BOLT-11, BIP21, LNURL, Lightning Address invoice generation, LNURL-auth, and Bitcoin address derivation across mainnet, testnet, and regtest
  • The Blocktank module documents LSP order creation, channel opening, just-in-time channel creation, and gift-code redemption, which is a strong signal that Bitkit packages Lightning liquidity operations into the wallet stack
  • The Trezor module documents deep-link integration plus Electrum-backed xpub, address, balance, UTXO, and signing flows, which reinforces that Bitkit is building a broader wallet-control-plane layer around the mobile app
• Whitepaper: No canonical Bitkit whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site plus the first-party umbrella, app, and shared-core repositories; see ../whitepapers/bitkit-primary-sources-2026-05-01.md.
• Sources:
  • https://bitkit.to/
  • https://github.com/synonymdev/bitkit
  • https://github.com/synonymdev/bitkit-android
  • https://github.com/synonymdev/bitkit-ios
  • https://github.com/synonymdev/bitkit-core

Internal linkages

• Direct liquidity backend in the stack: blocktank.
• Company / operator boundary above the wallet packaging: synonym.
• Stronger mobile-Lightning reads: phoenix-wallet and breez.

Protocol / company boundary

• Keep this note on the product surface: native mobile clients, the shared Rust core, Lightning and onchain payment parsing, Blocktank-backed liquidity hooks, and the hardware-wallet / Electrum escape hatches.
• Use synonym when the sharper question is who ships the binaries and support stack, packages the wallet into a broader company roadmap, and decides how tightly Bitkit stays coupled to adjacent Synonym-operated surfaces.
• That split matters because what can Bitkit do for a user? and which named operator keeps Bitkit packaged inside a wider Bitcoin/Lightning product shell? are related but not identical questions.

Control surface

• Practical leverage sits in Blocktank-dependent liquidity policy, wallet-core defaults around payment and channel handling, and how much of the stack stays tied to Synonym-shaped services versus user-chosen hardware and Electrum infrastructure.

• The product note is still useful because the mobile-wallet and payment-handling mechanics are specific enough to stand on their own.

• For the broader release, docs, and product-packaging shell above those mechanics, read synonym.

• Last reviewed: 2026-08-12 UTC