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

decode: print htlc_minimum_msat / htlc_maximum_msat in blinded paths.

Public commit record

What the developer wrote

Authored by Rusty Russell

81/100 · Strong
decode: print htlc_minimum_msat / htlc_maximum_msat in blinded paths.

Weird we didn't print this before!

Reported-by: https://github.com/Lagrang3
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit adds two missing fields, htlc_minimum_msat and htlc_maximum_msat, to the output of the 'decode' command when it shows blinded payment paths. Previously these values were decoded internally but not printed in JSON or CLI output. It is a display/information fix, not a code-execution vulnerability.

Recommended action

No security action required; treat as a normal feature/bug-fix update. Users relying on decode output for blinded path analysis may want to update to obtain complete payinfo fields.

Security signals we found

01

Missing output field in decode command for blinded path payinfo

02

No change to parsing, validation, or cryptographic handling

03

No memory safety, authorization, or consensus code modified

04

Reported-by line credits an external contributor

Risk score

Why this scored 20/100

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