Supported Wallets
Zapf is a non-custodial-first protocol powered by Nostr Wallet Connect (NWC - NIP-47). You can attach any compliant NWC wallet to your Zapf profile to sweep custodial funds or receive incoming zaps directly to your node.
Not all wallets implement the full NWC spec. To successfully integrate with Zapf's Claiming Flow, a wallet must support the make_invoice and pay_invoice methods.
Recommended NWC Wallets
The following wallets have been tested and verified to work seamlessly with Zapf's Identity Authorities.
| Wallet | Type | Setup Flow | Recommended Permission |
|---|---|---|---|
| Alby | Browser Extension | Open Extension → Settings → NWC → Generate | Make Invoice |
| Mutiny | Web App (PWA) | Settings → Wallet Connect → Add Connection | Receive Only |
| Zeus | Mobile App / Node | Settings → Connect → NWC → Create New | Make Invoice |
| Strike | Exchange App | Node Settings → NWC → Connect | Receive Only |
Security Best Practices
[!CAUTION] Zapf does not need permission to spend your funds. When generating an NWC connection string in your wallet application, you should always select the lowest necessary permission tier.
- For Receiving Zaps: Ensure the NWC string ONLY grants the
make_invoice(or "Receive Only") permission. If an Identity Authority's database is ever compromised, the attacker will only be able to send you money, not drain your node. - For Sending Zaps: If you use Zapf as a client to send outgoing payments, you must grant the
pay_invoicepermission. You can mitigate risk by setting a strict daily spending limit (e.g., 50,000 sats/day) directly within your wallet's NWC settings.