Skip to content

Assume SCID aliases; default for private channels - #1362

Open
tnull wants to merge 1 commit into
lightning:masterfrom
tnull:2026-09-assume-scid-alias
Open

tnull wants to merge 1 commit into
lightning:masterfrom
tnull:2026-09-assume-scid-alias

Conversation

@tnull

@tnull tnull commented Sep 24, 2026

Copy link
Copy Markdown
Contributor

The option_scid_alias channel type was introduced in #910.

I want to propose to make option_scid_alias ASSUMED in general and require implementations to require the channel type (i.e., disallow forwarding over real SCIDs of unannounced channels) when both parties negotiate the feature.

Require the option_scid_alias channel type for new unannounced
channels when both peers advertise support. This lets peers rely on
alias-only forwarding and reduces exposure to probes using real
SCIDs derived from P2WSH outputs observed on chain.

Mark support as ASSUMED while retaining feature advertisements and
conditioning the channel type requirement on them. This leaves a
compatibility window for peers that do not advertise support.

Co-Authored-By: HAL 9000
@tnull

tnull commented Sep 24, 2026

Copy link
Copy Markdown
Contributor Author

Oh, it seems while LND generally supported option_scid_alias for a long time, they still default to not advertising/negotiating the feature.

@Roasbeef I found some old discussions that indicate you had planned to switch the default to true for a long time. Is this still the plan? If not, is there any reason you don't support the feature by default?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant