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

bolt12: add chains TLV subtype

Public commit record

What the developer wrote

Authored by bitromortac

68/100 · Adequate
bolt12: add chains TLV subtype

Introduce the ChainsRecord subtype used by the offer_chains and
invoice_chains TLV fields. Decoding caps the count at maxOfferChains to
bound allocation.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit adds a new data type for handling lists of blockchain identifiers in BOLT 12 offers and invoices. The main security-relevant detail is that the decoder now limits how many chain hashes can be requested at once, preventing a malformed message from tricking the software into allocating excessive memory. It is a defensive, forward-looking change rather than a fix for an active bug.

Recommended action

No immediate action required. Treat as routine defensive hardening. Continue reviewing the broader BOLT 12 codec series for consistent input validation and resource limits.

Security signals we found

01

New decoder enforces maxOfferChains cap to bound memory allocation

02

Length validation ensures chain hash list length is a multiple of 32 bytes

03

No use of untrusted length for allocation without an upper bound

04

Test coverage includes malformed length and cap-exceeded cases

Risk score

Why this scored 21/100

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