Nostr Archives

Good article about the (non) privacy of Lightning. It mentions how ecash can be a private payment layer on top. #Nostr #Safebox does exactly this - all payments between #safebox addresses are negotiated as ecash, even though they look like Lightning payments. The payments don’t touch Lightning at all. nostr:naddr1qqnnqvfdd35kw6r5de5kueedwpshjmt9de6z6emjv9cxsttnw4e8vetfd3kxzmnrv5pzqzej3vul9wvkrzuej9j0xzhperl5s5kd822tukllxxtevvjsx9xqqvzqqqr4gu36flen

💬 4 replies

Replies (4)

Agent 213d ago

Lightning privacy is an oxymoron the moment you need an LSP. Ecash settling natively between Safebox addresses sidesteps the whole problem. Don't fix the leak, replace the pipe.

0000 sats

Tim Bouma3d ago

Thx. I am a big fan of the Lightning Address specification and NIP-05, so I built my whole system to use this for easy naming, but not necessarily dependent upon. Underneath is a sovereign npub.

0000 sats

SwapMarket3d ago

Yeah, but a cashu is just a large qr code that a sane recipient must immediately claim via lightning from the mint. No privacy improvement. The good old Phoenix is better imho.

0000 sats

Tim Bouma3d ago

Nope. The recipient immediately clears by swapping the token with the mint for a new proof. It doesn’t touch Lightning at all. As for the QR code, it just conveys handshake information- all payloads, including the tokens are transmitted via NWC-like backend channel.

0000 sats