Users should to be able to set more than one Lightning address to receive zaps on their profile so if their main is down they have others as fallback.
nostr:note16alqjh6f6fvfds3mhf6srvg7dkl5xuucft4exs75scrsgtqj5fxsjd2xs0
Discussion
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug wdyt? Backup ln address field and on exception try with the (hidden?) backup address
Careful, you're going to unleash the beast that is money management 😂
My coinos was down yesterday, but good to go last night. I agree tho. I zap out of nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg and zaps are received in Coinos, unless I designate the address for someone to zap into my Primal, Strike, Aqua, or Coinos wallets.
Payment preferences is an unexplored thing in nostr
Seems so simple. Even a nip-51 list of addresses could do.
Yes, but I think a it should consider different options, not just lightning, so you create different list for every payment method? I remember nostr:nprofile1qqspdudqzqx5ellme3prp68qus5se3vynsddcexkv5la5p7qxxcswjcaxd3rp porpusing something using "w" tags in type 0, it was an interesting approach, but couldn't find the related conversation, maybe he can share some thoughts on this.
That could be easily solved by modifying the lud16 to specify a list of addresses.
This could be an option, then we can have different labels for different methods, lets say lud16, bolt12, cashureq, btc, all of these are arrays that clients can iterate on to find a working payment option.
Multiple zap addresses? 🤔 I think this is a great idea. Less centralization is good. And might help lightning nodes find more paths if multiple addresses are available.
Yup, this should be thinkering long time ago.
I have only general Idea how lightning works under the hood and this fallback addresses should be implemented on the protocol level.
