What changed, and why it matters
This is a documentation-only change. A package comment was updated to accurately describe that the bolt12 codec library does depend on LND's lnwire package for low-level message types, while clarifying it still does not interact with the running daemon. There is no code change and no security impact.
No action required. This is a non-security documentation correction.
Security signals we found
No strong security signals were identified.
Evidence from the diff
Commit 5f53171d505c14c1e2b5a29e182535f00666901a modifies bolt12/doc.go only. It replaces the claim of ‘no LND daemon dependencies’ with a more precise statement that the package is a codec library that does not reach into the daemon but receives chain, clock, and feature bits from its caller. The import of lnwire for pure-TLV framing, blinded-path types, and feature vectors is implicitly acknowledged. No functional code was altered.
Changed components
bolt12/doc.goInspect captured patch +3 / −2
### bolt12/doc.go
@@ -1,6 +1,7 @@
// Package bolt12 implements encoding, decoding, and validation for BOLT 12
-// Offers, Invoice Requests, and Invoices. It provides a pure codec library
-// with no LND daemon dependencies.
+// Offers, Invoice Requests, and Invoices. It is a codec library: it does not
+// reach into the daemon, and it takes the chain, the clock and the known
+// feature bits from its caller.
//
// BOLT 12 messages use TLV streams encoded with a checksumless bech32 variant
// and signed with BIP-340 Schnorr signatures over a Merkle tree of TLV fields.Why this scored 15/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.