Wallet Product Map
The Nostr wallet market makes more sense when you group products by the job: daily wallet, NWC service, node remote, Cashu wallet, merchant surface, creator payment tool or developer building block.
Start with the job, not the alphabet
A wallet directory becomes useless when every product is listed with equal weight. Alby, ZEUS, LNbits, Coinos, Cashu.me, Minibits, BitBanana, Electrum, Primal Wallet, Rizful, Vortex and Zap Land are not interchangeable. Some are wallets. Some are wallet services. Some are remote controls. Some are commerce tools. Some are developer experiments. Some are mostly important because they show a pattern other products will copy.
A better map starts with the job. Do you want to receive zaps? Pay from a Nostr client? Run your own Lightning node? Give apps limited spending permission? Accept merchant payments? Use ecash for small private transfers? Test a protocol? Once the job is clear, the product shelf stops being noise.
Alby is the onboarding family
Alby is not one thing. Alby Account, Alby Extension, Alby Hub and Alby Go form a family around Lightning addresses, app connections, browser payments, self-hosted or hosted wallet services and daily Nostr payments. Alby matters because it keeps showing up where normal people first meet zaps and NWC.
Alby Extension made browser-based Lightning and WebLN feel ordinary. Alby Hub shifted the center toward a wallet service you can run or host. Alby Go gives that hub a phone surface. Alby Account adds Lightning address, Nostr identity, payment notifications and connected app flows. Together, they explain why wallet UX is not only about holding sats. It is about connecting the right app to the right payment authority.
ZEUS, BitBanana and Electrum are control surfaces
ZEUS and BitBanana are useful when you care about node connection and serious Lightning operations. ZEUS can manage LND or Core Lightning, connect over Tor, expose NWC behavior, handle LNURL and serve as a point-of-sale style wallet. BitBanana is an Android remote for Lightning backends with NWC in the orbit.
Electrum sits differently. It is a mature Bitcoin wallet that uses Nostr where relay transport helps wallet coordination, remote control or PSBT-style collaboration. It is not a social zap client, but it reminds you that Nostr can be useful beyond feeds.
LNbits and Coinos are operator and merchant surfaces
LNbits is the modular operator stack. It is valuable for people who want many wallets, extensions and API-controlled flows from one backend. In Nostr terms, it can be the payment engine behind community tools, point-of-sale systems, zap experiments and NWC services.
Coinos is more merchant-friendly. It combines wallet account, Lightning address, payment page, point of sale and Nostr profile ideas in a web surface. If you are reading from the commerce side, Coinos shows how Nostr payments become a counter, not only a social button.
Cashu wallets are a different category
Cashu.me, Minibits and Boardwalk Cash belong in their own lane because ecash changes the mental model. You are no longer only asking which Lightning wallet pays an invoice. You are asking which mint issued the token, where proofs live, how tokens are backed up, how Lightning deposits and redemptions work and how Nostr wallet state or Nutzaps enter the flow.
The attraction is strong: tiny payments can feel closer to handing over cash. The warning is also strong: the mint and wallet state matter. Treat Cashu wallets as a promising cash-like layer, not as a generic replacement for every Bitcoin wallet.
Smaller NWC tools show where the market is going
Avocadough, Brick Wallet, bullishNWC, Nostr Pay, Rizful, Sparky Hub, Vortex and Zap Land are useful because they show the shape of NWC as a market. Some are polished enough for daily experiments. Some are small interfaces around a connection string. Some are prototypes. All of them point to the same product question: what if any app could ask a wallet for a limited action without becoming the wallet?
These tools should be read with patience. A small project can be brilliant and fragile at the same time. Open the source when possible, test with tiny amounts and do not confuse protocol excitement with production readiness.
How to use the product shelf on Crays
Use the product shelf visually first. Logos help you find the name you remember. Then open the profile for the specific product. If the product asks you to connect money, follow the NWC, zaps, custody or Cashu article beside it. If you need implementation detail, open the protocol and source links at the end of the article.
The goal is not to make every wallet look equal. The goal is to make the first comparison honest enough that you know which product deserves your next fifteen minutes.
Sources worth opening
Open these when you want the specification, product documentation or implementation trail behind the article.
