pull down to refresh

I've also sometimes had trouble finding routes through SN's node. Sometimes I can only find a route if I increase the max fee to something like 100+.
One thing I noticed about SN is that sats are always flowing out of it.
On my public LN node, as soon as I put sats on the SN side of the channel, it almost immediately gets routed back to my side and onto some other destination.
My hypothesis is that there's a huge demand for liquidity to move sats out of or through SN. Thus, channels are setting high fees for the usage of those channels. The low fee ones quickly get exhausted (as my public channel always does.)
Maybe @k00b or @ek can comment. It's definitely a pattern that i've noticed.
Thanks, that's sort of what I imagined was happening, but I'm still new to managing a lightning node.
reply
57 sats \ 1 reply \ @ek 23 Oct
soon you will teach @grayruby
reply
Definitely. I have no clue.
reply
32 sats \ 2 replies \ @k00b 23 Oct
If you don't want other pushing around your liquidity in a direct channel you have with SN you have two options:
  1. make the channel private
  2. make the channel expensive (you won't pay routing fees from SN to you and vice versa)
reply
I am certainly thinking of raising the fee, and i imagine many other channels have done so after noticing how quickly their liquidity gets used.
reply
Hmm. Just found out that I can only set the fee on payments that use my channels' outbound capacity. I can't set a fee on payments using my channels' inbound capacity.
But I don't want to raise the fee on people sending sats to Stacker.News, I want to raise the fee on people wanting to send sats from Stacker.News.
Seems I can't do that specifically. You guys actually control the fee rate for that.
reply