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

zpay32: resync BOLT 11 vectors with bolts#1368

Public commit record

What the developer wrote

Authored by Olaoluwa Osuntokun

81/100 · Strong
zpay32: resync BOLT 11 vectors with bolts#1368

In this commit, we pick up the corrected high-S vector from
lightning/bolts#1368, which drops the duplicate `s` field it used to
carry. The vector now reaches the signature check, so we expect
`ErrHighSSignature` for it rather than `ErrDuplicatePaymentAddr`.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
The short version

What changed, and why it matters

This commit updates LND's test data and test expectations to match a corrected official BOLT 11 specification test vector. The invoice string used to exercise 'high-S' signature rejection was changed so it no longer contains a duplicate 's' field. The test now expects the code to reject it specifically for the high-S signature, not for a duplicate field. It is a test-only alignment with the spec, not a functional code change.

Recommended action

No action required. This is a test maintenance commit. Reviewers may optionally verify the new test vector matches the upstream BOLT 11 PR.

Security signals we found

01

Test-only update to align with upstream BOLT 11 specification vectors

02

Corrected high-S signature test vector no longer masks signature validation behind duplicate-field rejection

03

No changes to signature verification, duplicate-field detection, or invoice decoding logic

Risk score

Why this scored 20/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 2/15
Confidence 9/10
Evidence quality 5/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.