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

lnonion: explicitly forbid nesting trampoline-in-trampoline

Public commit record

What the developer wrote

Authored by SomberNight

85/100 · Strong
lnonion: explicitly forbid nesting trampoline-in-trampoline

This assert is needed because I don't want to reason about
what could happen without it.

We currently use fixed 400 bytes trampoline onion sizes, which would
implicitly prevent this. However the current bolts PR actually specifies
variable size trampoline onions.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This commit adds a safety check in Electrum's Lightning code to block a 'trampoline inside trampoline' payment routing scenario. The developer states they don't want to reason about what could go wrong without this guard. The current code already uses fixed-size onions that would likely prevent the nested case, but a future protocol change may allow variable-size trampoline onions, so this assert is added defensively.

Recommended action

Treat as a low-confidence hardening patch. Review whether nested trampoline onions could enable routing loops, fee extraction, or privacy degradation. If a security issue is suspected, request a security advisory or CVE from the maintainers; otherwise, include in normal release notes as a defensive fix.

Security signals we found

01

Defensive assert added to prevent nested trampoline onion routing

02

Developer explicitly states they don't want to reason about consequences without the check

03

Future protocol change (variable-size trampoline onions) motivates the guard

04

No CVE, advisory, or researcher attribution present in commit

Risk score

Why this scored 41/100

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