CommitWatch RSS
AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 31 Bitcoin

go: update lightning-onion

LL14024fc8 View source ↗
Public commit record

What the developer wrote

Authored by Gijs van Dam

50/100 · Thin
go: update lightning-onion

Update lightning-onion to commit that includes onion-messaging support.
✓ Descriptive subject✓ Provides an explanatory body
The short version

What changed, and why it matters

This commit updates a core Lightning Network library (lightning-onion) to a new version that adds 'onion-messaging support.' It also adjusts LND's own code to match renamed constants and functions in that library. The change is presented as a routine dependency update, but because the library handles the encrypted routing packets that every Lightning payment uses, any change there can affect payment privacy and correctness. There is no direct evidence in the commit of a security bug or fix, and no vendor statement that this update is security-related.

Recommended action

Treat as a normal dependency update unless additional context shows the lightning-onion v1.3.0 release contains a security fix. Review the lightning-onion v1.3.0 release notes and diff for any security-relevant changes, run existing fuzz tests, and verify that the MaxRoutingPayloadSize constant and DecodeHopPayload behavior do not weaken payload-size enforcement or parsing robustness.

Security signals we found

01

Dependency update of a cryptographic/onion-routing library to a new minor version

02

API rename from MaxPayloadSize to MaxRoutingPayloadSize and introduction of DecodeHopPayload with tlvGuaranteed flag

03

Commit message frames change as feature addition ('onion-messaging support'), not a security fix

04

No CVE, advisory, or vendor security statement present in supplied materials

Risk score

Why this scored 31/100

Our methodology →
Potential impact 5/30
Exploitability 5/25
Stealth signal 5/15
Affected reach 10/15
Confidence 4/10
Evidence quality 2/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.

More from LND

Related watches

Moderate 62 AI analysisMessage 58 · Thin
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11212 from ziggie1984/disable-legacy-channels

This change stops LND from opening new Lightning channels using the old 'legacy' commitment format. The legacy format makes it harder to recover funds if something goes wrong, because the money owed to you is tied to a secret key that chan…

Prevents opening new channels with the legacy commitment type, whose tweaked to_remote output complicates data-loss recoveryCloses a negotiation path where an empty channel_type TLV bypassed feature checks and forced a legacy channelAdds explicit RPC and wire rejection with a dedicated error code
112cb5f3by ziggieXXX+265−4716 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 56 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11223 from gijswijs/legacy-dust-retribution-fix

This update fixes a bug in how LND handles old-style punishment transactions when a channel partner tries to cheat. Previously, tiny (dust) HTLCs were left as blank placeholder entries in the punishment data, which could cause the node to …

nil-pointer dereference risk in breach retribution pathlegacy revocation log handling inconsistency with modern formatdefensive hardening added for trimmed/dust HTLCs
500ca51fby ziggieXXX+168−146 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 62 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11190 from Roasbeef/zpay32-reject-duplicate-payment-hashes

This change tightens how LND reads Lightning invoices (BOLT 11). Previously, if an invoice contained more than one payment hash field, LND would silently keep the first one and ignore the rest. Now it rejects the invoice entirely. The rele…

Behavior change from 'use first duplicate field' to 'reject duplicate fields'New error type ErrDuplicatePaymentHash returned on duplicate payment hash fieldsMalformed/unsupported-length duplicate payment hash now treated as duplicate and rejected
86306f89by Yong+147−106 files
No security note in commit
Open full analysis →Source commit ↗