From d0e12c1941f79b9fc054aee529684714dc0ccded Mon Sep 17 00:00:00 2001 From: Matt Corallo Date: Thu, 12 Sep 2024 18:43:02 +0000 Subject: [PATCH] f reword how we describe the payment id construciton --- lightning/src/events/mod.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lightning/src/events/mod.rs b/lightning/src/events/mod.rs index 14e043bd75..1c6cd52689 100644 --- a/lightning/src/events/mod.rs +++ b/lightning/src/events/mod.rs @@ -748,7 +748,7 @@ pub enum Event { /// /// [`ChannelManager::claim_funds`]: crate::ln::channelmanager::ChannelManager::claim_funds claim_deadline: Option, - /// A unique, random, ID describing this payment. + /// A unique ID describing this payment (derived from the list of HTLCs in the payment). /// /// Payers may pay for the same [`PaymentHash`] multiple times (though this is unsafe and /// an intermediary node may steal the funds). Thus, in order to accurately track when @@ -803,7 +803,7 @@ pub enum Event { /// /// Payments received on LDK versions prior to 0.0.124 will have this field unset. onion_fields: Option, - /// A unique, random, ID describing this payment. + /// A unique ID describing this payment (derived from the list of HTLCs in the payment). /// /// Payers may pay for the same [`PaymentHash`] multiple times (though this is unsafe and /// an intermediary node may steal the funds). Thus, in order to accurately track when