Peer network · supplier guide

Supply bandwidth from an Android phone, Linux box or Windows PC

PROXIES.SX pays partners for customer traffic their devices carry. You connect a device on a residential or mobile connection; it keeps an outbound connection to a relay, and when a customer session is routed through it, you earn at the rate in your partner terms.

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

Choose how you connect

Every bandwidth path uses the same relay protocol and the same farmer account; Mac compute is a separate programme with its own agent and key. Start with the hardware you already run.

How traffic reaches your device

Your device needs no open port on your router. It dials out to a regional relay, and customer sessions arrive through that connection.
Peer traffic pathCustomer application to PROXIES.SX gateway to regional relay, then through an outbound WebSocket to your device, which opens the connection to the destination website.Customer appHTTP or SOCKS5Gatewaygw.proxies.sxRegional relayEU and USYour devicephone, Linux, PCWebsitethe destinationoutbound WebSocketJWT, heartbeat 30 sEach customer session is a tunnel_connect TCP tunnel. HTTPS stays encrypted end to end; plain HTTP does not.
How customer traffic reaches a device on the peer network. The device needs no open port on your router.

A device authenticates to the relay with a short-lived token and sends a heartbeat every 30 seconds. Each customer session is a TCP tunnel: HTTPS traffic passes through still encrypted between the customer and the website; plain HTTP is not end-to-end encrypted.

A device goes on sale only after it passes the automatic test through its tunnel, including the throughput floor returned at registration (126 KiB/s on 12 October 2026), and it serves one customer session at a time. What runs on the device, and how to remove it, is explained in what runs on my device.

What you need before a device can earn

These are the steps in the supplier contract, in order.

  1. Create a farmer account

    Sign up at farmer.proxies.sx. This is the supplier dashboard; it is separate from the customer dashboard used to buy proxies.

  2. Sign Partner Agreement 2.0 in your own legal name

    Sign at farmer.proxies.sx/agreement, as an individual or as a company. We review each signed agreement, and until it is approved the relay refuses your devices with WebSocket close 1013 “Exit identity temporarily unavailable”: keep the client running, nothing needs to change, and the devices connect on a later retry after approval. You join as an independent partner, and you are responsible for your own devices, your network being lawful, and your own device, data and tax costs.

  3. Declare where your supply comes from

    In settings, describe the device owners or upstream suppliers, how the software is installed, the real country and network mix, how permission is obtained before any traffic, and how it can be withdrawn. Declarations are not independently verified KYC; identity and business verification is being prepared.

  4. Create an SDK / device key

    Listed customer traffic requires your own account-linked key (psx_…) created with the “SDK / device” preset. Anonymous registration does not qualify a device for customer traffic. A device belongs to the key that registered it: switching that key off stops the device, and registering with a different key creates a new device. Up to five keys can be active.

  5. Install on one device, then check it

    Pick a path above and start with a single device. A device registers, connects to a regional relay and receives its live rate in the earningsPerGB field. Expand only after the first device passes the self-test, is verified and listed, and has carried customer traffic. HTTP 429 means wait for Retry-After and try again; 401 and 403 do not clear by retrying: fix the key or sign the agreement first.

  6. Verification and listing

    A device goes on sale only after we have approved your signed agreement and the device has passed the automatic test through its tunnel, including the throughput floor returned as throughputContract.minKBps at registration (126 KiB/s on 12 October 2026). A device on a hosting or datacenter network is never listed as residential or mobile. Automatically verified devices are re-checked hourly, and devices are unlisted after an hour offline.

How pay is set

There is no universal public rate or percentage. What is published is how rates are applied.
IP classification and tiers
IP typeHow it is detectedTierListed for customers
Mobile carrierServer-side ASN check against mobile carrier ASNsHighestYes, needs verified cellular exits
ResidentialServer-side ASN checkMiddleYes
DatacenterServer-side ASN check against datacenter provider ASNsBaseNever as residential or mobile

The type a device reports about itself is ignored. Rates are set per partner and may be a fixed rate or a share of collected revenue; the authoritative figure is the earningsPerGB value in your device's registration response. Several devices behind one NAT may share an exit IP and do not count as separate exits.

Payout settings

Payouts are requested, not automatic. Confirm payout method, minimum and timing with support for your account.
Assets on the farmer account
Native SOL on Solana, native BTC on Bitcoin mainnet, USDC on Solana (separate settings)
Manual request floor
Approved, unclaimed earnings of at least $0.01
Device withdrawal API minimum
$5.00 for AI agents, $10.00 for Android SDK devices
Where funds go
Only to the wallet registered for that setting
Device wallet changes (withdrawal API)
Once per 24 hours, then a 7-day cooling period before payouts

Where supply is needed

Customer demand for peer supply is currently concentrated in the United States (gateway capacity API, measured 27 September 2026). Devices in other countries can register and be verified, but customer sessions follow customer demand, so listing is not the same as traffic.

What we do not offer

  • No guaranteed traffic or earnings

    Registration alone does not guarantee listing, traffic or earnings.

  • No public revenue percentage

    Terms are set per partner and read from your registration response and account.

  • No supplier referral programme

    Introductions go to maya@proxies.sx, with terms agreed in writing.

  • No lock-in

    Stop or leave at any time without notice. Recorded earnings are paid as usual.

Comparing bandwidth-sharing apps

If you are weighing this against Honeygain, EarnApp, Pawns.app or PacketStream, the bandwidth-sharing apps comparison puts published rates, payout rails, minimums and platform support side by side, each cell with its source and check date.

Questions

How much can I earn by sharing bandwidth?
There is no public rate. Rates are set per partner and may be fixed or a share of collected revenue. The live rate is the earningsPerGB value returned when your device registers, and it applies only to eligible traffic your device actually serves. Registration does not guarantee traffic or earnings.
Which connections are worth the most?
The server classifies every IP by its ASN, not by what the device reports. Mobile carrier IPs are the highest tier and residential IPs the middle tier. Datacenter IPs, including most VPS providers, are never listed as residential or mobile.
Can I run it on a VPS?
You can install the software, but a datacenter IP is never listed as residential or mobile. The peer network exists to carry residential and mobile IPs.
Where is supply needed?
Customer demand for peer supply is currently concentrated in the United States (gateway capacity API, measured 27 September 2026). A device elsewhere can still be verified, but customer sessions go where customers ask for them.
How are payouts made?
The farmer account has separate payout settings for native SOL on Solana, native BTC on Bitcoin mainnet and USDC on Solana. Saving a wallet does not send funds; you request a payout for approved earnings. Confirm payout method, minimum and timing with support for your account.
Is there a referral programme for suppliers?
No. There is no supplier referral link, code or percentage of another supplier's earnings. If you can introduce a supplier, email maya@proxies.sx and agree any terms in writing first.
Do I have to verify my identity?
You sign the agreement in your own legal name and declare your supply sources. Those declarations are not independently verified KYC today; identity and business verification is being prepared.
Can I stop at any time?
Yes. You can stop or leave without asking and without a notice period. Earnings already recorded stay on your account and are paid as usual.

Connect one device and see how it does

Create a farmer account, sign the agreement and install on a single device. Expand only after it passes the self-test, is verified and listed, and has carried customer traffic.
Create farmer account Read the supplier contract

Sources