I made a bot that turned $20 into $180 trading crypto on Polymarket in a week (91% win rate, and yes I know how that sounds)

I made a bot that turned $20 into $180 trading crypto on Polymarket in a week (91% win rate, and yes I know how that sounds)

Woke up a few mornings ago, checked the dashboard, and the number staring back at me was $180 from a $20 starting balance. 1,500+ trades executed. 91% win rate. I did not touch a single button.

I know a 91% win rate sounds like either a scam or a rounding error. It's neither. Let me explain what's actually happening.

What I made:

A self-hosted Go bot that trades Polymarket's crypto prediction markets — BTC, ETH, XRP, SOL — on 5-minute and 15-minute windows. These markets ask one question over and over: did the price go up or down in this window. Settles, resets, repeats. Forever.

Why 91% win rate isn't magic:

These are small, fast, frequent trades ($5 each). The strategies aren't predicting BTC's next move like some oracle — they're reacting to short-term patterns (reversals, momentum flips, late-window collapses, etc.) that happen consistently enough on a 5-minute timeframe to have an edge, small position after small position. It's not one big bet, it's fifteen hundred small ones.

I'm not claiming this scales infinitely or that it'll hold up forever. I'm telling you what happened in one 7-day window with real money.

Why I built it:

Tried trading these manually first. Lasted about four days before I accepted the truth: humans cannot react fast enough to a market that resets every 300 seconds. By the time you register a setup and click through Polymarket's UI, the window's basically over. And there's no manually watching 8 markets (4 assets × 2 timeframes) at once unless you enjoy suffering.

How it actually works:

Ships with 5 built-in strategies — reversal, collapse, conviction, flip, scalp/fade/resolution-type patterns. You're not stuck with one hammer looking for a nail; you pick strategies based on what the market's doing.

Before it fires a trade, multiple independent signals have to agree first — not just one indicator flashing green. Once they do, execution is millisecond-level.

You can run all 8 markets at once, each with a fully separate config, as independent instances.

The scheduling thing that actually mattered:

Some strategies are great at 3am and terrible at noon (or vice versa — still figuring out exactly why). Instead of ignoring that and trading blind 24/7, I added active day/hour scheduling so a strategy only runs during the windows where it actually has an edge. This alone changed my results more than any single strategy tweak.

Real numbers, 7-day live session:

• Starting balance: $20
• Trade size: $5
• Trades executed: 1,500+
• Win rate: 91%
• Net profit: +$160

The technical side:

• Written in Go, compiled to a single binary
• WebSocket connections, no polling
• Full PnL journal — every trade logged with why it closed
• Backtesting built in, runs against your OWN trade history, not generic data
• Setup wizard, no config file surgery required

The part I'm most stubborn about:

It's fully self-hosted. Runs on your own machine. Your API keys and wallet credentials never leave your computer, never touch a server I control. I've seen too many "trading bot" products that are just a wrapper for "give us your keys and trust us." Didn't want to build that, and honestly didn't want to trust that either.

What I'd push back on if I were you:

• 91% win rate over 7 days on a $20 account is a small sample. I'm not going to pretend otherwise.
• Crypto prediction markets can and do change behavior. What works this month might stop working next month.
• $5 trades mean this isn't "quit your job" money at this balance — it's proof of concept, not a lambo fund.

If someone in the comments wants to tell me this is gambling with extra steps, they might have a point, and I'm happy to argue about it.

Current status:

Live for about two weeks now. There's a small Discord (350+ people) where users compare strategy configs and results, which has honestly been the most useful part of building this — I learn about edge cases from people running it in ways I didn't expect.

Ask me anything — the strategies, the 91% number, the scheduling logic, or why I think self-hosting matters for something that touches your wallet. Also happy to hear why I'm wrong about any of this.