@@ -60,11 +60,10 @@ use crate::ln::chan_utils::selected_commitment_sat_per_1000_weight;
6060// Since this struct is returned in `list_channels` methods, expose it here in case users want to
6161// construct one themselves.
6262use crate::ln::channel::{
63- self, hold_time , Channel, ChannelError, ChannelUpdateStatus, FundedChannel, InboundV1Channel ,
64- OutboundV1Channel, ReconnectionMsg, ShutdownResult, UpdateFulfillCommitFetch ,
65- WithChannelContext,
63+ self, hold_time_since , Channel, ChannelError, ChannelUpdateStatus, FundedChannel,
64+ InboundV1Channel, OutboundV1Channel, PendingV2Channel, ReconnectionMsg, ShutdownResult ,
65+ UpdateFulfillCommitFetch, WithChannelContext,
6666};
67- use crate::ln::channel::{duration_since_epoch, PendingV2Channel};
6867use crate::ln::channel_state::ChannelDetails;
6968use crate::ln::inbound_payment;
7069use crate::ln::msgs;
@@ -8299,8 +8298,7 @@ This indicates a bug inside LDK. Please report this error at https://github.com/
82998298 RAAMonitorUpdateBlockingAction::from_prev_hop_data(&hop_data);
83008299
83018300 // Obtain hold time, if available.
8302- let now = duration_since_epoch();
8303- let hold_time = hold_time(send_timestamp, now).unwrap_or(0);
8301+ let hold_time = hold_time_since(send_timestamp).unwrap_or(0);
83048302
83058303 // If attribution data was received from downstream, we shift it and get it ready for adding our hold
83068304 // time. Note that fulfilled HTLCs take a fast path to the incoming side. We don't need to wait for RAA
0 commit comments