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

Merge pull request #11340 from bitromortac/20261012-b57b-dispatch

Public commit record

What the developer wrote

Authored by Yong

73/100 · Adequate
Merge pull request #11340 from bitromortac/20261012-b57b-dispatch

bolt12handler: add the invoice request handler behind a protocol flag
✓ 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 commit adds a new, experimental BOLT 12 invoice-request handler to LND. It is gated behind a build flag and a protocol option, requires native SQL, and is described in release notes as not yet routing real invoice requests to the handler. The change is a feature addition with defensive validation and tests, not a fix for an active vulnerability.

Recommended action

Treat this as a routine feature merge rather than an urgent security patch. Reviewers should focus on the validation logic in bolt12handler/validate.go and handler.go, ensure the CLTV-delta bounds are correct, and confirm the experimental gating prevents accidental production activation. Continue monitoring for follow-up commits that wire real invoice-request routing and database persistence.

Security signals we found

01

New experimental feature behind build and protocol flags

02

Adds input validation for BOLT 12 invoice requests (reply path, offer lookup, expiry, disabled, currency)

03

Adds CLTV delta bounds checks to avoid uint16 overflow when building blinded payment paths

04

Adds startup config validation requiring native SQL, onion messages, route blinding, and development migrations

05

No database row is written for generated BOLT 12 invoices yet; only an in-memory notification is sent

06

No vendor disclosure of a security issue or CVE

Risk score

Why this scored 25/100

Our methodology →
Potential impact 4/30
Exploitability 3/25
Stealth signal 3/15
Affected reach 3/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.