Community

Wallets

Move value without handing over the wallet.

Wallets are where Nostr stops being only speech and starts moving money. Before you zap, sell, stream, vote, unlock or connect an app, you need to know who controls funds, which permission is granted, where the receipt appears and how you can leave cleanly.

Start where value can move

Read the wallet by permission, not by logo.

A Nostr wallet decision is never just a button. It is custody, a payment rail, a wallet service, a relay, a budget, a receipt, a mint or a recovery path. Start with the risk you are about to create, then open the product.

Wallet decisions around self-custody, permissions and payment flow
Connect without surrendering the wallet iconConnect without surrendering the walletNWC is the permission layer: the app can ask, the wallet can limit, and you should see the budget before money moves. Read zaps as public receipts iconRead zaps as public receiptsA zap ties a Lightning payment to a social action, but the receipt still needs validation and context. Separate custody from interface iconSeparate custody from interfaceA pretty wallet UI does not tell you who controls funds, backups, channels, mints or app permissions. Understand Cashu before treating it like Lightning iconUnderstand Cashu before treating it like LightningCashu changes privacy and UX, but mints, proofs, wallet state and Nutzaps have their own risk model. Find the product by job iconFind the product by jobAlby, ZEUS, LNbits, Coinos, Cashu wallets and NWC tools make sense only after you know the job. Keep permissions small iconKeep permissions smallSmall balances, scoped app connections, tested recovery and visible revocation keep experiments survivable. Know where Bitcoin enters the story iconKnow where Bitcoin enters the storyNostr is not the payment network. Bitcoin and Lightning move value; Nostr carries identity and context. Treat zap games as money games iconTreat zap games as money gamesGoals and leaderboards can fund real work, but they need plain rules before status swallows context.
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.

Follow the money path

The useful Wallets route starts before the payment.

Use this map when a client asks to connect, a zap appears, a Cashu token moves, a creator goal opens, or a wallet product looks simple enough that you might forget the risk underneath.

01The first wallet questionWho controls the funds, and what happens if the app, node, wallet service or mint disappears? 02The NWC momentWhen an app asks for a connection string, read the methods, budget, relay and revoke path before approving. 03The zap momentWhen money becomes visible in the feed, understand what the receipt proves and what it cannot prove. 04The ecash momentWhen Cashu enters the flow, ask about mints, proofs, backup and token custody. 05The product shelfUse product names after you know whether you need a daily wallet, node remote, wallet service or ecash wallet. 06The safety routineTest with tiny amounts, revoke old connections and never let a smooth flow hide recovery.
An open doorway through technical diagrams for portable wallet access.
Digital asset community energy around Bitcoin value movement.
A team table where payment permissions and custody decisions become concrete.
People discussing self-custody and wallet decisions in a finance setting.
A digital finance dashboard for wallet permissions, invoices and payment state.

Product shelves

Find the wallet by the job it does.

Favicons and app icons give you a fast visual entry. The profiles and articles explain custody, NWC, zaps, Cashu, node control, merchant use and developer context without hiding the source trail.

NWC Wallet Services

NWC Wallet Services

Wallet services and wallets that can sit behind app connections.
8
Alby Hub iconAlby Hub Bankify iconBankify Bitvora iconBitvora Cashu.me iconCashu.me Coinos iconCoinos LNbits iconLNbits Primal Wallet iconPrimal Wallet Zap Land iconZap Land

Wallet Interfaces

Wallet Interfaces

User-facing surfaces for sending, receiving, approving or managing wallet connections.
8
Alby Account iconAlby Account Alby Extension iconAlby Extension Alby Go iconAlby Go Avocadough iconAvocadough BitBanana iconBitBanana Brick Wallet iconBrick Wallet Nostr Pay iconNostr Pay ZEUS iconZEUS

Cashu and Ecash

Cashu and Ecash

Cash-like token wallets, mint tools and ecash references.
8
Cashu iconCashu Cashu.me iconCashu.me Minibits iconMinibits Boardwalk Cash iconBoardwalk Cash Cashu Redeem iconCashu Redeem Bankify iconBankify NIP-60 iconNIP-60 NIP-61 iconNIP-61

Commerce and Creator Payments

Commerce and Creator Payments

Payment products where wallet choice touches selling, streaming or creator support.
8
Flash Wallet iconFlash Wallet zap.stream iconzap.stream Zapplepay iconZapplepay ZapStore iconZapStore BuzzPay iconBuzzPay BTCPay Server iconBTCPay Server NakaPay iconNakaPay ZapPlanner iconZapPlanner

Developer Building Blocks

Developer Building Blocks

SDKs, specs and utilities behind app-to-wallet behavior.
8
NWC iconNWC Alby SDK iconAlby SDK Bitcoin Connect iconBitcoin Connect Cashu NUTs iconCashu NUTs LNURL iconLNURL Breez SDK iconBreez SDK LND iconLND Core Lightning iconCore Lightning
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.

Wallets are the permission layer of the Nostr economy.

The Wallets route is not just a payment directory. It is the place where a visitor learns what they are authorizing when a Nostr app starts moving value. A zap is a public signal. NWC is a scoped remote-control channel. Cashu is bearer ecash with mint trust. A Lightning address is a social money handle with an always-on service behind it. A product wallet can be a hosted account, node remote, operator backend, ecash wallet, app connector or all of those at once. The hub should help you name the boundary before the interface asks you to fund it.

The current source trail points to five anchors: NIP-47 for app-to-wallet permissions, NIP-57 for zaps, NIP-60 and NIP-61 for Cashu wallets and nutzaps, NIP-75 for fundraising goals and NIP-87 for ecash mint discoverability. Around those standards sit the products that make them livable: Alby Hub, ZEUS, LNbits, Coinos, Primal Wallet, Cashu.me, Minibits, Boardwalk Cash and smaller NWC tools. The useful hub does not crown one winner. It teaches you how to read the promise each product makes.

Read the wallet by failure mode.

A strong wallet page asks what happens when the happy path fails. If the relay drops an encrypted NWC request, can the app tell you that transport failed? If an invoice expires, does the UI separate timeout from insufficient budget? If a Cashu mint disappears, does the wallet explain what that means for proofs and redemption? If a hosted provider closes the account, can the user export or withdraw? If a creator goal is overfunded, missed or disputed, does the page say what the money now means? These are not pessimistic questions. They are the difference between a magazine article and a brochure.

This is also where Wallets connects to the rest of the archive. Privacy explains why key custody and metadata matter. Commerce explains why a zap is not automatically a purchase. Media explains why creators need payment language that fits the room. NIPs explain which event kind carries which promise. Apps explain the product surface. The Wallets hub sits in the middle because money makes every vague interface more expensive.

Payment map

Start with the next payment, then choose the tool.

If you are about to connect an app, open NWC. If you are reading a public tip, open zaps. If a Cashu token appears, open the ecash path. If you are choosing a product, use the product shelves after you know the custody model.

Read first

Product examples

Useful next