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
Allow forwarding HTLCs that were constructed for previous config
This is mostly motivated by the fact that payments may happen while the
latest `ChannelUpdate` indicating our new `ChannelConfig` is still
propagating throughout the network. By temporarily allowing the previous
config, we can help reduce payment failures across the network.
breakSome(("Forwarding node has tampered with the intended HTLC values or origin node has an obsolete cltv_expiry_delta",0x1000 | 13, chan_update_opt));
2271
-
}
2272
2274
let cur_height = self.best_block.read().unwrap().height() + 1;
2273
2275
// Theoretically, channel counterparty shouldn't send us a HTLC expiring now,
2274
2276
// but we want to be robust wrt to counterparty packet sanitization (see
Copy file name to clipboardExpand all lines: lightning/src/ln/onion_route_tests.rs
+26-6
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,7 @@
14
14
use chain::channelmonitor::{ChannelMonitor,CLTV_CLAIM_BUFFER,LATENCY_GRACE_PERIOD_BLOCKS};
15
15
use chain::keysinterface::{KeysInterface,Recipient};
16
16
use ln::{PaymentHash,PaymentSecret};
17
+
use ln::channel::EXPIRE_PREV_CONFIG_TICKS;
17
18
use ln::channelmanager::{ChannelManager,ChannelManagerReadArgs,HTLCForwardInfo,CLTV_FAR_FAR_AWAY,MIN_CLTV_EXPIRY_DELTA,PendingHTLCInfo,PendingHTLCRouting};
18
19
use ln::onion_utils;
19
20
use routing::gossip::{NetworkUpdate,RoutingFees,NodeId};
0 commit comments