Proxies

The Proxies page is a flat list. Import in bulk, health-probe in batch, group however you like.

Supported formats

One proxy per line, four flavors:

host:port
host:port:user:pass
http://host:port
http://user:pass@host:port

SOCKS5 works the same way (socks5://...). The parser auto-detects scheme; bare host:port is treated as HTTP.

Import

Action	What it does
Paste import	Big textarea, one-per-line.
Batch import	File picker for a .txt.
Health probe	Tests every proxy against a small target URL. Latency + status chip per row.

Where they’re used

• Social tasks: per-account proxy binding when a module needs it (CF-WAF-protected sites, captcha-gated submissions). Each burner account can be pinned to a proxy.
• HTTP transport for onchain RPC: persisted but not yet wired — proxies here don’t bind to task RPC calls. This is on the roadmap; for now, if you need geo-rotated RPC, use a service that already proxies for you (Alchemy supernode etc.).

Where they live

%LOCALAPPDATA%\zyper-suite\data\proxies.dat, DPAPI-encrypted. Username/password fields are encrypted at rest along with the rest of the line.

Health check semantics

The probe times out at a generous budget (~10s) per proxy. Failures don’t drop proxies from the list — they just mark them unhealthy. Re-run the probe later to revive ones that come back.