Thread - Nostr Hypermedia

Vitor Pamplona _@vitorpamplona.com 10 months ago

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.

Cameri🐦‍🔥

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. View quoted note →

View quoted note →

↑ Parent

Replies (9)

Logen logen@btcforplebs.com 10 months ago

This would be killer!

utxo the webmaster 🧑‍💻 _@utxo.one 10 months ago

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

maggabyr maggabyr@blink.sv 10 months ago

Woooow

Dante dante@zaps.lol 10 months ago

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 🙂👍

Vitor Pamplona

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. View quoted note →

View quoted note →

1 replies ↓

greenart7c3 10 months ago

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

1 replies ↓

Gzuuus gzuuus@nostree.me 10 months ago

Yes please 🙏

1 replies ↓

Vitor Pamplona _@vitorpamplona.com 10 months ago

I think we are already saving on both places :)

1 replies ↓

Gzuuus gzuuus@nostree.me 10 months ago

Little by little then suddenly 💪

DZC 10 months ago

💯 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.