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

askrene: add auto.include_fees layer

Public commit record

What the developer wrote

Authored by Lagrang3

68/100 · Adequate
askrene: add auto.include_fees layer

Changelog-Added: askrene: add a new layer auto.include_fees thhat makes fees be deducted from the payment amount making in effect the receiver pay for routing fees.

Signed-off-by: Lagrang3 <lagrang3@protonmail.com>
✓ 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 optional routing layer called auto.include_fees to Core Lightning's askrene plugin. Normally, when sending a Lightning payment, the sender adds extra money on top of the requested amount to cover routing fees. With this new layer, the total amount sent is fixed, and the fees are subtracted from what the receiver gets instead. This is a deliberate feature change, not a bug fix, and it only affects routing calculations when a user explicitly requests the new layer. There is no direct security vulnerability in the code shown, but any mistake in fee arithmetic could in theory cause incorrect payment amounts.

Recommended action

No immediate security action required. Treat as a normal feature review: verify the new fee-deduction arithmetic is correct in all edge cases (MPP, sourcefree, zero-fee channels, overflow/underflow handling), and ensure documentation clearly warns users that the receiver receives less than the requested amount when auto.include_fees is used.

Security signals we found

01

New feature code, not a security patch

02

Fee arithmetic changed in routing path construction

03

No input validation, buffer, or cryptographic changes observed

04

No vendor security disclosure or CVE references present

Risk score

Why this scored 21/100

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