AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 62 Bitcoin

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

Public commit record

What the developer wrote

Authored by Yong

73/100 · Adequate
Merge pull request #11190 from Roasbeef/zpay32-reject-duplicate-payment-hashes

zpay32: reject duplicate payment hash fields
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

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 release notes frame this as an interoperability improvement rather than a security fix, but the behavior removes a potential source of confusion or invoice manipulation where a second, different payment hash could be present but ignored.

Recommended action

Treat as a hardening/interoperability patch. Review whether any downstream callers rely on the old silent-skip behavior and ensure the new error is handled gracefully. Consider monitoring for any reports linking duplicate payment hash invoices to real-world attacks, but no immediate emergency response is indicated by the commit materials.

Security signals we found

01

Behavior change from 'use first duplicate field' to 'reject duplicate fields'

02

New error type ErrDuplicatePaymentHash returned on duplicate payment hash fields

03

Malformed/unsupported-length duplicate payment hash now treated as duplicate and rejected

04

Release notes explicitly mention BOLT 11 interop and link to BOLTS PR 1357

05

No CVE, advisory, or security advisory language present in commit or references

Risk score

Why this scored 62/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 8/15
Affected reach 12/15
Confidence 8/10
Evidence quality 4/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.