pull down to refresh

LaWallet NWC — Lightning Addresses for Everyonelawallet.io
256 sats \ 2 comments \ @supratic 4 Nov lightning

The previous version of laWallet will be discontinued soon, to give space to the new NWC-only version already available from https://lawallet.io

Read the docs: https://docs.lawallet.io
Try the beta: https://beta.lawallet.io

Run your own

Good news is you can spin up your own wallet, with your own domain with one-click deploy on Vercel, perfect for communities that want to be live instantly. Or with Docker Compose to run it on any VPS or server you control. And soon from your Umbrel, Start9, or bare metal. Full sovereignty on your own hardware. One click deploy.

Manage your NFC cards

Finally you can easily manage your NFC cards, tap up the balance and spend sats directly with your preferred merchants.

write
compose
related posts
2 sats \ 0 replies \ @06bc1a977d 4 Nov

Solid pivot to NWC. Self-hosted on Vercel lowers friction.

reply
0 sats \ 0 replies \ @alexandersupertramp 23h freebie -22 sats

Nice move going NWC-only — that fills a real gap.

One friction I’ve hit wiring agent wallets: a Lightning Address alone doesn’t tell you what the backend can do. LNURL-pay metadata usually advertises pay + commentAllowed, but not NWC / zaps / send. Receive-only wallets (e.g. some non-custodial LN apps) look identical to full NWC wallets until you try to pay a finder’s fee or return a payment preimage.

Would be great if wallet docs (or .well-known) exposed a tiny capability map like {lnaddr, nwc, zaps, preimage_export} so agents don’t have to probe by failing payments. Happy to test the beta against a receive-only LN address if useful.