Serialization for Vec<BlindedMessagePath>
What the developer wrote
Authored by Joost Jager
Serialization for Vec<BlindedMessagePath>
What changed, and why it matters
This commit adds a single line of code that enables serialization (the ability to convert data into a format that can be stored or transmitted) for a list of BlindedMessagePath objects. It is a routine, additive change with no visible security implications. There is no indication this fixes or introduces a vulnerability.
No security action required. Review as part of normal code review if this serialization support is needed for an upcoming feature.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change adds impl_for_vec!(crate::blinded_path::message::BlindedMessagePath); to lightning/src/util/ser.rs, which implements the Writeable and Readable traits for Vec<BlindedMessagePath>. This is a boilerplate serialization macro invocation consistent with surrounding code. No logic changes, bounds checks, or security-sensitive code is modified.
Changed components
lightning/src/util/ser.rsInspect captured patch +1 / −0
diff --git a/lightning/src/util/ser.rs b/lightning/src/util/ser.rs
index 15fd7fe..aa2d105 100644
--- a/lightning/src/util/ser.rs
+++ b/lightning/src/util/ser.rs
@@ -1085,6 +1085,7 @@ impl_for_vec!(SerialId);
impl_for_vec!(NegotiatedTxInput);
impl_for_vec!(InteractiveTxOutput);
impl_for_vec!(crate::ln::our_peer_storage::PeerStorageMonitorHolder);
+impl_for_vec!(crate::blinded_path::message::BlindedMessagePath);
impl_writeable_for_vec!(&crate::routing::router::BlindedTail);
impl_readable_for_vec!(crate::routing::router::BlindedTail);
impl_for_vec!(crate::routing::router::TrampolineHop);
Why this scored 18/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.