Native / Desktop Apps
Desktop apps and CLIs integrate via the Rust SDK, with two broad approaches: embedding Nym clients on both sides of the communication (E2E), or using the Mixnet as a proxy to reach external services.
Option 1: Mixnet End-To-End
Both sides of your app run Nym clients. All traffic stays Sphinx-encrypted the entire way. Works for peer-to-peer setups or any case where you control both ends.
Stream Module
The Stream module provides AsyncRead + AsyncWrite byte streams multiplexed over the mixnet, the closest analogue to TCP sockets.
Mixnet & Client Pool Modules
The Mixnet module exposes the raw message API and MixnetClient. The Client Pool maintains pre-connected clients for bursty workloads. These are appropriate when you need full control over the communication model.
TcpProxy Module (Unmaintained)
This module is unmaintained. Use the Stream module for new projects. Existing users should plan to migrate when possible.
Exposes localhost TCP sockets that proxy traffic through the mixnet.
Option 2: Mixnet-As-Proxy
For cases where you only control the client side and need to reach a third-party service such as a blockchain RPC or remote API.
Security Considerations
Traffic is Sphinx-encrypted until the Exit Gateway, where it's unwrapped into HTTPS (Network Requester) or raw IP (IP Packet Router). The last hop to the remote host travels as normal internet traffic.
Weaker than E2E against a global passive adversary, but you still get timing obfuscation and sender-receiver unlinkability between your client and the remote service.
SOCKS Client
Applications that support SOCKS4, 4a, or 5 can use the Socks Client exposed by the Mixnet module. Traffic is routed through the Exit Gateway's Network Requester, which uses SURBs to reply to the sender anonymously.
Development is in progress to allow for this proxy method from native Rust, C, and Go without requiring a separate SOCKS client. Stay tuned.