Even though I don't run lnd v0.18 on c-otto.de, yet, I already tweaked my scripts so that they are ready to set negative inbound fees once the feature is available. For this, I came up with the following rules (which, of course, are not set in stone) and I'd be very happy to hear your feedback.
Default 0. Obviously.
Still 0 if at least one of the following is true:
- less than 15M sat on the remote side: those sats will flow naturally
- more sats on my side than on the remote side: 50/50 is fine
- channel is less than 45 days old: maybe the natural flow is good enough
- I haven't earned at least 2,000sats routing to that peer: I don't feel the need to pay in order to have more sats on my side
Otherwise, I will set some negative fee rate, i.e. introduce a rebate for sats flowing from that peer.
This negative fee rate is relative to the outbound fee rate, starting with -50%. This also means the rebate is low (possibly 0) if my outbound fee rate is low, and higher for lucrative peers where I charge a lot (like LOOP).
If, for example, I charge 800ppm for outbound traffic, I might set the inbound fee rate to -400ppm (-50%). For peers where I have lots of remote liquidity, I increase the rebate to -75% or, if there's even more remote liquidity, to -85%.
For very specific peers (like LOOP) I don't bother with this configuration and, instead, configure a fixed rebate of -1000ppm or so.
I can't wait to see how this works out in practice. What do you think?
updatechanpolicyinlncliand the APIs. I don't see the reason, but you could check the existence of these parameters if you don't know the version of lnd itself.