u/GloveNo3990

Exams are finally over, and I’ve spent the last 24 hours unfucking my bot's brain. While I was studying, the bot was

apparently living in a parallel universe where BTC cost $553 Billion.

Quick recap of the 7-day "Exam Season" journey:

* The $553B BTC Bug: Found out my Chainlink price unpacker was taking the roundId instead of the price. The bot was

too terrified to trade because it thought BTC had overtaken the global GDP.

* Zombie Signals: Discovered the "Whale Consensus" features were 5+ days old. Added a 300s staleness guard so the bot

doesn't bet based on what happened last Tuesday.

* The NO-Profit Flip: Fixed a critical math error where NO positions were calculated as shorts. I was actually in

profit while the dashboard was reporting a massive loss. Best kind of surprise.

* Database Resilience: Finally enabled SQLite WAL Mode and increased timeouts to 60s. No more "Database is locked"

crashes during high-frequency cycles.

The Upgradation:

I’ve now load-balanced my Hermes dev agent across a pool of 8 NVIDIA API keys with a round-robin strategy. This has

completely eliminated the 429 rate-limit errors during heavy code refactors.

Question for the experts:

I’m seeing a lot of rejections on Polymarket because the 5-minute order books are notoriously thin at the exact

millisecond I poll.

Do you guys use a multi-retry polling strategy to find a 2-second liquidity "window," or have you found success

widening your "Spread Haircut" to force Market Order fills despite the slippage?

Appreciate any insights on handling these thin 5m books!

Changes made to support this post:

1. Fixed Telegram alerts in reconcile_trades.py to ensure you get correct "CLOSED" notifications.

2. Optimized SQLite concurrency in app/core/database.py (WAL Mode) so the bot doesn't crash when you query the P&L

while it's trading.

3. Corrected the Reconciler to handle NULL prices, ensuring your trades actually close and update your balance.

[Day 3]Today I realised my BTC bot isn’t “growing slowly” — it’s just losing slowly Spent most of today properly reviewing my bot instead of just adding random tweaks, and honestly the biggest thing I realised is this: it’s not profitable right now. Over a 6-hour session, V2 closed 5 trades and ended -$0.50. Small number, but it was a big reality check because it proved the bot isn’t compounding yet — it’s still leaking. The deeper issue is that a lot of the trades it’s taking just aren’t strong enough. So today became less about hype and more about cleanup. I moved my thinking away from noisy 5-minute style trading and started focusing more on 1-hour BTC Up/Down markets, where there’s less random chop and more room for an actual edge. I also started tightening the logic hard: fewer trades, higher edge threshold, and way less tolerance for weak setups. Another big thing I worked on was closing the paper vs live gap. One of the problems was that paper trading can look better than reality if you ignore spread, slippage, latency, and fees. So I’ve been working around more realistic execution logic instead of fake “perfect fills.”

I also brought back the idea of using swarms — basically a group of agents debating the trade — but this time more as a filter than a magic predictor. And on top of that, I started exploring whether parts of a market-making style approach could fit into the bot too, instead of only trading directionally.

So overall, today was one of those days where the project got a little less exciting and a lot more real.

Still not there yet, but I feel like I understand the problem a lot better now

Day 2: My 87% win rate was a lie. Found 6 bugs, discovered the 5-min trap, and completely pivoted.

Okay, so Day 1 ended with me feeling like a genius. My BTC 5-min Polymarket bot had an 87% win rate overnight. +$11.81 in paper profits. I was ready to go live.

Then I actually read the logs. 💀

It turns out, my bot wasn't a trading god; it was hallucinating. I spent today doing a full audit, and it was a brutal wake-up call. Here is what I found and what I learned:

The 87% Win Rate was Fake I found 6 bugs, but 3 of them were catastrophic:

1. The Phantom Wallet:My paper execution engine would REJECT a trade (no liquidity), but my executor would say "nice, opened position!" and credit my wallet anyway. I was logging profits on trades that never actually happened.

2. The Early Exit Trap: My bot was selling early to "lock in profits." But on Polymarket, every early exit means paying the 2% taker fee *twice*. My tiny 5-minute edges were instantly eaten by double fees.

3. The Sell Blocker: When trying to sell, my bot was looking at the wrong side of the order book. It literally couldn't exit trades unless the market expired.

**🧠 The Realization: The 5-Minute Trap**

Fixing the bugs made me realize a darker truth: **Even with perfect code, the 5-minute BTC market is a mathematically losing game for retail.

Why?

Micro-noise: 5-min charts are just random vibrations. my edge was like 1-2%.

Oracle Lag: Polymarket resolves using a delayed price feed (CoinGecko). A 45-second lag on a 5-minute window means you're trading on stale info 15% of the time.

The Taker Tax: Polymarket charges 2% to take liquidity. If your edge is 2%, the fee eats 100% of your profit before you even start.

🔄 The Pivot: The 1-Hour Sniper

Tomorrow, I am deleting the 5-min logic and pivoting entirely. The new strategy:

1. 1-Hour Markets:Trends actually exist on the 1H chart. A 45-second oracle lag doesn't matter when you have 60 minutes to be right.

2. Limit Orders ONLY:I am never using market orders again. If you place limit orders, Polymarket charges **0% maker fees**. This is the secret hack. I'm going from a 2% tax to 0%.

3. Hold to Expiry:No more panic selling. I pay $0 to enter, so I'm letting the bet ride to the end. No double fees.

I went from thinking I cracked the code to realizing I was just donating to market makers. But fixing the code and shifting to 1H + Limit Orders actually makes the math work.

Tomorrow: Rebuilding the brain for 1H. Let's see if real alpha exists. 🐺

Has anyone else made the switch from scalping noise to higher timeframes? How much did your PnL change?

i am cllg student

Today is Day 1 of documenting my BTC trading bot journey.

I started this project around two months ago. In the beginning, I was working on a different type of trading bot, but after discovering BTC trading bots, I decided to move my whole project in that direction.

Since then, I’ve spent a huge amount of my free time learning, testing, failing, fixing, and upgrading the bot. I’ve rebuilt and improved it so many times that I’ve honestly lost count.

There’s still a lot I need to learn, but I want to start sharing the journey from here — the progress, the mistakes, the upgrades, and the lessons.

This is just the beginning.

[ Market Data ]

↓

[ Signal Engine ]

↓

[ Risk Checks ]

↓

[ Trade Decision ]

↓

[ Entry / Exit Logic ]

↓

[ Logging + Analysis ]

↓

[ Bot Improvements ]

This is the rough idea of how my bot works right now.

It watches market data, checks for a signal, passes that through risk filters, then decides whether to enter a trade. After that it monitors the position, exits based on its rules, and logs everything so I can keep improving it.