Warpnet Overlay SOCKS5 Proxy for Telegram

Warpnet supports Telegram connectivity through a SOCKS5 proxy built on top of the Warpnet overlay network.

In this setup, Telegram traffic is not sent directly to the public internet from the client. Instead, it is first routed through a Warpnet bootstrap node, then forwarded through the encrypted overlay to another Warpnet node, which acts as the egress point and connects to Telegram servers.

A typical traffic path looks like this:

Telegram client → Warpnet bootstrap enter node → encrypted Warpnet overlay → remote Warpnet bootstrap exit node → Telegram servers

This design allows Telegram traffic to traverse the Warpnet peer-to-peer network before leaving through a remote node.

How it works

The client connects to a SOCKS5 endpoint exposed by a Warpnet bootstrap node HOSTED IN A CENSORED COUNTRY. That node accepts the client connection, encapsulates the traffic into the Warpnet overlay transport, and forwards it to another Warpnet node in different country selected as the exit point. The remote node then opens the outbound connection to Telegram servers and relays responses back through the same encrypted path.

From the user’s perspective, Telegram only needs standard SOCKS5 settings. No client-side Warpnet integration is required beyond the proxy configuration.

Deployment guide

1. Download the bootstrap node binary from the Warpnet releases page:

https://github.com/Warp-net/warpnet/releases

Alternatively, build it from source:

go build -o bootstrap ./cmd/bootstrap/main.go

2. Deploy the bootstrap node to a server.

Use any Linux host with a public IP address and open inbound access to the SOCKS5 port you want to expose.

3. Start the bootstrap node and configure its SOCKS5 listener.

At minimum, you need:

• server host or IP

• SOCKS5 port

• username (hardcoded 'warpnet')

• pre-shared key

Make sure the node is reachable from the client and that the chosen port is allowed by the firewall.

4. Configure Telegram to use the SOCKS5 proxy.

Telegram supports SOCKS5 natively. Fill in the server, port, username, and password from your bootstrap node configuration.

You can also use a ready-made Telegram proxy link in this format:

https://t.me/socks?server=<YOUR_ENTER_NODE_HOST>&port=4080&user=warpnet&pass=<YOUR_PSK>

Replace:

• <YOUR_ENTER_NODE_HOST> with your server hostname or IP

• 4080 with your SOCKS5 port if different

• <YOUR_PSK> with your pre-shared key (to get it run node with flag '--node.print-psk')

When opened on a device with Telegram installed, this link prefills the SOCKS5 proxy settings.