Skip to content

Conversation

@wpaulino
Copy link
Contributor

@wpaulino wpaulino commented Mar 7, 2020

This allows Loop users to further improve their privacy by not revealing their source IP address. Note that the identity of the lnd node behind Loop can still be revealed when performing a Loop In due to the swap server extending an off-chain HTLC to the user.

Onion addresses don't yet exist for the swap servers, but they will be added at a later time.

This allows Loop users to further improve their privacy by not revealing
their source IP address. Note that the identity of the lnd node behind
Loop can still be revealed when performing a Loop In due to the swap
server extending an off-chain HTLC to the user.

Onion addresses don't yet exist for the swap servers, but they will be
added at a later time.
Copy link
Contributor

@guggero guggero left a comment

Choose a reason for hiding this comment

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

Nice work! Was able to test this and seems to work fine on testnet.
One thing I noticed when testing in conjunction with LSAT is that we need to allow attaching macaroons to insecure requests. I created #167 to address that.

Copy link
Member

@Roasbeef Roasbeef left a comment

Choose a reason for hiding this comment

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

LGTM 🥂

@Roasbeef Roasbeef merged commit bb38cf5 into lightninglabs:master Mar 15, 2020
@wpaulino wpaulino deleted the swap-server-over-tor branch March 16, 2020 17:39
@joostjager joostjager added this to the 0.6.0 milestone Apr 27, 2020
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.

4 participants