ProxyBase Markets¶

Category: Bandwidth Sharing | Status: Active

Website: proxybase.xyz

Referral link: the CashPilot maintainer may earn a commission from it.

Description¶

ProxyBase Markets is a SOCKS5 proxy marketplace built for AI agents. Sellers run a lightweight Rust CLI daemon that connects via WebSocket to relay buyer traffic through their internet connection, earning USDC on Tempo Chain per GB sold. Supports both direct mode (sell your own bandwidth) and upstream mode (resell external SOCKS5 proxies alongside your own connection). The official multi-arch Docker image (amd64/arm64) handles wallet creation, authentication, and seller startup automatically.

Earning Estimates¶

Earnings are based on GB sold at market rates. VPS/datacenter IPs typically earn less than residential. Multi-upstream mode can combine your own bandwidth with external proxies for additional throughput.

Requirements¶

Setup Instructions¶

1. Deploy with CashPilot¶

In the CashPilot web UI, open Catalog and click Add on the ProxyBase Markets row, or click + Add service in the top bar and pick it there. Then click Deploy ProxyBase Markets. No account signup or credentials are needed: the container auto-generates a secp256k1 wallet (BIP-39), authenticates via ECDSA challenge-response against the ProxyBase backend, creates a default seller config for direct-only mode, and starts relaying traffic.

2. Check the wallet address¶

On first start, check the container logs for your wallet address:

==> No wallet found — creating one...
Wallet created successfully!
Address: 0xb956cb455901fba57a330221bb1caa00c3ec7acb

This address receives your seller payouts. Save the mnemonic shown in the logs if you want to back up the wallet.

3. (Optional) Add upstream proxies¶

To resell external SOCKS5 proxies alongside your own bandwidth, run the container with the --upstream flag:

docker run --rm -v proxybase-data:/home/proxybase/.proxybase \
  ghcr.io/proxybasehq/proxybase-cli@sha256:007e2be8087e6926230ac69de9b23b4b9d7d195f63e0d87fd8626916c91cc268 \
  proxybase-cli seller start --foreground \
  --upstream proxy-host:1080 --upstream-user user --upstream-pass pass

This saves the upstream config to the volume. Subsequent starts without --upstream will reuse the saved config.

Docker Configuration¶

• Image: ghcr.io/proxybasehq/proxybase-cli@sha256:007e2be8087e6926230ac69de9b23b4b9d7d195f63e0d87fd8626916c91cc268 (digest-pinned; the catalog entry is authoritative if they ever differ)
• Platforms: linux/amd64, linux/arm64

Environment Variables¶

Volumes¶

The wallet, session token, and seller config are all stored in this volume. The volume holds the only copy of the wallet key: there is no server-side copy, so deleting it destroys the funds in that wallet. A new, empty wallet is generated on the next start.

Payouts¶

Payouts are managed via the CLI:

# Check your seller credit balance
docker run --rm -v proxybase-data:/home/proxybase/.proxybase \
  ghcr.io/proxybasehq/proxybase-cli@sha256:007e2be8087e6926230ac69de9b23b4b9d7d195f63e0d87fd8626916c91cc268 proxybase-cli seller status

# Lock earnings for payout (amount in microcredits, tempo_address = your Tempo wallet)
docker run --rm -v proxybase-data:/home/proxybase/.proxybase \
  ghcr.io/proxybasehq/proxybase-cli@sha256:007e2be8087e6926230ac69de9b23b4b9d7d195f63e0d87fd8626916c91cc268 proxybase-cli seller payout create --amount 1000000 --tempo-address <your-tempo-address>

# List payout history
docker run --rm -v proxybase-data:/home/proxybase/.proxybase \
  ghcr.io/proxybasehq/proxybase-cli@sha256:007e2be8087e6926230ac69de9b23b4b9d7d195f63e0d87fd8626916c91cc268 proxybase-cli seller payout list

Payments settle in USDC on Tempo via the Machine Payments Protocol (MPP). Minimum payout is $1. Tempo is an EVM chain, so any EVM address whose key you hold, such as a MetaMask one, receives the USDC with nothing to sign. Add the Tempo network to the wallet to see it.

Troubleshooting¶

Container exits with "No saved seller config"¶

The entrypoint creates a default seller_config.json on first run. If you see this error, the config file may have been deleted from the volume. Run:

docker run --rm -v proxybase-data:/home/proxybase/.proxybase \
  --entrypoint /bin/bash ghcr.io/proxybasehq/proxybase-cli@sha256:007e2be8087e6926230ac69de9b23b4b9d7d195f63e0d87fd8626916c91cc268 \
  -c 'echo "{\"upstream_proxies\":[],\"no_direct\":false}" > /home/proxybase/.proxybase/seller_config.json && chown proxybase:proxybase /home/proxybase/.proxybase/seller_config.json'

WebSocket keeps reconnecting¶

The seller auto-reconnects with exponential backoff (1s → 60s max). If it cycles indefinitely, check that:

1. Your server can reach api.proxybase.xyz on port 443 (outbound WebSocket).
2. The session token hasn't expired. The entrypoint re-authenticates on container restart if the token is missing, but long-running containers may hit token expiry. Restart the container to refresh.

How do I back up my wallet?¶

The wallet keyfile is stored at /home/proxybase/.proxybase/wallet/keyfile.enc inside the volume. For a full backup, save the mnemonic phrase printed in the container logs on first start, or back up the entire proxybase-data volume.