Device guide · Windows · Node.js client 1.6.0

Run a bandwidth-sharing peer on Windows

On Windows the PROXIES.SX peer is a small Node.js program you can read before running. Install Node.js, run setup.bat, put your SDK / device key in config.json, then keep start.bat running. It works on Windows 10 and 11 and Windows Server.

Registration does not guarantee traffic or earnings. Earnings depend on eligible traffic your devices actually serve and on your active partner terms.

Checked on against our published supplier terms

What is in the zip

We downloaded the package from agents.proxies.sx on 27 September 2026 and read every file.
File
proxies-peer-windows.zip, 15,046 bytes
SHA-256
3b5e75806237b59ef42c899f0d97778a1394b4b8b478b002e238c4b9a027cc27
Client version
peer.js SDK_VERSION 1.6.0
Dependency
ws (WebSocket library), installed by setup.bat
Licence
MIT
Executables
None shipped. Batch files and JavaScript only.
Files in the package
FileWhat it does
setup.batChecks for Node.js, runs npm install --omit=dev, copies config.example.json to config.json if missing
start.batChecks setup, runs node peer.js, and restarts it 10 seconds after any exit
peer.jsThe whole relay-protocol client (about 24 KB of JavaScript)
config.example.jsonSettings template
build-exe.batOptional: packages a standalone proxies-peer.exe with pkg (Node 18, win-x64)
README.mdSetup, auto-start and troubleshooting notes

Set it up

  1. Create your account, declaration and key

    In the farmer dashboard, sign the agreement, complete the supply-source declaration and create an SDK / device key. Only share a connection whose owner has given informed consent.

  2. Install Node.js

    Download the LTS installer from nodejs.org and accept the defaults. The client needs Node.js 18 or later.

  3. Download and check the zip

    Download only from agents.proxies.sx and compare the SHA-256 with the value above before unzipping.
    Command Prompt
    curl -fLO https://agents.proxies.sx/peer/proxies-peer-windows.zip
certutil -hashfile proxies-peer-windows.zip SHA256

  4. Run setup.bat

    It installs the one dependency and creates config.json from the template. It leaves an existing config.json untouched.

  5. Add your key to config.json

    Open config.json in Notepad and set apiKey to your psx_ key. Environment variables such as API_KEY override the file.
    config.json template
    {
  "apiKey": "psx_REPLACE_WITH_YOUR_API_KEY",
  "agentName": "my-windows-rig",
  "walletAddress": "",
  "country": "US",
  "carrier": "unknown",
  "wsConnections": 4,
  "connectionMethod": "windows",
  "verbose": false
}

  6. Run start.bat and keep it running

    Leave the window open. You should see [REGISTERED], [CONNECTED] and [ACK]. A device has to stay online to be verified: at least an hour online and a quality score of 50 or more.

config.json settings

From README.md in the package.
Settings
FieldDefaultWhat it does
apiKeyrequiredYour SDK / device key
agentNamemy-windows-rig (template)Name shown in your dashboard. Give every PC its own unique name: the server derives device identity from the key and the name
walletAddressemptyOptional payout wallet; can be set in the dashboard instead
countryUSA hint only; the server verifies the real IP
wsConnections4Parallel relay sockets, clamped to 1-5 (the relay allows 6 per device)
verbosefalseLogs every tunnel open and close

Start with Windows

The README documents two options. start.bat already restarts the client if it stops.

Task Scheduler: create a task that runs whether or not you are logged on, triggered at start-up, with the full path to start.bat as the program.

As a service with NSSM: from an Administrator Command Prompt, install cmd.exe /c with the path to start.bat as a service, then start it. Stop it with nssm stop ProxiesPeer.

Command Prompt (Administrator)
nssm install ProxiesPeer "C:\Windows\System32\cmd.exe" "/c C:\path\to\start.bat"
nssm start ProxiesPeer

Before you run it

Malware has been documented installing legitimate bandwidth-sharing clients without the owner's knowledge, and security products classify some of this software as potentially unwanted. Download only from agents.proxies.sx, compare the hash, and run it only on a computer and connection you are entitled to share. What the client does on your machine, and what it does not, is set out in what runs on my device.

A home connection can be listed. A cloud VM cannot, because datacenter IPs are rejected for listing.

Questions

Is there a Windows bandwidth-sharing client that I can read before running?
Yes. The PROXIES.SX Windows package is not an installer: it is a 15 KB zip of plain-text files, the Node.js peer client 1.6.0 (peer.js) and three batch files, under the MIT licence. You can read every line before running it.
Do I need Node.js?
Yes, to run it as shipped. setup.bat stops if Node.js is missing and points you to the LTS installer at nodejs.org; package.json requires Node.js 18 or later. An optional build-exe.bat can package a standalone .exe, which itself needs Node.js to build.
Where do I get the API key?
Create an SDK / device key in the farmer dashboard at farmer.proxies.sx (API keys, "SDK / device" preset). The text inside setup.bat and README.md still points to client.proxies.sx; the supplier contract names the farmer dashboard as the place to create supplier keys.
Will my antivirus flag it?
We have not tested it against antivirus products. Security vendors do classify some bandwidth-sharing software as potentially unwanted, so download only from agents.proxies.sx and compare the SHA-256 on this page before running anything.
Why does it say CONNECTED but show no earnings?
Connected is only the first stage. A device needs at least an hour online and a quality score of 50 or more for auto-approval, must be on a residential or mobile IP, and customer sessions follow customer demand. Registration does not guarantee traffic or earnings.
How do I stop sharing?
Close the start.bat window: the script prints "Close this window to stop sharing completely." Remove any scheduled task or service you created, delete the folder, and remove the device from the farmer dashboard.

Set up one Windows PC

Create a farmer account and an SDK / device key, run the client on one residential connection, and check it is verified before adding more machines.
Create farmer account Read the supplier contract

Sources