Copy tradingbotfree
Polymarket-betting-bot: what it does, how it is built, where it stops
Last checked 2026-09-08
Polymarket-betting-bot is a TypeScript and Express backend that runs two bot types on Polymarket: copy-trading bots that replicate any wallet's trades, and strategy bots that fire market or limit orders when odds on BTC, ETH, SOL or XRP markets cross a trigger.
It is a server, not a desktop app. Users, JWT auth, MongoDB storage and encrypted private keys are part of the design, which points at a small operator running bots for several wallets.
What it does
Copy bots take a target wallet and settings: percentage or fixed bet sizing, a copy ratio from 0 to 1, minimum bet size (floor 5 USDC), maximum bet size, retry limit up to 100, timeout up to 3,600 seconds, and an option to dump remaining shares on a partial sell. Several copy bots run at once.
Strategy bots pick a market (BTC, ETH, SOL, XRP), a trigger price from 0 to 100, market or limit, a fixed size and retry settings. Order history, WebSocket updates and Winston logs come with it.
- @polymarket/clob-client and ethers.js for trading
- bcrypt for passwords, custom encryption for stored private keys, JWT for the API
- Joi validation, graceful shutdown, role-based users
Strategy
Copy: mirror a wallet at a ratio with size floors and caps. Trigger: enter when odds reach a threshold. Neither has a model behind it; the README describes mechanics, not edge, and its disclaimer says educational and research purposes.
Setup and requirements
Node.js 18 or newer, a MongoDB instance, a Polygon RPC endpoint (Alchemy, Infura or QuickNode), and the Polymarket CLOB HTTP and WebSocket URLs. The .env also carries JWT_SECRET, a 32-byte ENCRYPTION_KEY and the USDC contract address on Polygon.
npm run build then npm start. Wallets are added through the API with their private keys, which are encrypted at rest.
Activity and maintenance
99 stars and 37 forks as of 2026-09-08. Created 2025-11-11, last push 2026-03-16, 3 open issues. TypeScript. Six months since the last push; the README's USDC contract address is the USDC.e address on Polygon, and the Alphapoly README states Polymarket V2 moved to pUSD collateral on 2026-04-28.
Where it falls short
No frontend is documented beyond a public/ folder, no backtest, no risk engine beyond per-bot size caps. The collateral and CLOB assumptions are from before Polymarket's V2 change and have not been updated.
Running other people's private keys on your server, even encrypted, is a custody business. The README's security list is a good start and nothing more.
Who should use it
A developer who wants a multi-tenant copy-trading backend to build a UI on, and will update the Polymarket client first.
Not for someone who wants to double-click and copy a wallet.
Questions about Polymarket-betting-bot
Is Polymarket-betting-bot free?
Yes. GitHub detects an MIT license file; the README says ISC.
Does Polymarket-betting-bot work with Kalshi?
No. Polymarket only, and the strategy bots cover BTC, ETH, SOL and XRP markets.
Is Polymarket-betting-bot maintained?
Last push 2026-03-16 as of 2026-09-08, with 3 open issues. Its collateral settings predate Polymarket V2.
How does Polymarket-betting-bot store private keys?
Encrypted with a 32-byte key you set in ENCRYPTION_KEY, in MongoDB.
Bots die in execution. Terminals are execution.
Wanted a bot for speed and cross-venue vision? The free Kairos terminal trades Kalshi, Polymarket and Predict.fun from one book, no keys to manage.