Skip to content

Conversation

@tnull
Copy link
Collaborator

@tnull tnull commented Mar 21, 2025

Closes #499.

Previously, we'd always disallow forwarding to unannounced channels. However, if we're acting as an LSP, we should allow forwarding to unannounced channels.

@tnull tnull added this to the 0.5 milestone Mar 28, 2025
.max_inbound_htlc_value_in_flight_percent_of_channel,
100
);
debug_assert!(config.accept_forwards_to_priv_channels);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems quite defensive. Is it really needed?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, in this case I'd prefer to make sure it is set. The issue is that we have 2-3 UserConfigs flying around now that we change depending on the context/assumptions. This is just insurance going forward that we don't change something somewhere else without keeping this use case in mind. Maybe at some point it might warrant a refactoring with some more involved config management, but I think we're not entirely there yet.

Previously, we'd always disallow forwarding to unannounced channels.
However, if we're acting as an LSP, we *should* allow forwarding to
unannounced channels.
@tnull tnull force-pushed the 2025-03-set-priv-channel-forward-if-lsp branch from 6555b69 to da5a839 Compare March 28, 2025 17:22
@tnull
Copy link
Collaborator Author

tnull commented Mar 28, 2025

Squashed the fixup without further changes, going ahead landing this.

@tnull tnull merged commit 095ba89 into lightningdevkit:main Mar 28, 2025
10 of 14 checks passed
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.

accept_forwards_to_priv_channels is always false

2 participants