lnproxy on Nostr: This is a great idea: ...
This is a great idea:
nevent1qqsxxy3mejv29m8dhf9tahyehge2mc55edgdd2rtcznzx2px7gfghkgprpmhxue69uhkummnw3ezuendwsh8w6t69e3xj730qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg4waehxw309ahx7um5wghx77r5wghxgetk9uq32amnwvaz7tmjv4kxz7fwdehhxarj9e3xwtcy3wvvl
I've been thinking about adding zap support for https://github.com/lnproxy/lnproxy-address but I've come to the conclusions that the use case doesn't fit.
I would recommend receiving zaps to a custodian then, when your balance is large enough to care, withdrawing to your own node through an lnproxy relay (there's more than one now!). If the payment fails, you can up the routing budget and try again, but the people sending you tips don't have to deal with the issues associated with better privacy.
If custodians accepted an automatic redirect, then you could simply give them an lnproxy wrapped invoice to send funds to and keep your node pub key private from your custodian.
nevent1qqsxxy3mejv29m8dhf9tahyehge2mc55edgdd2rtcznzx2px7gfghkgprpmhxue69uhkummnw3ezuendwsh8w6t69e3xj730qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg4waehxw309ahx7um5wghx77r5wghxgetk9uq32amnwvaz7tmjv4kxz7fwdehhxarj9e3xwtcy3wvvl
I've been thinking about adding zap support for https://github.com/lnproxy/lnproxy-address but I've come to the conclusions that the use case doesn't fit.
I would recommend receiving zaps to a custodian then, when your balance is large enough to care, withdrawing to your own node through an lnproxy relay (there's more than one now!). If the payment fails, you can up the routing budget and try again, but the people sending you tips don't have to deal with the issues associated with better privacy.
If custodians accepted an automatic redirect, then you could simply give them an lnproxy wrapped invoice to send funds to and keep your node pub key private from your custodian.