Oddbean new post about login | logout Introducing npub.cash – everyone with an npub has a Lightning address, whether they know it or not! 🥜 Yours is <your_npub>@npub.cash 🥜 You can receive zaps on this address while you're offline – and redeem either your nuts either with your Cashu wallet or directly to your Lightning wallet of choice. No accounts. No sign-ups. Nostr-native. All you need is a Nostr signer browser extension like Alby. https://void.cat/d/F1e24ovNr38eTrEufaaEqE.webp
Here is the link: https://npub.cash – all this was coded by the remarkable @Egge
Osea que mi billetera sin que lo sepa es @negr0@npub.cash ????
This works with eNuts wallet?
This is a standalone service but we want to use it to integrate this functionality into other Cashu wallets! Stay tuned
Thank you @calle 👁️⚡👁️
Nice. But how will I be notified if someone sent SATs to it?
I get my notifications from Amethyst for example. The tool will also be able to send the nuts to you via DM.
Nice new domain name. FYI: <title> tag needs to be updated.
Tagging @Egge
alright, super cool ^^
Are these 2 websites the same website? https://cashu-address.com https://npub.cash
Yes
Team Cashu with so many wins. Can't wait for all this to be free of browser extensions that require email logins to use.
I built a CLI for anyone that doesn’t want to use a nip-07 provider. You can use it with node https://github.com/lightning-digital-entertainment/cashu-address-cli $ npx cashu-address-cli
Back then, we would just zap each other nuts for fun. Many of us didn’t even know we had nuts zapped to us. Often, the nut zaps were large enough to buy a car or house today. https://newfastuff.com/wp-content/uploads/2019/05/KORPM7j.png
Just tested sending to mynpub.npub.cash and didn't received.
@npub, not .npub
Sent a few sats to @Ronin@npub.cash and it went through on my end
Thanks but also didn't received. In my test it also went through in WoS, but didn't received nothing in my minibits wallet neither in my DMs.
It's not going to ur Minibits wallet. Gotta go to https://npub.cash/ and claim there
Wow! nostr:nevent1qqsq20d0fd6rqhlx4g7dqr8cnknp73qcmc968t2fscufh2hvwaljk8gpzfmhxue69uhk7enxvd5xz6tw9ec82cszypgdjn7zmpvqc6ptqud9gtutrcc6yq9s2z96h9dr80hss4wl9qwkxqcyqqqqqqgrhkhg3
But it's not twitter, so the bluechecks think nostr ngmi.
How does this compare (pros/cons) to a custodial wallet like Alby?
I like Alby, but it has more friction because you need an invite code now.
Testing. Please send 10 sats to the following address. @₿logging₿itcoin@npub.cash nostr:nevent1qqsq20d0fd6rqhlx4g7dqr8cnknp73qcmc968t2fscufh2hvwaljk8gpp4mhxue69uhkummn9ekx7mqzypgdjn7zmpvqc6ptqud9gtutrcc6yq9s2z96h9dr80hss4wl9qwkxqcyqqqqqqgfm8xhv
Since the interview you did with @petermccormack in #whatbitcoindid I felt like you are working on something very important but didn’t understand it completely back then. I guess it is much more mature now and a Part II is desperately needed.
Wen nostr-login @Egge ? 🙏
NIP-47? It doesn’t really help in this case because all cashu-address endpoints are NIP-98 protected, so you need to sign every request anyways. There is no other auth layer but nostr, which is what makes it so awesome IMO.
Nip46. If you are using nip07 then you can use nip46
Thought you were referring to this here: https://github.com/nostr-protocol/nips/pull/1042 Yeah I played around with NIP-46 and would love to build something with it for npub.cash soon. I think it would be easiest to implement in the CLI tool first.
Awesome! Let me know if it needs improvements to meet your needs
Working on this now 🤙 I read through the spec and I think it’s truely a missed opportunity that a remote signer response does not reference the requests ID. Did you add that to your implementation by any chance?
The spec is too badly written. The reply has format of
"content": "METHOD({id: <request-id>, result: <string>, error: <reason-string>})",
And the "result" field contains the method-specific payload.
The spec is being rewritten now with oauth-stuff added, hopefully it gets more readable. Yes I noticed. I was able to integrate it into my SDK and successfully requested my Cashu-address balance using nsec.app 👏 great work btw… However request-id is the random string from my request, not an event id right? I want to build a set of asynchronous functions that send a request and then resolve once I get the response, but from what I can tell there is no way to subscribe to ONLY the response, because the response does not include the requests e-tag, right?
Right, request-id is random string, not the request event id.
Not including the requests e-tag in the response is a huge missed opportunity IMO
You can chime in to this huge rewrite if you're in for some arguing 😉 https://github.com/nostr-protocol/nips/pull/1047
Ser, you're nuts
