The official documentation for the Poly-Maker, a market-making bot for Polymarket.
| English | 简体中文 |
Disclaimer: This is not financial advice. Trading cryptocurrencies and participating in prediction markets involves significant risk. This is high-risk software that trades real money. Market making can lead to losses due to sudden price movements, one-sided fills, market resolution, API/network failures, or changes in reward structures. Always start with DRY_RUN=true and use very small amounts of capital for live testing.
This repository contains a market-making bot for the Polymarket prediction market platform.
.env file, designed for efficiency and ease of use..env Configuration: All parameters, from API keys to strategy variables, are managed in a single .env file.GTC (Good-Til-Cancelled) + Post-Only orders to act as a maker and capture rebates.systemd service file for running as a background service on a VPS.git clone https://github.com/your-username/poly-maker.git
cd poly-maker
uv:
uv sync
cd poly_merger
npm install
cd ..
cp .env.example .env
.env: Open the .env file and fill in your details. Refer to ENV_CONFIG_GUIDE.md for a detailed explanation of every variable.uv run python discover_markets.py --limit 10
uv run python resolve_market.py "https://polymarket.com/event/..."
Run the latency probe to find the value for PREDICTION_LATENCY_MS in your .env.
uv run python latency_probe.py --samples 20
If you encounter invalid signature errors, this script can help diagnose issues.
uv run python check_auth.py
ALWAYS start with a dry run.
uv run python main.py
DRY_RUN=false in your .env.
DRY_RUN=false uv run python main.py
For continuous operation, it’s recommended to run the bot on a server. A systemd service file is provided in service/poly-maker.service for convenience.
This project is licensed under the terms of the LICENSE file.