feat: add Tor SOCKS5 proxy support for outbound .onion connections #91
Conversation
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
This was referenced Feb 7, 2026
Implement SOCKS5 protocol in connection.rs to route outbound peer connections through a Tor proxy. This enables LDK nodes to connect to peers at .onion addresses. Changes: - Add tor_socks5_connect() with full SOCKS5 handshake (RFC 1928/1929) - Support Tor stream isolation via random password auth per connection - Add set_tor_proxy_address() on NodeBuilder (FFI-compatible via UDL) - Route OnionV3 addresses through SOCKS5, clearnet through direct TCP - Include base32 encoder for OnionV3 address derivation Based on the approach in upstream ldk-node PR lightningdevkit#778, but with a self-contained SOCKS5 implementation that doesn't depend on unreleased lightning_net_tokio::tor_connect_outbound(). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
sat-engineer
force-pushed
the
feat/tor-socks-outbound
branch
from
814c9d1 to
c51e3e6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
connection.rsfor routing outbound peer connections through a Tor proxyset_tor_proxy_address()onNodeBuilder(FFI-compatible via UDL) to configure the SOCKS5 proxy.onion(OnionV3) addresses through SOCKS5 with Tor stream isolation (random password auth per connection), clearnet addresses through direct TCPlightning_net_tokio::tor_connect_outbound()from upstream PR Add Tor support for outbound connections via SOCKS lightningdevkit/ldk-node#778Relates to getAlby/hub#2035
Related PRs
This is part of a 3-PR series enabling Tor .onion-to-.onion Lightning peer connections in Alby Hub:
Dependency chain: PR 1 → PR 2 → PR 3
Files changed
src/connection.rs— SOCKS5 handshake, base32 encoder for OnionV3 address derivation, routing logic + 15 unit testssrc/builder.rs—tor_proxy_addressfield andset_tor_proxy_address()method onNodeBuilderbindings/ldk_node.udl— FFI interface definition forset_tor_proxy_addressTest plan
cargo test --lib connection::tests— 15 tests passing (base32 encoding, SOCKS5 protocol with mock proxy)cargo checkpasses with zero warnings🤖 Generated with Claude Code
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com