I am currently running an http server on the clearnet and want to provide lightning addresses to wallets that are sitting behind tor.
From my understanding I should just be able to return a valid LNURL/lnurl-p json blob to the client and that should allow the client to finish the rest of the process.
In my testing though (using zeusln), it seems like the client side doesn't change the connection to a tor connection to hit the callback address.
I am wondering if this is a client side issue, or if this is unsupported as per the spec.
For a bit more background I am running multiple wallets using lnbits to generate different lnurlp links for each. Each user has their own lnurlp json return, and the client side just gets the json from the GET request to the ${domain}/.well-known/lnurlp/${user}. These are all properly formatted and can be used when not referenced via my lightning address.
Wondering if this setup is "allowed" per say.
I am currently running an http server on the clearnet and want to provide lightning addresses to wallets that are sitting behind tor.
From my understanding I should just be able to return a valid LNURL/lnurl-p json blob to the client and that should allow the client to finish the rest of the process.
In my testing though (using zeusln), it seems like the client side doesn't change the connection to a tor connection to hit the callback address.
I am wondering if this is a client side issue, or if this is unsupported as per the spec.
For a bit more background I am running multiple wallets using lnbits to generate different lnurlp links for each. Each user has their own lnurlp json return, and the client side just gets the json from the GET request to the
${domain}/.well-known/lnurlp/${user}. These are all properly formatted and can be used when not referenced via my lightning address.