What do some developers think? nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3qamnwvaz7tmwdaehgu3wd4hk6tcqyprqcf0xst760qet2tglytfay2e3wmvh9asdehpjztkceyh0s5r9cpvx58v nostr:nprofile1qyfhwue69uhhyetvv9uju6nzx56jucm0d5qs6amnwvaz7tmwdaejumr0dsqzqvhpsfmr23gwhv795lgjc8uw0v44z3pe4sg2vlh08k0an3wx3cj96l2ln2 nostr:nprofile1qyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99uqzqun2rcnpe3j8ge6ws2z789gm8wcnn056wu734n6fmjrgmwrp58q390rp63 nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq36amnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdshsqgxkruautvltgsqwlkhxz6d9c972hueyddg5xcw7jwwwfgdqmfh0fgtc0xaw nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnvv9hxgqpqr0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgsy67l5w nostr:nprofile1qyv8wumn8ghj76twvfhhstnjv4kxz7tn9ekxzmny9uq35amnwvaz7tms09exzmtfvshxv6tpw34xze3wvdhk6tcqyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6luf5tq

I asked chatgpt

The NOSTR protocol only allows one address, and I've noticed that sometimes some fail, and you have to keep changing addresses. My question is, is it possible to build or develop the option to have two lightning addresses in your profile so that when your primary wallet is zapped, it doesn't work; those zaps go to your secondary address.

I answer this:

What you're proposing makes a lot of sense from a redundancy and reliability perspective for receiving zaps. However, the NIP-05 protocol and the lud16 (Lightning address) field in Nostr's kind:0 are currently

OPTION 1: Lightning Address Proxy or "Redirector"

Create an intermediate service that acts as your official Lightning Address (e.g., zaps@proxy.negr0.dev) and receives the zaps, checking the status of your wallet(s):

If your primary wallet (e.g., Alby) is online, resend the invoice to it.

If that fails, generate the invoice in a secondary wallet (e.g., LNbits, Phoenix, WoS, etc.).

If you want, you can even rotate between multiple wallets at the same time.

This can be done as a small backend in Node.js, Python, or similar, acting as a compatible LNURLp server (as LNPay or LNbits do). It wouldn't be difficult to set up with the right libraries.

OPTION 2: Custom Nostr Client

Modify a client (e.g., a fork of Amethyst, Iris, Coracle, etc.) so that:

It allows you to define two lud16s, for example, in an extended metadata type:

{

"name": "negr0",

"lud16": "negr0@lawallet.ar",

"lud16_backup": "negr0@lnbits.com"

}

And the same client when zapping:

Try the primary client.

If it fails (timeout, or LNURLp server ERROR), try the secondary client.

This would require an informal proposal for a protocol extension and would be slower to adopt, but if you build your own client (or a plugin/patch to an existing one), it's viable.

OPCIÓN 3: Wallet multiproxy desde LNbits

LNbits te permite hacer extensiones. Podés hacer que tu dirección negr0@lnbits.com se encargue de gestionar redirección y fallback a otras wallets. Ideal para experimentar rápido.