feat: add SOCKS5/HTTP proxy support by croll83 · Pull Request #21 · Polymarket/polymarket-cli

croll83 · 2026-02-25T17:45:10Z

Summary

Adds --proxy global CLI flag for SOCKS5/HTTP proxy (e.g., --proxy socks5://127.0.0.1:1080)
Reads POLYMARKET_PROXY env var as fallback when flag is not provided
Enables reqwest socks feature for SOCKS5 protocol support

Motivation

The Polymarket CLOB geoblocks certain regions. Users behind VPNs or corporate proxies need a way to route CLI traffic through a SOCKS5 or HTTP proxy. Currently reqwest is compiled without socks support, so standard proxy env vars (ALL_PROXY, HTTPS_PROXY) don't work with SOCKS5 URLs.

Changes

Cargo.toml: Added reqwest with socks feature (Cargo unifies features across dependency tree)
src/main.rs: Added --proxy global flag + POLYMARKET_PROXY env var resolution, sets HTTPS_PROXY/HTTP_PROXY before client initialization

Usage

# Via flag
polymarket --proxy socks5://127.0.0.1:1080 markets search "Bitcoin"

# Via env var
POLYMARKET_PROXY=socks5://127.0.0.1:1080 polymarket markets search "Bitcoin"

# HTTP proxy also works
polymarket --proxy http://proxy.example.com:8080 clob balance

Note

Medium Risk
Changes process-wide proxy environment handling and early startup/runtime initialization, which can affect all outbound networking behavior if misconfigured; scope is otherwise contained to CLI/config plumbing and output renames.

Overview
Adds SOCKS5/HTTP proxy support via a new global --proxy flag plus POLYMARKET_PROXY/config-file fallback, and enables reqwest’s socks feature to make SOCKS URLs work.

Moves proxy resolution to happen before the Tokio runtime starts and sets HTTP_PROXY/HTTPS_PROXY (with NO_PROXY exclusions for Polygon RPC) so only API traffic is proxied; also extends config schema to persist an optional proxy value and avoids treating an empty stored private_key as configured.

Separately, wallet/setup output is generalized from “proxy wallet” to “trading wallet” by deriving the address based on signature type (proxy vs gnosis-safe vs EOA) and renaming JSON fields accordingly.

^{Written by Cursor Bugbot for commit 489d83e. This will update automatically on new commits. Configure here.}

…ROXY env var

src/main.rs

cursor · 2026-02-25T18:03:30Z

Cargo.lock

 "dirs",
 "polymarket-client-sdk",
 "predicates",
+ "reqwest 0.13.2",


Cargo.lock missing tokio-socks, SOCKS feature not compiled

High Severity

Cargo.toml declares reqwest with features = ["socks"], which requires the tokio-socks optional dependency. However, tokio-socks is completely absent from Cargo.lock — searching for "socks" yields zero results. The lock file appears to have been manually edited (only adding the "reqwest 0.13.2" line) rather than regenerated by cargo. This means the socks feature isn't actually compiled in, so SOCKS5 proxy support silently doesn't work.

Additional Locations (1)

Cargo.toml#L25-L26

src/main.rs

…ARKET_PROXY env > config file)

Address review feedback: - Move from #[tokio::main] to sync fn main() so set_var runs before any worker threads are spawned (eliminates UB on Rust 2024 edition) - Add NO_PROXY=polygon.drpc.org,drpc.org to exclude Polygon RPC from SOCKS5 proxying — alloy depends on reqwest 0.12 which lacks socks support and would fail if HTTP(S)_PROXY points to a socks5:// URL - Build tokio runtime manually with Builder::new_multi_thread() Tested: CLOB calls route through SOCKS5, approve check (alloy RPC) bypasses proxy and queries Polygon directly.

croll83 · 2026-02-25T18:17:04Z

all valid points!

The third commit (e690e5f) addresses all 3 Cursor bot review issues:

Issue	Fix
set_var after tokio spawns threads (UB)	Converted to sync fn main() — env vars set before Builder::new_multi_thread().build()
tokio-socks missing from Cargo.lock	Resolved automatically on build (reqwest socks feature pulls it in)
Global SOCKS5 breaks alloy reqwest 0.12	Added NO_PROXY=polygon.drpc.org,drpc.org to exclude Polygon RPC from proxying

Verified on server:

✅ polymarket status → API OK (through SOCKS5 proxy)
✅ polymarket clob balance → $5.49 (CLOB calls go through proxy)
✅ polymarket approve check → All contracts approved (alloy RPC bypasses proxy via NO_PROXY)

src/config.rs

src/main.rs

Address cursor bot review: - save_wallet now reads existing proxy from config before overwriting, preventing silent loss of user-configured proxy URL - resolve_key treats empty string from config as None, so callers get the helpful "No wallet configured" message instead of a confusing "Invalid private key" error when private_key is absent from config

cursor · 2026-02-25T20:48:12Z

src/main.rs

