fixup! Expose per-channel features in ChannelDetails

make outbound_htlc_minimum_msat optional

this handles the conversion of the LDK type correctly
& removes the possibility of panicking when we list
channels

Author: enigbe

src/types.rs

@@ -446,7 +446,10 @@ pub struct ChannelCounterparty {
 	/// payments to us through this channel.
 	pub forwarding_info: Option<CounterpartyForwardingInfo>,
 	/// The smallest value HTLC (in msat) the remote peer will accept, for this channel.
-	pub outbound_htlc_minimum_msat: u64,
+	///
+	/// Will be `None` before we have received the `OpenChannel` or `AcceptChannel` message
+	/// from the remote peer.
+	pub outbound_htlc_minimum_msat: Option<u64>,
 	/// The largest value HTLC (in msat) the remote peer currently will accept, for this channel.
 	pub outbound_htlc_maximum_msat: Option<u64>,
 }
@@ -696,12 +699,7 @@ impl ChannelDetails {
 				features: maybe_wrap(value.counterparty.features),
 				unspendable_punishment_reserve: value.counterparty.unspendable_punishment_reserve,
 				forwarding_info: value.counterparty.forwarding_info,
-				// unwrap safety: This value will be `None` for objects serialized with LDK versions
-				// prior to 0.0.115.
-				outbound_htlc_minimum_msat: value
-					.counterparty
-					.outbound_htlc_minimum_msat
-					.expect("value is set for objects serialized with LDK v0.0.107+"),
+				outbound_htlc_minimum_msat: value.counterparty.outbound_htlc_minimum_msat,
 				outbound_htlc_maximum_msat: value.counterparty.outbound_htlc_maximum_msat,
 			},
 			funding_txo: value.funding_txo.map(|o| o.into_bitcoin_outpoint()),