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

Check that relay fees are nonnegative (#3209)

Public commit record

What the developer wrote

Authored by Thomas HUET

53/100 · Thin
Check that relay fees are nonnegative (#3209)

Fixes #3204
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This commit adds a server-side check to make sure users cannot set negative Lightning Network routing fees through the API. Previously, the API accepted negative values for base and proportional relay fees, which could cause a node to pay others when forwarding payments or create confusing, loss-inducing channel policies. The fix rejects such inputs with a validation error.

Recommended action

Review whether negative fee values could already exist in persisted channel configurations or database state, and consider adding similar validation at the business-logic layer (eclairApi.updateRelayFee) as defense in depth. No immediate emergency action is indicated.

Security signals we found

01

Input validation added for API fee parameters

02

Negative fee values previously accepted by updateRelayFee endpoint

03

Potential for fee policy manipulation leading to unintended payment forwarding losses

04

Fixes referenced issue #3204

Risk score

Why this scored 54/100

Our methodology →
Potential impact 12/30
Exploitability 14/25
Stealth signal 8/15
Affected reach 10/15
Confidence 7/10
Evidence quality 3/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.