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
Router: Ensure used liquidity is always limited by hop's capacity
Previously, when recomputing fees for bottleneck hops, we might allow
the tracked used liquidity values to surpass the actual hop capacity,
which is bogus. Here, we assert we'd always limit the amount spend on
a hop by its capacity.
Found by a `fuzz` test hitting the related `debug_assert`.
0 commit comments