Polymarket copy-trading bot (Python)

A ready-to-run Polymarket copy-trading bot built on PMWallets: it follows the traders you subscribe to and mirrors their fills on the Polymarket CLOB with your own account, inside the limits you set.

pmwallets-copytrade on PyPI · 中文说明 · Node.js version: polymarket-copy-trading-bot · SDK: pmwallets-python

What the bot does

1. You pick the traders on pmwallets.com: filter the board by the lower bound of the win-rate confidence interval, profit without the single best market, activity and style, then subscribe.
2. The bot receives every fill of those traders over the PMWallets WebSocket, typically within a second of the block (measured latency). Missed frames are detected (session/seq) and replayed from the last fill handled, including everything that happened while the bot was down.
3. It mirrors them on Polymarket with your own account, inside the limits you set. Your keys never leave your machine; PMWallets never sees them and never places orders.

Quick start

# Python ≥ 3.10
pip install pmwallets-copytrade
pmwallets-copytrade init            # writes config.yaml
export PMW_API_KEY=pmw_...          # https://pmwallets.com/keys
pmwallets-copytrade run             # dry-run: logs every decision, trades nothing

When the dry-run log looks right, switch to live:

mode: live
polymarket:
  privateKey: ${POLY_PRIVATE_KEY}        # signs your orders
  signatureType: 2                       # 0 plain wallet · 1 email/Magic login · 2 browser-wallet login
  funderAddress: ${POLY_FUNDER_ADDRESS}  # your Polymarket profile address (holds the USDC)

pmwallets-copytrade status prints open positions, today's spend and any order still being confirmed. If the bot cannot establish by itself whether an order filled, it keeps the order's reservation (no further BUY can exceed your limits because of it) and asks you: check polymarket.com and run pmwallets-copytrade reconcile <key> --none or --filled <shares> --usdc <usdc> with the bot stopped. Every decision — including each skip and its reason — is appended to pmw-data/decisions.<mode>.jsonl.

How it decides

The rules come from a copy-trading bot that ran live on Polymarket; each one is there because of a lost trade or a rejected order.

BUY (the trader bought)

• skip fills older than maxFillAgeSec (a replay after downtime must not buy history), below minTargetNotionalUsdc, or from a role you excluded;
• one copy per trader transaction, one position per (trader, outcome), at most maxBuysPerOutcome buys into it (DCA), maxOpenPositionsPerTarget / maxOpenPositions / maxDailySpendUsdc caps;
• the market must be open, accepting orders and not settle within minSecondsToEndDate;
• the best ask must sit in [minPrice, maxPrice], be at most maxSlippage above what the trader paid, and the book must hold minBookDepthUsdc;
• order: fill-or-kill for an exact number of shares at the best ask (orderSizeUsdc / ask), rounded so the CLOB accepts it. Share-denominated on purpose — a USDC-budget market order can overfill.

SELL (the trader sold)

• sellMode: all exits everything the bot bought following that trader in that outcome. Shares booked to another trader in the same outcome are never sold: the most it sells is your token balance minus what the other traders hold. If that comes to nothing, it stops and asks you to reconcile;
• the exit is saved and retried (with backoff, across restarts) until the position is gone. Freshness does not apply: if the trader left while the bot was down, it still gets out;
• order: fill-and-kill at the best bid — a partial exit beats none, and the rest is retried.

Safety

• dry-run by default; live needs an explicit mode: live;
• at most once: a fill is marked decided in the state file before any order is sent, so a crash can miss a copy but never place it twice. One bot per data directory: a second instance refuses to start;
• no lost fills: every order is saved as pending before it is sent. An order the exchange reports as killed (such replies have carried real partial fills) is looked up again by its order id with backoff until its fill — or its absence — is certain, even across restarts. One that got no answer at all has no id to look up: if a matching trade appears, the bot does not guess whose it is (it could be yours by hand, or another trader's copy) and hands it to you to reconcile;
• resolved markets are swept every 10 minutes so they stop counting against the caps.

One stream per account. PMWallets allows one WebSocket per account and the newest connection wins, so the bot and the live-feed page on pmwallets.com (or a second bot) will take the stream from each other. Run one consumer per account.

Development

pip install -e '.[dev]'   # or: uv pip install -e . pytest pytest-asyncio
pytest

The same config.yaml, state files and lock file work with the Node.js version. testdata/ holds the contract cases both implementations must pass — keep it identical in both repositories.

Resources

• Polymarket smart-money leaderboard — profitable Polymarket traders scored from the Polygon chain, with win-rate confidence intervals
• Polymarket copy trading guide — which wallets are worth following and how to get their fills in time
• How to learn from Polymarket smart money — reading a trader's record: confidence intervals, maker vs taker, market specialism
• PMWallets API documentation — WebSocket and webhook fill push, fills replay, trade-history exports
• Measured fill-push latency — block-to-push p50 / p95, published live
• Ways to follow Polymarket wallets, compared — official leaderboard, free trackers, SQL dashboards
• FAQ · 中文站

Proxies

HTTPS_PROXY / HTTP_PROXY / NO_PROXY are honoured for the PMWallets API, the WebSocket and the Polymarket CLOB.

Disclaimer

This software places real orders with real money when mode: live. A copied order is not the trader's order: the price may have moved, fees apply and liquidity is shared. Past results do not predict future ones. PMWallets provides data about what traders did, not advice. Use at your own risk; see LICENSE (MIT).