Highly experimental Lightning address that will lead to loss of funds: <npub>@cashu.me

Replies (98)

Blink and BlueWallet fail due to invoice Metadata not matching description_hash (this is a known related problem)
Default avatar
Carlos 2 years ago
I think it relies on the privacy-invazive zap flow, meaning your LN tip leaves traces in nostr events of who sent the sats. Otherwise it wouldn't know the npub of the sender, e.g. who to send the DM to with the token.
Just lost 100 sats because I just sent it to the wrong lightning address, but the npub lightning address works great! 🤣
Default avatar
Carlos 2 years ago
AFAIK Blixt and Phoenix do the plain anonymous "pay to LN Address flow", which doesn't touch nostr.
brrbrr's avatar
brrbrr 2 years ago
i was able to claim that using enuts app. but not in nostr client (amethyst). try enuts.
How? We need self custody lightning wallets that can do roger@walletofsatoshi.com is so easy to transmit the address to receive funds, is this it?
Worked, flow was a bit odd. First tap of redeem button didn't show anything. Second tap gave an error (didn't record it). Third tap gave an already spent error. This was on amethyst client. Went to ln address set for zaps. Thought I thought I had to claim at cashu.me So overall seemed fine. Not sure why I didn't see confirmation message that it was redeemed in amethyst. But I believe that's the NOSTR client.
@calle see a couple small things on your end, not putting the empty routes array and missing the text/identifier item in your Metadata. Added a test in the library and it seems to work, will need to debug more.
I'm curious about the privacy implications here. Does this actually solve the custodial receive problem for people who run their own node but don't want to expose their router's IP to receive sats?
Default avatar
Carlos 2 years ago
Yes it solves that problem, but adds trust in the mint. You're not receiving sats per se, you're receiving cashu, which is redeemable to sats via the mint.
Right, so the redeem does not happen directly from ZEUS for example? It's still a manual process for each zap through a mint like cashu.me ? So is the most convenient method to receive/redeem via some cashu app? But still send zaps using a lightning wallet like ZEUS or Mutiny?
I wope up thinking about this exact idea, this is crazy. But what I was thinking is that nostr message metadata are public, so having all cashu payments come to your inbox might not be great, privacy wise. Is it possible to have 1 nostr npub that generates sub-npubs, like Bitcoin does with addresses? So the forwarder (cashu.me) would know the main pubkey but each payment coming to a different address.
Your npub is npub1cq47m26ft2xh8c33jtapvxstsdzgy86gg35prv0gzravvk6cfaysa9sukg. Send to npub1cq47m26ft2xh8c33jtapvxstsdzgy86gg35prv0gzravvk6cfaysa9sukg@cashu.me and check your messages
Here is the spec! It's just missing one previous request (/checkfees). The sendable amount is then token_amount-fee_reserve. If we had a full Cashu wallet in Amethyst, we could also get the overpaid fees back but unfortunately it won't work without the lib. Step by step! ☺️
This was one of those moments, where technology works so magically, that I start screaming uncontrollably, and the people next to me ask if I'm alright. It's not just that it works, but that you get a glimpse of what this technology might mean for humankind. View quoted note →