WINDOWS PEER SDK - FLEET DEPLOYMENT GUIDE

LEGACY NATIVE .EXE - SEPARATE RELEASE

30-second setup

1. Unzip the native zip anywhere (e.g. C:\proxies-peer).
2. Right-click start.bat → Edit, paste your psx_ key into the API_KEY line, save.
3. Double-click start.bat. Done - no install of anything.

The device name is auto-set to the PC name (%COMPUTERNAME%) - stable + unique per machine, so restarts reuse the same device (no duplicate-device churn). start.bat auto-restarts on exit. Or run the exe directly with your own flags:

proxies-peer.exe -key=psx_YOUR_KEY -name=my-rig-01

Community Edition - open-source, MIT, provided AS IS (not a warranted Proxies.sx product). This older native archive was built from a Go client; it has not been rebuilt for the current Linux Go 1.6.8 release. A Linux build or Node test does not validate Windows socket behavior. Deliberately not UPX-packed: packing would halve the size but trips Windows Defender heuristics on networked binaries, which would block installs. 5 MB + clean beats 2 MB + quarantined.

NODE.JS PACKAGE 1.6.6

Use this Node.js package for the one-socket default and retained relay-selection fixes and existing retry/target-safety protection. It requires Node.js; those changes are not included in the older native download above.

A ready-to-run Windows package that shares your internet connection's bandwidth and earns USDC. It speaks the complete Proxies.sx relay protocol - identical wire format to the Node, Go, and Android SDKs The Node.js package includes batch scripts for setup and launch; it opens a terminal window while running.

• Registers once and reuses the same device identity across restarts
• Connects to the nearest relay over WebSocket (server-driven geo-routing + relay_redirect)
• Opens parallel WebSockets for throughput, heartbeats every 30s
• Forwards customer tunnels (raw TCP, TLS stays end-to-end), reports failures fast
• start.bat auto-restarts the peer if it ever stops - close the window to stop sharing

Requires Node.js LTS (free, one-time install). Download: proxies-peer-windows-node-1.6.6.zip.

UPDATE WITHOUT REPLACING YOUR DEVICE

Stop the existing window or service once and back up its folder. Replace the package files in that same folder, preserving config.json, .sx-peer-state.json, the API key, agent name and any PEER_STATE_FILE override. Run setup.bat, then the same start.bat. The archive contains no live configuration or identity. Run only one copy. To roll back, restore the backed-up package files while retaining configuration and state.

Verify the archive against SHA256SUMS. During congestion, changing only wsConnections to 1 in existing config reduces connection attempts; an existing WS_CONNECTIONS environment override wins. It does not guarantee admission. Do not repeatedly restart or register a new identity because of HTTP 429.

QUICK START (single machine)

1. Install Node.js - grab the "LTS" installer from nodejs.org, accept the defaults. (One time, ~1 min.)
2. Download & unzip proxies-peer-windows-node-1.6.6.zip into a folder, e.g. C:\proxies-peer.
3. Double-click setup.bat - it checks Node, installs the one dependency, and creates config.json from the template.
4. Open config.json in Notepad and paste your psx_ API key (create the SDK / device preset at farmer API keys). Set a unique agentName (see Stable Identity).
5. Double-click start.bat. You'll see:

[REGISTERED] device=agent_... relay=wss://relay.proxies.sx sockets=1
[CONNECTED]  device=agent_...
[ACK] relay confirmed connection

CONFIGURATION (config.json)

setup.bat writes config.json from config.example.json. Edit it in any text editor:

{
  "apiKey": "psx_YOUR_API_KEY",     // required - farmer SDK / device key
  "agentName": "my-windows-rig",    // STABLE + UNIQUE per machine (see below)
  "walletAddress": "",              // optional USDC payout wallet
  "country": "US",                  // ISO-2 hint (server verifies the real IP)
  "carrier": "unknown",             // optional
  "wsConnections": 1,               // parallel relay sockets (1-5; default 1)
  "connectionMethod": "windows",    // leave as-is (shows correctly on dashboard)
  "verbose": false                  // true = log every tunnel open/close
}

STABLE IDENTITY - THE #1 FLEET RULE

One machine = one entry in config.json with one stable agentName (office-pc-01, office-pc-02, …). The package also saves a state file next to peer.js so identity survives even before the name hash is needed - don't delete it.

RUN AS A WINDOWS SERVICE (survives reboot / logout)

start.bat already auto-restarts on crash, but the window must stay open. To run headless and survive reboots, install it as a service with the free NSSM (Non-Sucking Service Manager):

