Add SOCKS5 proxy support for peer and Esplora#24
Merged
amackillop merged 1 commit intolsp-0.7.0_accept-underpaying-htlcs_with_timing_logsfrom Apr 29, 2026
Merged
Conversation
Thread an optional socks5_proxy_addr through Config, Builder, ConnectionManager, and EsploraChainSource so all outbound connections can be routed through a SOCKS5 proxy (e.g. Tor). Peer connections branch between connect_outbound_via_socks5 and the existing connect_outbound. The two async fns return different opaque Future types, so we Box::pin in each branch to erase the type before the shared match block. Esplora passes socks5://<addr> to esplora_client::Builder::proxy, which uses reqwest's built-in SOCKS5 support under the hood. Bumps rust-lightning to lsp-0.2.0_socks-support (adf445e5) which adds the connect_outbound_via_socks5 function behind a "socks" feature flag on lightning-net-tokio. Electrum proxy support deferred to a follow-up.
amackillop
force-pushed
the
austin_socks-support
branch
from
3849d35 to
078e170
Compare
Author
|
Replaces #15 to fix a merge conflict. The previous branch name trigger the force push protection rule |
martinsaposnic
approved these changes
Apr 29, 2026
amackillop
merged commit 522b511
into
lsp-0.7.0_accept-underpaying-htlcs_with_timing_logs
6 of 34 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thread an optional socks5_proxy_addr through Config, Builder, ConnectionManager, and EsploraChainSource so all outbound connections can be routed through a SOCKS5 proxy (e.g. Tor).
Peer connections branch between connect_outbound_via_socks5 and the existing connect_outbound. The two async fns return different opaque Future types, so we Box::pin in each branch to erase the type before the shared match block.
Esplora passes socks5:// to esplora_client::Builder::proxy, which uses reqwest's built-in SOCKS5 support under the hood.
Bumps rust-lightning to lsp-0.2.0_socks-support (adf445e5) which adds the connect_outbound_via_socks5 function behind a "socks" feature flag on lightning-net-tokio.
Electrum proxy support deferred to a follow-up.