Community

Wallets / Products

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.

Wallet Product Map visual
Wallets Products Value, permission, custody and proof before the next payment.
Wallets751 wordsProducts

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.

Useful next pages

Back to Wallets
A digital finance dashboard for wallet permissions, invoices and payment state.
People discussing self-custody and wallet decisions in a finance setting.
A team table where payment permissions and custody decisions become concrete.
Digital asset community energy around Bitcoin value movement.
An open doorway through technical diagrams for portable wallet access.

The market is splitting by permission shape

The wallet shelf is no longer a simple list of places to store sats. It is becoming a map of permission shapes. One product gives you a Lightning address and a friendly hosted balance. Another gives you a hub that can expose scoped NWC connections. Another lets a mobile app control your own node. Another is an operator backend for many wallets. Another handles bearer ecash. Another is just a thin tool that uses a NWC secret for one job. When you compare them alphabetically, the market looks crowded. When you compare the permission shape, it starts to make sense.

NWC's own app directory is useful because it shows the breadth: social clients, streaming apps, wallet tools, Boardwalk Cash, Wavlake, Zapple Pay, Primal, Amethyst, noStrudel and other products can all meet the same wallet-connection idea from different angles. Alby Hub turns that idea into a daily service layer. ZEUS anchors the node-control side. LNbits anchors the modular operator side. Awesome Cashu shows a separate ecash field with mobile wallets, web wallets, mints, libraries and NIP-60/61 support. These are different economies of trust, not one product category wearing different logos.

Alby, ZEUS, LNbits and Cashu are four archetypes

Alby is the archetype for approachable connection management. Its strongest editorial lesson is that wallet UX can expose permissions without turning the page into a sysadmin manual. Connection names, budgets, expirations and app pairing are human features. ZEUS is the archetype for serious mobile Lightning control. It speaks to people who want a wallet in the hand and a node behind it, with the complexity that comes with that choice. LNbits is the archetype for operators and communities: one backend, extensions, APIs, point-of-sale flows and experimental surfaces. Cashu is the archetype for cash-like small value: mint trust, proofs, wallet state and privacy tradeoffs rather than invoice-only thinking.

Most wallet products in the Nostr archive can be read as a variation on those archetypes. Coinos and Primal simplify receiving for social users. BitBanana and ZEUS speak to node-control instincts. Minibits, Cashu.me and Boardwalk Cash pull you into ecash. Zapple Pay, Vortex, Nostr Pay and similar tools show the thin-app side of NWC, where the core question is not custody but how safely a single app can ask a wallet to act. The product map gets more useful when each profile says which archetype it belongs to and what it borrows from the others.

Directories are starting points, not verdicts

A directory can tell you that a wallet exists. It cannot tell you whether you should trust it with meaningful money today. For that you need source trails: official site, documentation, repository activity, issue history, app-store records, NIP support, custody language, fee disclosure, recovery language and live behavior. A small project can be technically sharp and operationally fragile. A polished product can be convenient while hiding tradeoffs. An old reference implementation can be valuable historically while no longer being the active path. The original Alby NWC repository is a good example: it points you toward Alby Hub as the newer focus, which is precisely the kind of source context a product map should preserve.

So use the shelf in two passes. First, find the product by the job you want: receive zaps, pay from a client, run a node, operate a community wallet, test Cashu, build an app, sell something or stream. Second, read the trust boundary. Who has the money? Who has the permission? Who has the server? Who has the relay dependency? Who has the recovery story? If a product profile cannot answer those questions, the right next move is not rejection. It is a smaller test.

What a great wallet profile should do

A strong profile should feel like a reporter sat with the product and followed the money. It should tell you what the wallet is for, what it is not for, which NIPs matter, which source trail was checked, what can be tested safely and where the product might fail. It should not flatten Alby, ZEUS, LNbits, Coinos, Cashu.me, Minibits and Primal into one paragraph of interchangeable optimism. The Nostr wallet ecosystem is more interesting than that. Its best products are not trying to be one universal wallet. They are trying to make one trust boundary livable.