Stacker News Private Receive Option without the 10% Proxy Fee \ stacker news ~lightning

Hello Fellow Stackers,

As many of you know, Stacker News will be completely eliminating it's custodial lightning wallet soon. Prior to this change, Stacker News could serve as a 'poor man's' ln proxy as the sats would go to the Stacker News node, then Stacker News would create a new payment to your node (depending on your wallet settings). This was an awesome tool for us Plebs, but I totally understand that it was probably never the intent of Stacker News to serve this purpose ; more of an emergent behavior. So, I mourn it's loss but I am excited for the next phase of the Stacker News value for value experiment.

So, what does this mean for lightning node runners that want to receive sats sent to their Stacker News ln address or want to receive sats from Stacker News activity instead of cowboy credits ? Well, it means that now when you setup a receive option, the receiving node will be exposed when a zap is sent to your Stacker News address. This is a bit of a bummer in comparison to the old setup.

With that said, Stacker News is providing an immediate solution for those users that do not want their node ID exposed. Stacker News now has a setting where you can turn on a proxy for any incoming sats to your Stacker News ln address, albeit at a cost of 10% of the receiving amount. I assume this will work to basically give you the same experience as before, with the Stacker News lightning node acting as the proxy before sats are sent to your node.

That's awesome that the option is available, but the price is pretty steep (I'd imagine that the price is set steep because Stacker News does not want to act in this function for its users ; this is a classy move to provide it at all even though Stacker News is not probably intending to be a leading privacy service provider in the lightning space). So, what is a pleb to do ? Well, there is a solution out there available to all plebs that can give you the proxy receiving privacy you want without paying 10% of your received sats for that privacy: Enter Zeuspay (https://docs.zeusln.app/lightning-address/intro/)

So, Zeuspay is an ln address that any LND node runner can use by setting up their node in the Zeus app via the available options. I won't go into detail how to do this (i'm happy to answer questions in the comments, but not really the point of this post to give a step by step tutorial), but essentially once you have set up your connection in Zeus to your LND node, there is an option in the setting to create your own Zeuspay ln address. This ln address is a bit different than custodial options you have experienced:

When sats are sent to this ln address, they actually need to be redeemed by you within the Zeus app within 24 hours. If not redeemed within 24 hours, they are sent back to the sender's wallet. This is how zeus set up the service so that it works best with their embedded mobile node as such nodes will not be online all the time.
When you redeem sats, those sats are then actually going first to the Zeus lightning node, and then to your node. Thus, it is a proxy for receiving sats that will not reveal your node to the original sat sender.

So, if a Stacker News user sets up their wallet config in Stacker News to receive sats using the ln address to their Zeuspay ln address, they will now have the privacy benefit of before. AND, what's great is that Zeus just recently dropped the receiving fees to 0 for this service (see the recent nost post here: https://njump.me/nevent1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpz9mhxue69uhkummnw3ezumrpdejz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcpz9mhxue69uhkummnw3ezuamfdejj7qgewaehxw309aex2mrp0yh8xmn0wf6zuum0vd5kzmp0qqsdmf5h6kpzt2pxh0cmgf43uksjhklx07s49n2ydeh82lnqw83p2pqsph5ec). So, as long as you make sure to log into your Zeus app and redeem sats once a day, you can use this option to receive sats to your Stacker News ln address with a privacy proxy that does not utilize Stacker News' proxy service. Now, one caveat I will say which I experienced while testing: if you do not have a channel open with Zeus, it did not work very well for me. However, once I got a channel open with Zeus, and got some inbound liquidity in that channel, it has worked perfectly. Hope that post serves you well fellow Stackers, happy zapping n stacking :)

#bitcoin #lightning

500 sats \ 0 replies \ @DarthCoin 18h

You have many many many other ways to have a LN address. Read here all the options: https://darth-coin.github.io/beginner/getting-started-ln-address-en.html

I personally love to use Zeus but I do not use Zeuspay. Why? Because it relays on the hold invoice method. Hold invoices could trigger anytime a force close of your channels. Also this redeem time I do not like it. I want to receive the sats straight away not having to redeem them manually.

Zeuspay was created from the pressure of nostr users that wanted a so called "self-custodial" LN address, then Zeus team come up with this method so all Zeus users could have a LN address directly into their Zeus app. And Zeuspay is some kind in the middle. I am not saying is a bad concept, only that is not suitable for SN. Even if you run Zeus with a remote node, you will still have problems. With embedded node will be even more, due to the fact that you must be online when you redeem. And many users don't know how to use persistent mode or even have the patience to wait for sync. And will do stupid things that will trigger force closures.

If you really want a 100% stable functional LN address better run your own LN address server hosted on your own hardware, with your own node. If you do not want/have your own domain, fine, read my above guide and you will find out multiple ways to have a LN address with different domains, as decoys or using a federated option.

YOU HAVE BEEN WARNED Using SN with a Zeupay LN address you will have a lot of force closures and trouble, due to the intensity of zaps and particular way of redeeming. Zeuspay is NOT suitable for using it with SN! Maybe in other cases, but not here.

And I raise again and again the whole warning about this craziness with "self-custodial zaps" on SN: Any interceptor for zaps will be added not necessary complexity that will create more trouble than good, due to the intensity of zaps in a certain period. People STILL don't know how to run properly nodes and will have a lot of trouble and will give even more trouble for SN team trying to find where is the problem. But they still do not want to see that the whole system is a MISTAKE.

Instead of dedicating more time in improving SN, they will waste time in debugging users payments and routes.

0 sats \ 0 replies \ @random_ 13h

https://amboss.tech/blog/ghost-addresses

0 sats \ 2 replies \ @bren 20h

You put a lot of thought and work into this post. Paving new trails, thanks for the advice.

0 sats \ 1 reply \ @Bee_Aye OP 20h

ty 🙂

0 sats \ 0 replies \ @bren 20h

Also you can get them in a set. One for the front and one with a long cord for the back. You can connect to the admin interface through wifi on your phone