From e87762b652fc41d0986eb0693a2ef4b7ba8209ff Mon Sep 17 00:00:00 2001 From: Matt Corallo Date: Wed, 27 Jul 2022 03:53:47 +0000 Subject: [PATCH] Expose `ChannelMonitor::get_counterparty_node_id` This fixes an oversight in ac842ed9dd7a36a4a26eb6b856d80ab04eecf750 namely that it left users unable to implement their own `ChainMonitor` from outside of the `rust-lightning` crate. --- lightning/src/chain/channelmonitor.rs | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/lightning/src/chain/channelmonitor.rs b/lightning/src/chain/channelmonitor.rs index 38dcd6cf0..855263fe5 100644 --- a/lightning/src/chain/channelmonitor.rs +++ b/lightning/src/chain/channelmonitor.rs @@ -1214,7 +1214,11 @@ impl ChannelMonitor { self.inner.lock().unwrap().get_cur_holder_commitment_number() } - pub(crate) fn get_counterparty_node_id(&self) -> Option { + /// Gets the `node_id` of the counterparty for this channel. + /// + /// Will be `None` for channels constructed on LDK versions prior to 0.0.110 and always `Some` + /// otherwise. + pub fn get_counterparty_node_id(&self) -> Option { self.inner.lock().unwrap().counterparty_node_id } -- 2.39.5