Sharing Bandwidth on the Peer Marketplace:
What Suppliers Should Know

A device holds an outbound WebSocket to a regional relay, authenticated with a short-lived token. Customer HTTP and HTTPS traffic arrives as TCP tunnels over that connection, and the device sends a heartbeat every 30 seconds. No inbound port is needed. IP type is classified on the server by ASN (mobile carrier, residential or datacenter); the type a device reports about itself is ignored.

Only residential and mobile IPs can be listed for customers; datacenter IPs are rejected. A device is routed to customers only at or above a minimum speed, serves one customer session at a time, is re-verified hourly, and is unlisted after an hour offline. To see exactly what the software does on a device, read what runs on my device.

• Share bandwidth only from devices whose owners have given informed consent.
• Sign the current partner agreement in your own legal name, as an individual or a company.
• Connect with your own account-linked API key, created in the farmer dashboard. Anonymous registration does not qualify a device for listed customer traffic.
• Declare where your supply comes from: device owners or upstream suppliers, apps and installation channels, the real country and network mix, and how permission is obtained and withdrawn.
• Take responsibility for your own devices and for your network being lawful, and bear your own device, data and tax costs.

Declarations are not independently verified KYC or proof of consent. Identity and business verification is being prepared separately.

Rates are set per partner and may be fixed or a share of collected revenue. They are returned live as earningsPerGB when a device registers. There is no public percentage, and registration does not guarantee traffic or earnings: what you earn depends on eligible traffic your devices actually serve and on your active partner terms. Mobile is the highest IP tier and residential the middle. See proxies.sx/earn for the current requirements.

There is no automatic supplier-to-supplier commission. Supplier introductions go to the team by email, with any terms agreed in writing.

The farmer account has separate payout settings for USDC on Solana, native SOL on Solana and native BTC on Bitcoin mainnet. Saving a wallet or submitting a request does not send funds automatically. Manual payout requests from the farmer account can include approved, unclaimed earnings of at least $0.01. A wallet can be changed once per 24 hours, followed by a 7-day cooling period before payouts.

The supplier contract is published at agents.proxies.sx/peer/skill.md and overrides this article where they differ.