Ben Franklin's Kite asked almost 3 years ago
What can node operators do to prevent remote liquidity from being taken?
What can node operators do to prevent remote liquidity from being "taken" (perhaps not the right word, but converted from remote to local liquidity) IMMEDIATELY after channel connection being established?
The following has taken place multiple times- A swap is joined for the purpose of gaining remote liquidity and expanding reach on the network. As soon as the channel is opened, the remote liquidity is zapped by what appears to be an auto rebalance script; its definitely not a payment for the full amount of the channel. I've tried to prevent this by raising fees immediately after channel opening, but it happens so fast that I can't make it to the channel fee update or even blink an eye before losing the remote liquidity. This happens even if I wait for channel connection prior to announcing the channel is being opened. I'm watching mempool for the opening transaction to go through so I can be on top of it as soon as there is confirmation.
When I try to rebalance, I can't find a profitable route. In essence, I'm paying fees to connect to my own local liquidity (and sometimes end up with a channel partner that can't route even at 0/2 so then I have closing fees as well).
Is there a workaround or prevention method I can implement before these rug pulls cause me to break my tailbone?
The following has taken place multiple times- A swap is joined for the purpose of gaining remote liquidity and expanding reach on the network. As soon as the channel is opened, the remote liquidity is zapped by what appears to be an auto rebalance script; its definitely not a payment for the full amount of the channel. I've tried to prevent this by raising fees immediately after channel opening, but it happens so fast that I can't make it to the channel fee update or even blink an eye before losing the remote liquidity. This happens even if I wait for channel connection prior to announcing the channel is being opened. I'm watching mempool for the opening transaction to go through so I can be on top of it as soon as there is confirmation.
When I try to rebalance, I can't find a profitable route. In essence, I'm paying fees to connect to my own local liquidity (and sometimes end up with a channel partner that can't route even at 0/2 so then I have closing fees as well).
Is there a workaround or prevention method I can implement before these rug pulls cause me to break my tailbone?
1 Comment
LN+ Admin wrote almost 3 years ago
Yes, you can set your default fees on your node. So when the channel opens it would immediately have the high fees.
Please login to post comments.