MetaScalp + PingNitro: set up in 3 steps

CScalp

1. Open the "Connections" window (CScalp settings → "Connections") → the "My proxies" button.
   What you should see: the "My proxies" window is open.
2. "Add proxy": any name (for example, PingNitro), IP address 127.0.0.1, port 1081, leave login and password empty → "Add".
   What you should see: PingNitro is in the "My proxies" list.
3. In the "Connections" window, in the "Proxy" column of Binance (USDⓈ-M and Spot), OKX and other exchanges, select PingNitro. Leave Bybit and BingX on "Direct connection" — the route to their servers is shorter that way. The proxy is set for each connection separately — check every row of the list (it scrolls): Binance USDⓈ-M, Binance Spot, OKX and the rest. The PingNitro app does not yet tell CScalp connections apart and says "CScalp — full stream via PingNitro" even if only one of them goes through PingNitro.
   What you should see: the "Proxy" column shows PingNitro for every exchange you need, and the "Speed" column shows a noticeably lower latency to Binance.
4. Be sure to restart CScalp (close it and open it again) — every time you change the proxy: otherwise the connections that are already open stay direct. Done — compare the feed before and after (for example, with the test on our site).
   What you should see: the terminal shows a connection to the exchange.

Tiger.com (Tiger.Trade)

1. Main menu "File" → "Connections" → "Configure".
   What you should see: the "Connections" window with your exchanges is open.
2. In the "Connections" window click the "Proxy" button (top right) → "Add proxy": any name (for example, 1081), "Proxy settings" — 127.0.0.1:1081, login and password empty → "Apply".
   What you should see: your proxy 127.0.0.1:1081 is in the proxy list.
3. In the connections list, in the "Proxy" column of every Binance connection (futures and spot), select the proxy you created.
   What you should see: the "Proxy" column of the Binance connections shows your proxy (1081 in the screenshot).
4. If the Binance connection settings have the checkboxes "Use proxy for market data" (feed and order book — the main gain), "…for user data" and "…for orders", turn on all three. For OKX — both.
   What you should see: both the feed with the order book and your orders go through the proxy.
5. Be sure to restart Tiger.com (close it and start it again) — every time you change the proxy: otherwise connections that are already open stay direct, not through the proxy.
   What you should see: the terminal shows a connection to the exchange.

Vataga.terminal (EasyScalp)

1. The gear icon in the program header → the "Proxy" tab → "Add proxy".
   What you should see: the "Proxy" tab is open.
2. Host (the "Address" field) — 127.0.0.1, Port — 1081, login and password empty. Save. (The switch for Vataga's own services, «Для сервисов Vataga…» in the Russian interface, is not needed — leave it as it is.)
   What you should see: the proxy 127.0.0.1:1081 is saved.
3. The "Connections" tab → choose the exchange connection → in its "Proxy" field choose the proxy you created.
   What you should see: the exchange connection has the proxy you created selected.
4. "Proxy mode" — "Full stream" (both the feed with the order book and your orders go through the route; in the "Orders only" mode the feed stays slow).
   What you should see: the proxy mode is "Full stream".
5. Click the button in the connection header — the green "Connected" indicator lights up. If the exchange was already connected or you changed the proxy, be sure to restart Vataga (close it and open it again).
   What you should see: the green "Connected" indicator is lit in the header.

MetaScalp

1. Settings → the "Proxy" tab → the "Add proxy server" section.
   What you should see: the "Add proxy server" section is open.
2. Name — PingNitro, IP address — 127.0.0.1, port — 1081, login and password empty → "Add".
   What you should see: the proxy PingNitro (127.0.0.1:1081) is added.
3. In the exchange connection, choose PingNitro in the "Proxy" drop-down.
   What you should see: the exchange connection has PingNitro selected.
4. Be sure to restart MetaScalp (close it and open it again) — every time you change the proxy: otherwise connections that are already open stay direct.
   What you should see: the exchange label is green — the terminal is connected to the exchange.

Any other terminal

Any program that lets you set a proxy for the exchange connection will do: look for "Proxy" in the connection settings. Type — HTTP (if you have a choice, SOCKS5 works too), address 127.0.0.1, port 1081, no login. If the proxy can be enabled separately for "market data" and "orders", enable it for both — the feed gets faster only when it goes through the route. Once you have set or changed the proxy, be sure to restart the terminal (close it and open it again). If the proxy is set for each connection separately, check all of them.

Your own bot or script

# Python + ccxt
import ccxt
ex = ccxt.binanceusdm({"apiKey": "...", "secret": "..."})
ex.httpsProxy = "http://127.0.0.1:1081/"   # REST
ex.wsProxy    = "http://127.0.0.1:1081/"   # WebSocket (ccxt.pro)

# curl - check the route
curl -x http://127.0.0.1:1081 https://fapi.binance.com/fapi/v1/time

The PingNitro client accepts HTTP, SOCKS5 and SOCKS4 on a single port, 1081.