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
Scorers could benefit from having the channel's EffectiveCapacity rather
than a u64 msat value. For instance, ProbabilisticScorer can give a more
accurate penalty when given the ExactLiquidity variant. Pass a struct
wrapping the effective capacity, the proposed amount, and any in-flight
HTLC value.
use routing::network_graph::{NetworkGraph,NetGraphMsgHandler,NodeId};
1714
1727
use routing::router::{get_route, add_random_cltv_offset, default_node_features,PaymentParameters,Route,RouteHint,RouteHintHop,RouteHop,RoutingFees,DEFAULT_MAX_TOTAL_CLTV_EXPIRY_DELTA};
1715
-
use routing::scoring::Score;
1728
+
use routing::scoring::{ChannelUsage,Score};
1716
1729
use chain::transaction::OutPoint;
1717
1730
use chain::keysinterface::KeysInterface;
1718
1731
use ln::features::{ChannelFeatures,InitFeatures,InvoiceFeatures,NodeFeatures};
0 commit comments