Loki is becoming Oxen! Check out our announcement blog, or head over to oxen.io for a glimpse at the future of the Loki Project! Note: All posts, other information, and download links on loki.network are up-to-date and relevant. For any queries, you can find us on Telegram or contact us via email.
Lokinet exit nodes, Lokinet exit nodes: Onions gone wild

Lokinet exit nodes: Onions gone wild

Lokinet exit nodes have been on the bucket list for Lokinet since launch — and this week, exits have entered the building.

That’s right, this is not a drill, Lokinet exit node functionality is making its way to a Lokinet client near you. If you’ve been following Lokinet for a while, you’ll know just how big of a deal this is. But if you’re new to the Lokinet landscape, or just want to brush up on the basics of onion routing, you’ve come to the right place.

Lokinet exit nodes: How they work, what they do, and what they mean for you

In a nutshell, Lokinet exit nodes allow you to onion-route all your internet traffic over Lokinet. Every site you browse, every meme you share, every video you stream — all that traffic is completely anonymised by Lokinet’s onion routing. With exit nodes, Lokinet functions similarly to a VPN — but better. Let’s break down how all that works.

When you enable exit node browsing and connect to an exit node through the Lokinet client, your traffic is encrypted multiple times, once for every node it will travel through, then sent to a Lokinet “edge node” — your entry point to the Lokinet network. That node forwards your traffic through the network until it reaches a “pivot node”, which knows the location of the exit node you’re connecting to. That pivot node then relays your traffic — still fully encrypted — to the exit node. The exit node then decrypts your traffic and forwards it to its destination. The process for incoming traffic is the same in reverse.

Lokinet exit nodes, Lokinet exit nodes: Onions gone wild
A typical Lokinet exit node path

But hold on a minute. The exit node decrypts your traffic? How anonymous can this be if the exit node knows what you’re sending and receiving?

The answer is simple: the exit node may know what traffic is passing through it, but  it never knows who is sending or receiving that traffic. If you connect to a Lokinet exit node to send dankmeme.gif to someone on Facebook, the exit node may know that you’re sending something to someone on Facebook — but it won’t know who is sending it. And if the traffic is secured using HTTPS, the node won’t know exactly what you’re sending, either. Your ISP will know that you’re connected to Lokinet, but they won’t know whether you’re even connected to an exit node. And because Lokinet is fully decentralised, unlike VPN providers, there’s no central authority that can log your IP address, even if they wanted to.

When you’re browsing through a Lokinet exit node, no other server, anywhere on the internet, ever gets the complete picture about what you’re accessing. The first Lokinet node you connect to will know your IP address, but because your traffic is already fully encrypted, that node won’t know what you’re sending or receiving — all they know is that you’re using Lokinet in some way. The nodes in between that node and the exit node know absolutely nothing — they can’t see your IP or the contents or destination of the traffic they’re relaying; all they see are unreadable packets of data that they need to pass along the chain. And the exit node decrypts your traffic, but that node has no clue who sent it. Full anonymity, powered by Lokinet.

Lokinet exit node release: What works, what doesn’t, and what we want to know

In a nutshell, everything should “just work”. You should be able to enter an exit node’s details in the Lokinet client, enable it, and voila — you should be browsing the clearnet through Lokinet. You can check whether it’s working by using a site like WhatsMyIP: load it up before connecting to an exit node, check your IP, connect to an exit node and check your IP again. You should see your IP change once you’re browsing via Lokinet.

Wondering where to find those exit node details? There’s currently one exit node available, accessed via this address: exit.loki

However, there are a few provisos. There may be some service disruptions during this initial period, as until more nodes become available, everyone will be using the same exit node — the node may experience performance bottlenecks with all that traffic running through it. And if you’re hoping to use Lokinet exits to stream Netflix, you may run into issues. Netflix blocks most known VPS providers, so depending on where the exit node you’re using is hosted, you might not be able to anonymously catch up on Stranger Things.

We’ll be keeping our ears to the ground for any and all bug reports and other issues you might encounter. If you run into any issues with the GUI, problems connecting to or using exit nodes, or anomalous CPU or memory usage, let us know and we’ll look into it. We’d also love to see some SpeedTest results with exit nodes enabled — it should be pretty smooth, but the proof is in the pudding. And if you have any other feedback, questions, or suggestions, don’t hesitate to reach out.

Happy anonymous browsing!

Leave a Comment

Your email address will not be published. Required fields are marked *