:: From an elevated (Administrator) Command Prompt, in the unzipped folder:
nssm install ProxiesPeer "C:\Windows\System32\cmd.exe" "/c C:\proxies-peer\start.bat"
nssm set ProxiesPeer AppDirectory C:\proxies-peer
nssm set ProxiesPeer Start SERVICE_AUTO_START
nssm start ProxiesPeer

:: Manage it:
nssm status ProxiesPeer
nssm restart ProxiesPeer
nssm stop ProxiesPeer

Alternative: Task Scheduler (no extra download)

:: Run at startup, restart if it ever exits, no visible window:
schtasks /create /tn "ProxiesPeer" /tr "C:\proxies-peer\start.bat" ^
  /sc onstart /ru SYSTEM /rl HIGHEST /f

Both keep the peer online across reboots with zero device churn, because agentName + the state file are fixed.

FLEET DEPLOYMENT - MANY MACHINES

Device limit

Accounts scale to 200,000 devices - real fleets are welcome. The only limit that bites is an anti-flood guard on unproven devices: at most 20,000 that have never served traffic (and aren’t yet verified). The moment a device serves a byte or passes verification it stops counting against that guard, so a fleet that’s actually earning grows freely to the full 200k. A flood of random-named ghosts (which never serve) simply parks at 20,000 and goes no further. The rule is the same either way: give every machine a stable, unique name so it reconnects as one device instead of spawning a ghost on each restart. Need more than 200k genuine nodes? Email agents@proxies.sx.

Deploy to N machines (same key, unique name each)

1. Unzip the package once, fill in config.json with your shared apiKey but leave agentName as a placeholder.
2. Push the folder to each machine (GPO, PDQ Deploy, Intune, a network share, or a USB stick).
3. On each machine set a unique name - a one-liner that stamps the hostname in is the easiest:

:: per-machine: set agentName = the PC's hostname (unique by definition)
powershell -Command "(Get-Content config.json) -replace 'my-windows-rig', $env:COMPUTERNAME | Set-Content config.json"
:: then install the service (see above) and start it

Multiple distinct uplinks on one box

Only if a single PC truly has several separate connections (e.g. multiple USB modems), copy the folder once per uplink into its own directory (C:\peer-modem-1, C:\peer-modem-2), each with its own unique agentName and its own service. One uplink = one instance.

STANDALONE .EXE (no Node.js on target machines)

The package ships build-exe.bat. Run it once on a build machine (with Node installed) to produce a single proxies-peer.exe you can copy to machines that don't have Node:

:: produces dist\proxies-peer.exe (bundles Node + peer.js)
build-exe.bat

:: on target machines, just drop the exe next to a config.json and run:
proxies-peer.exe

Identity rules are unchanged - the exe still reads config.json and persists the state file beside itself.

HOW IT WORKS (protocol, in order)

1. Register   POST /v1/peer/agents/register {name, type:"custom", apiKey, sdkVersion}
              -> { deviceId, token|jwt, refreshToken, relay, earningsPerGB }
              deviceId = SHA-256(apiKey + ":" + agentName)  (stable across restarts)
2. Connect    wss to register.relay, JWT in Sec-WebSocket-Protocol as token.<jwt>
              (NEVER in the URL). Opens wsConnections parallel sockets.
3. device_info  announce {country, protocol:"binary-v1", supportsRelayRedirect:true}
4. Heartbeat  every 30s
5. tunnel_connect  open raw TCP to target host:port, stream bytes both ways.
              HTTPS stays end-to-end - the peer never sees plaintext.
6. relay_redirect  server can move you to a nearer relay; the pool reconnects there.

This package speaks the same protocol as reference-sdk.js - if you'd rather script it yourself, the Node and Go pages document the protocol identically.

EARNINGS REALITY (read before scaling)

• You're paid per GB of customer traffic your node serves, by IP type: mobile > residential > datacenter. Live rate is the earningsPerGB field in the register response (and on the dashboard).
• Read the current routing speed floor from throughputContract.minKBps in the registration response (KiB/s, 1024 bytes per second per unit). The floor is configurable; verification alone does not establish usable speed. Latency, quality, country, consent and account checks also apply.
• One fast node on a real connection >> many slow ones splitting one line. Build for throughput per distinct IP, not raw machine count.
• CONNECTED → VERIFIED → LISTED → ROUTABLE → EARNING are separate states. Listing requires current measurements and all eligibility checks; timing varies with the probe queue and recovery backoff. Earnings require billable customer traffic.

LINKS