+        unsafe {
+            std::env::set_var("HTTPS_PROXY", url);
+            std::env::set_var("HTTP_PROXY", url);
+            std::env::set_var("NO_PROXY", "polygon.drpc.org,drpc.org");


NO_PROXY overwrites existing user environment variable values

Medium Severity

Setting NO_PROXY to a hardcoded value unconditionally replaces any existing NO_PROXY entries the user already has in their environment. Since this feature specifically targets corporate/VPN users — who commonly have NO_PROXY configured for internal services — this overwrites those entries within the CLI process. The existing entries need to be preserved by reading the current NO_PROXY value and appending polygon.drpc.org,drpc.org to it rather than replacing it.

cursor · 2026-02-25T20:48:12Z

src/config.rs

+/// Priority: CLI flag > env var > config file.
+pub fn resolve_proxy(cli_flag: Option<&str>) -> Option<String> {
+    if let Some(url) = cli_flag {
+        return Some(url.to_string());


Empty proxy string not filtered from CLI flag

Low Severity

resolve_proxy filters empty strings for the POLYMARKET_PROXY env var path (via !url.is_empty()) but does not apply the same check to the CLI flag path or the config file path. An empty --proxy "" value or an empty proxy string in the config file would result in setting HTTPS_PROXY and HTTP_PROXY to empty strings, likely causing confusing request failures.

…pport) wallet show/create/import now use the configured signature_type to derive the correct trading wallet address: - "proxy" → EIP-1167 minimal proxy (Magic/email wallets) - "gnosis-safe" → Gnosis Safe 1-of-1 (browser/MetaMask wallets) - "eoa" → no derived wallet, use EOA directly Previously all wallet commands hardcoded derive_proxy_wallet(), ignoring the signature_type setting entirely. This caused the CLI to show the wrong deposit address when using gnosis-safe mode (which is what polymarket.com creates for browser wallet users). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

scripts/recover-proxy-funds.js

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

cursor · 2026-02-26T00:48:29Z

Cargo.toml

 tabled = "0.17"
 rust_decimal = "1"
 anyhow = "1"
+reqwest = { version = "0.13", features = ["socks"] }


Cargo.lock missing tokio-socks breaks SOCKS5 proxy support

High Severity

The Cargo.toml adds reqwest with features = ["socks"], but the committed Cargo.lock does not contain tokio-socks anywhere — the required transitive dependency for SOCKS5 support. The reqwest 0.13.2 entry in the lockfile lists no socks-related dependencies. This means builds using cargo install --locked or CI with --locked will compile reqwest without actual SOCKS5 support, silently making the PR's core feature non-functional at runtime.

Additional Locations (1)

Cargo.lock#L3464-L3503

feat: add SOCKS5/HTTP proxy support via --proxy flag and POLYMARKET_P…

d3d1f23

…ROXY env var

cursor bot reviewed Feb 25, 2026

View reviewed changes

croll83 added 2 commits February 25, 2026 18:06

feat: read proxy URL from config file (priority: --proxy flag > POLYM…

5acf9f7

…ARKET_PROXY env > config file)

cursor bot reviewed Feb 25, 2026

View reviewed changes

src/config.rs Outdated Show resolved Hide resolved

src/config.rs Show resolved Hide resolved

src/main.rs Show resolved Hide resolved

cursor bot reviewed Feb 25, 2026

View reviewed changes

scripts/recover-proxy-funds.js Outdated Show resolved Hide resolved

scripts/recover-proxy-funds.js Outdated Show resolved Hide resolved

croll83 force-pushed the feat/socks-proxy-support branch from 586b4ba to 489d83e Compare February 25, 2026 23:56

cursor bot reviewed Feb 26, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: add SOCKS5/HTTP proxy support#21

feat: add SOCKS5/HTTP proxy support#21
croll83 wants to merge 5 commits intoPolymarket:mainfrom
croll83:feat/socks-proxy-support

croll83 commented Feb 25, 2026 •

edited by cursor bot

Loading

Uh oh!

Uh oh!

cursor bot Feb 25, 2026

Uh oh!

Uh oh!

croll83 commented Feb 25, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cursor bot Feb 25, 2026

Uh oh!

cursor bot Feb 25, 2026

Uh oh!

Uh oh!

Uh oh!

cursor bot left a comment

Uh oh!

cursor bot Feb 26, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

croll83 commented Feb 25, 2026 • edited by cursor bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Motivation

Changes

Usage

Uh oh!

Uh oh!

cursor bot Feb 25, 2026

Choose a reason for hiding this comment

Cargo.lock missing tokio-socks, SOCKS feature not compiled

Uh oh!

Uh oh!

croll83 commented Feb 25, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cursor bot Feb 25, 2026

Choose a reason for hiding this comment

NO_PROXY overwrites existing user environment variable values

Uh oh!

cursor bot Feb 25, 2026

Choose a reason for hiding this comment

Empty proxy string not filtered from CLI flag

Uh oh!

Uh oh!

Uh oh!

cursor bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor bot Feb 26, 2026

Choose a reason for hiding this comment

Cargo.lock missing tokio-socks breaks SOCKS5 proxy support

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

croll83 commented Feb 25, 2026 •

edited by cursor bot

Loading

Cargo.lock missing `tokio-socks`, SOCKS feature not compiled

Cargo.lock missing `tokio-socks` breaks SOCKS5 proxy support