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.

nostr:nevent1qqsz04x0esc0s7ntkauh3p74gzd9fjleluzv4wghe3x562xchavgeycpz9mhxue69uhkummnw3ezuamfdejj7q3qqqqqqqyz0la2jjl752yv8h7wgs3v098mh9nztd4nr6gynaef6uqqxpqqqqqqz98f7w5

Reply to this note

Please Login to reply.

Discussion

This would be killer!

I think profile should have a nwc field, then we don't even need lnurl

Woooow

Aqui vai uma excelente ideia: Ter mais de um endereço para zaps caso um deles caia.

E melhor ainda se der para automatizar a troca de endereços quando um deles não responder 🙂👍

nostr:nevent1qqsdxd8s782e9h6ywmcd9vaezzns7lsa2fruaa8vlu3ys6gx2y4vs2spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygzxpsj7dqha57pjk5k37gkn6g4nzakewtmqmnwryyhd3jfwlpgxtspsgqqqqqqs7yq7xw

love it

One more reason for profile fields in tags instead of encoded json

Yes please 🙏

I think we are already saving on both places :)

Little by little then suddenly 💪

💯

And this could be combined with multiple way to receive zaps:

- lnurl address(es)

- bolt12 address(es)

- nutzaps

- etc

Zap clients could support several ways of zapping, with different priorities, ofc.