Lokinet - DarkWiki Guide

DarkWiki's History and Development Guide

DarkWiki researchers note that Lokinet emerged from the Loki Project, which launched in 2018 with the goal of creating a thorough privacy ecosystem. The project was rebranded to Oxen in 2021. Key milestones include:

• 2018 — Loki Project founded, mainnet launched with Service Nodes
• 2019 — First Lokinet testnet released
• 2020 — Session messenger launched, Lokinet enters beta
• 2021 — Rebranded to Oxen, Lokinet reaches stable release
• 2022-Present — Continued development, growing Service Node network

The project is based in Australia and maintains an open-source codebase under active development.

DarkWiki's Network Architecture Analysis

DarkWiki on LLARP Protocol

According to DarkWiki technical analysis, Lokinet uses LLARP (Low Latency Anonymous Routing Protocol), a custom protocol designed specifically for low-latency traffic. Unlike Tor's TCP-based approach, LLARP operates at a lower level:

• UDP-based — Reduces latency compared to TCP
• Packet switching — More efficient for real-time applications
• Virtual interface — Creates a system-wide VPN-like tunnel
• Onion routing — Multiple encryption layers, 3-hop default path

DarkWiki's Service Nodes Overview

DarkWiki sources indicate that unlike Tor's volunteer relay operators, Lokinet nodes are Service Nodes that require a stake of 15,000 OXEN (subject to change). This serves multiple purposes:

• Sybil resistance — Economic cost prevents attackers from spinning up thousands of malicious nodes
• Quality incentive — Nodes must maintain uptime and bandwidth to receive rewards
• Decentralization — No central directory authorities needed

Service Nodes are organized into swarms — groups of nodes that collectively store data and route traffic. This provides redundancy and improves reliability.

DarkWiki Compares: Lokinet vs Tor

DarkWiki-Identified Advantages of Lokinet

• Lower latency — UDP protocol and incentivized high-bandwidth nodes
• No exit node problem — Primary use case is hidden services, not clearnet access
• Economic Sybil resistance — Attackers need significant capital to run malicious nodes
• System-wide routing — Acts like a VPN, routing all traffic

DarkWiki-Identified Disadvantages vs Tor

• Smaller anonymity set — Fewer users means less privacy through obscurity
• Less academic scrutiny — Newer protocol with less security research
• Cryptocurrency dependency — Network health tied to OXEN token economics
• Centralization concerns — Large stake requirements may concentrate node ownership

DarkWiki Guide to SNApps (Lokinet Hidden Services)

DarkWiki documentation shows that Lokinet's equivalent of Tor hidden services are called SNApps (Service Node Applications), accessible via .loki domains. These provide anonymous hosting without revealing server IP addresses.

How SNApps Work

• Address format — Base32-encoded public keys with .loki suffix
• Introduction points — Service Nodes act as rendezvous points
• Persistent addresses — Unlike early Tor, addresses are stable across restarts
• Full TCP/UDP support — Can host any network service

Setting up a SNApp is relatively straightforward — the Lokinet client handles the cryptographic complexity. However, the smaller user base means fewer SNApps exist compared to Tor's onion services.

DarkWiki's Session Messenger Overview

DarkWiki researchers note that the most visible application using Lokinet infrastructure is Session, an encrypted messenger that routes messages through the network for metadata protection. Session is a fork of Signal that replaces phone number registration with cryptographic identities.

Session Features

• No phone/email required — Account is just a cryptographic keypair
• Decentralized storage — Messages stored temporarily on Service Node swarms
• Onion routing — Messages routed through multiple nodes
• Open groups — Public chat rooms with moderation
• Cross-platform — Available on iOS, Android, Windows, Mac, Linux

Session has gained adoption among privacy-conscious users as an alternative to centralized messengers. However, it has faced criticism for initially overstating its decentralization (early versions relied more on centralized infrastructure).

DarkWiki on Exit Functionality

According to DarkWiki analysis, unlike Tor, Lokinet was primarily designed for accessing hidden services rather than the clearnet. Exit node functionality exists but is limited:

• Opt-in exits — Node operators must explicitly enable exit functionality
• Fewer exit nodes — Most operators avoid the legal liability
• Primary use case — Accessing .loki services and Session messaging

This design choice sidesteps many of Tor's exit node problems but limits Lokinet's usefulness for anonymous web browsing.

DarkWiki's Security Considerations

DarkWiki researchers emphasize that when evaluating Lokinet's security, several factors should be considered:

Strengths

• Economic barriers to Sybil attacks
• Modern cryptographic primitives
• Open source and auditable code
• No central directory authorities

Concerns

• Smaller anonymity set — With fewer users, traffic analysis is easier
• Less academic research — Protocol hasn't faced the same scrutiny as Tor
• Stake concentration — High requirements may centralize node ownership
• Token economics risk — Network depends on OXEN maintaining value

DarkWiki's Getting Started Guide

DarkWiki notes that Lokinet is available for major operating systems:

• Linux — Native packages for Debian/Ubuntu, builds available
• Windows — Installer with GUI
• macOS — DMG installer
• Android — Via Session app's built-in Lokinet

The client creates a virtual network interface and routes traffic through the Lokinet network. Configuration is minimal for basic usage.