Thanks for your feedback! The website has rough edges that need to be smoothed out I agree. What sign in method are you using?
If npub.cash reliable showed my balance I would be showing it off to everybody. But it mostly hangs when loading nostr:npub1mhcr4j594hsrnen594d7700n2t03n8gdx83zhxzculk6sh9nhwlq7uc226 
Man I am really sorry about that! Are you using nostore on iOS by any chance?
Copy that. Sometimes the signer connection can’t be established for some reason, resulting in „Loading…“
Yes it is. It’s available here: https://github.com/lightning-digital-entertainment/npubcash-website
However I am working on moving everything to a mono repo, so that frontend and backend can be built in one command
Looks good to me. Does it still appear offline to you?
Just thinking out lout: Amethyst could check the /claim endpoint of npub.cash periodically and send a mocked DM to the user with the token.
npub.cash already sends dm on payments. I am currently working on adding the token in those as well. Once thats done, users would receive ecash directly in their inboxes without clients doing anything
No lightning address? Use npub cash.
User sets any lightning address in profile? Auto-withdraw from npub cash to lightning address.
Npub cash needs to support auto withdraw for this to work, of course.
CC nostr:npub1mz3vx0ew9le6n48l9f2e8u745k0fzel6thksv0gwfxy3wanprcxq79mymx nostr:npub1mhcr4j594hsrnen594d7700n2t03n8gdx83zhxzculk6sh9nhwlq7uc226
Can you elaborate on the idea of auto-withdrawals? Right now this could already be done by client logic. Periodically call the APIs /claim with NIP-98 header to get eCash. Store them locally. If user want to send them elsewhere do a /melt with the Cashu mint.
I’ll write a short post about that idea today
With Cashu you do not need nip-47. You can use the npub.cash API to get a users token using NIP-98 and then use them to pay any invoice. You app can basically be a Cashu wallet under the hood
Now imagine npub.cash users could set a list of mints in their settings. Zaps would be automatically split between them to reduce custodial risks and there would be zero UX implication.
You are a genius 💜🧡🥜
nostr:note182cgc0h8ys7mp6rxqrnp80t9v6vp8hwgzwquj2clrwaxwzygwltszsuu04
Oh, so basically sending from it? Happy to help with that 💪
What do you mean exactly? Zaps seem to work fine on my side
Yes. Are you using a browser with strict local storage policies? Some browsers will wipe it quite regularly
Hey 👋🏻
Your private key will be encrypted and stored in you browsers cache. The key itself is only available in memory. That’s why you need to unlock it with your passphrase every time you open the website again.
E.g., a person posts a #Cashu token in a note but doesn't want anyone else to see it unless they have the password for that note
... or are there other ways to protect against the discoverability of Cashu tokens?
nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg
nostr:npub1mhcr4j594hsrnen594d7700n2t03n8gdx83zhxzculk6sh9nhwlq7uc226
There is NUT-11, pay to public key. That will let you lock tokens to public keys, so that there is no reason for obfuscation anymore.
But isn’t this the opposite of what you said above? New users can have a seamless experience with npub.cash, by setting their Lightning address to their npub.cash address. Clients could display the balance within their UI, no friction whatsoever
That’s a pretty neat idea, but also an edge case. The idea is to provide an address in the first place.
This could work, but npub.cash has to improve their claim screens for new lightning users. It's too complicated right now to claim the tokens. Maybe a partnership with nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgewaehxw309aex2mrp0yh8xmn0wf6zuum0vd5kzmp0qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0sjh66rd or other wallets can help.
Strongly agree! The webpage was meant as a POC. The idea is that apps and wallets implement the API directly. Amethyst users could use their npub.cash address absolutely seamlessly.
We are currently strengthening foundations, adding proper CI and testing etc. Once that’s done we will revisit the webpage, even though it would be best if apps implement it directly
Super happy to see the npub.cash repo move from our companies to the official CashuBTC GitHub organisation.
npub.cash is FOSS and for everyone. 💜📂
I am taking the weekend off 💜
Enjoy Madeira 🙏
GM and thanks for keeping the feedback loop alive 🙏
Getting your sats out is easy: go to https://npub.cash/claim, login with one of the support methods and claim wither directly to a Cashu wallet or paste a Lightning invoice.
You can alternatively use Cashu-address-CLI in your terminal