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

Intercept onion messages for unknown SCID hops

Public commit record

What the developer wrote

Authored by Elias Rohrer

68/100 · Adequate
Intercept onion messages for unknown SCID hops

Allow integrations to intercept blinded onion-message hops that identify
the next node by short channel id, so LSPS-style protocols can resolve
those hops out of band instead of dropping the message.

Co-Authored-By: HAL 9000
✓ 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 feature to LDK's onion message forwarding. Previously, if an onion message's next hop was identified by a short channel ID (SCID) that the node didn't know, the message was silently dropped. Now, if a user explicitly enables 'intercept_for_unknown_scids', the node can hold onto the message and emit an event, allowing external protocols (like LSPS-style services) to resolve the SCID out-of-band and forward the message later. The change also updates how these intercepted events are serialized for backwards compatibility with older LDK versions.

Recommended action

Review the new interception API and serialization behavior for correctness; ensure that user-facing documentation clearly warns that enabling intercept_for_unknown_scids produces events that cannot be downgraded to LDK 0.2. Consider whether persisted intercepted messages could be replayed or abused, and verify that re-injected messages are validated before forwarding.

Security signals we found

01

New interception path for onion messages with unresolvable SCID next hops

02

Event serialization change with backward-incompatible ShortChannelId variant

03

Behavior gated by explicit opt-in flag intercept_for_unknown_scids

04

Potential for intercepted messages to be persisted and re-injected by user code

05

Serialization downgrade test confirms LDK 0.2 cannot read ShortChannelId variant

Risk score

Why this scored 37/100

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