You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In discussions this week, it was noted that channels with an HTLC in-flight-max smaller than the channel capacity (specifically, both directions having an htlc_in_flight_max < 50% of the channel capacity, with lower better) makes a channel somewhat harder to probe for live balances, thereby improving privacy for payments routed through that node.
While more privacy protections should be added, this is a super trivial heuristic that we can use to encourage network-wide "good behavior" today - simply detect this and prefer channels which have this privacy improvement in our scorer.
The text was updated successfully, but these errors were encountered:
In discussions this week, it was noted that channels with an HTLC in-flight-max smaller than the channel capacity (specifically, both directions having an htlc_in_flight_max < 50% of the channel capacity, with lower better) makes a channel somewhat harder to probe for live balances, thereby improving privacy for payments routed through that node.
While more privacy protections should be added, this is a super trivial heuristic that we can use to encourage network-wide "good behavior" today - simply detect this and prefer channels which have this privacy improvement in our scorer.
The text was updated successfully, but these errors were encountered: