Nostr Web Client

THE MONEY IS IN THE NOSTR!

👉 Create a new npub AND DOING NOTHING ELSE, no WoS, no nostr-wallet-connect pairing,... NOTHING

☑️ receive zaps

☑️ send zaps

☑️ and most importantly ACCESS MY WALLET FROM ANY CLIENT ON ANY DEVICE

these zaps are verifiable, way faster -- they are immediate (since the sending of the ecash is the zap, instead of waiting for a LN node to, maybe, publish a zap receipt)

Just like our contact lists follows us around, just like our profile data and our shitposts pops up in any nostr application, now so does our sats.

the money is in the nostr!

https://m.primal.net/JOgu.mp4

<old>cypherhoodlum 1y ago 💬 4

Wen this on NDK nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft?

Reply to this note

Please Login to reply.

Discussion

PABLOF7z 1y ago 💬 3

working on it right now

<old>cypherhoodlum 1y ago

Fantastic 😎

pailakapo 1y ago

the biggest hurdle for me for usability is the storage of the ecash tokens. Right now, if I delete the browser data on my phone I *may* be able to restore them.

Storing them on nostr is a huge UI win for me.

Wallets should be able to use this off-phone storage, and users should have this option to use this for all npub-protected ecash tokens.

Leito 1y ago 💬 2

Will it use the dm relays for the outbox model?

PABLOF7z 1y ago

No, it shouldn’t; dm relays might guard REQs behind AUTH which you don’t want for public zaps; for private zaps you might, yeah

Leito 1y ago

So it would just use the public inbox relays correct?

Five 1y ago

I've been thinking about this ALL day! Crazy stoked!

Will implement as soon as this ships.

ben 1y ago

code review: you can mutate a const or should that be var/let? 😅

nout 1y ago

Const means you can't replace the object pointer by anything else, but you can still modify the contents of the object.