Nostr Web Client

Would it possible to give users a way to define a backup/secondary receive wallet? Then if the primary receive wallet failed, incoming zaps could be sent to the secondary one. It’s easy enough to swap sending wallets when we have issues. But if our receiving wallet goes down like this we may not realize it for hours.

PABLOF7z 1y ago 💬 1

not with LN zaps; the zapper is set on the kind:0, so you can only have one

Reply to this note

Please Login to reply.

Discussion

hodlbod 1y ago 💬 2

You could have contradictory lud06/16 fields

PABLOF7z 1y ago

do you test both? I check for both but use only one 🤔

hodlbod 1y ago

Yeah, me too, but a smarter implementation could use the alternative as a fallback

corndalorian 1y ago 💬 1

So that would require a change to the kind:0 NIP to allow for a second/backup LN address? If so, then theoretically would it possible for a client to implement that? Or a fallback cashu wallet? Just thinking what would need to happen to even make it possible. Payments are fundamental to a lot of what happens on nostr. Whether custodial or self hosted, a wallet failure is more than just a nuisance, and it happens too often, regardless the wallet provider.

PABLOF7z 1y ago 💬 1

nutzaps fix this completely;

the expected use is to have many many mints (since the UX is much better when sending/receiving nutzaps within the same mint)

corndalorian 1y ago

I’m here for it 🥜🚀