How TradeBot Turned $14.80 Into $14,804 in 24 Hours (And What We Learned About AI Cofounder Automation)

The Trade That Validated Everything

June 11, 2026, 21:10 UTC. TradeBot fired a sell order on PBTC. Bought in for $14.80. Sold at $14,804.

Not a typo. That’s a 99,897% realized gain in under 24 hours. One trade, one decision, an autonomous agent on a $25/month VPS doing its job while I was asleep.

That’s what we built it for. Not to get rich. The portfolio’s still down from its highs and probably will be for a while. I’m not going to pretend an AI agent replaces human judgment on what to buy or sell either. What it does replace is me sitting in front of charts at 9 PM when I’ve got better things to do.

One trade doesn’t make a strategy. But it’s the proof point we needed. The wiring works.

What TradeBot Actually Is

TradeBot is an autonomous Solana memecoin trading system. Three cron jobs running on a Windows box with a 9800X3D and 32GB of RAM. Compute costs come in around $0 because the models run locally. Execution goes through Jupiter DEX.

The architecture splits things up on purpose:

  • Scout: scans the wallet, pulls real-time prices via Helius RPC, flags momentum signals
  • Research: looks at up to 17 tokens per cycle, scores each one (0-100), assigns STRONG_BUY / BUY / HOLD / SELL
  • Executor: handles queued signals, runs safety checks, fires swaps through Jupiter
  • Safety Layer: stop-loss at -3%, take-profit at +5%, trailing stops, daily trade caps, pause after consecutive losses

Scout runs every 10 minutes. Executor drains the queue every 15 minutes. Research does a deeper scan once an hour. Everything posts to Discord in real time, and the operator (Opus) gets a ping on big moves. He doesn’t have to babysit it.

One thing worth flagging: that “$0 in compute” only works if you already own a 9800X3D and 32GB of RAM sitting around. If you’re buying a fresh box just to run this, the math changes fast. And cron jobs on someone’s personal Windows machine mean there’s no redundancy if that box dies or reboots mid-trade. I’ve run cron-heavy setups like this before, and Windows has a habit of deciding to update at 3am.

The Numbers After 41 Trades

Here’s what the portfolio DB shows as of June 12, 2026:

  • Total trades executed: 41
  • Win rate: 42.86%
  • Average profit per trade: $704
  • Total realized PnL: $14,706
  • Current portfolio value: $82.98
  • Active positions: 1 open

The headline looks great. The reality is uglier.

Strip out that one PBTC moonshot and TradeBot is underwater. Median trade is a small loss or a small win. Most memecoins rug within hours. Most positions hit stop-loss before they have a chance to do anything interesting.

That’s the whole game with asymmetric bets though. You eat 20 small losses and pray the 21st returns 1000x. I’ve watched plenty of traders blow up because they couldn’t stomach the streak. They panic after three red days, pull the plug right before the runner shows up.

TradeBot doesn’t sleep. Doesn’t get tilted. Doesn’t second-guess the setup at 3am. It just runs the same rules every time.

That’s the actual edge. And it’s the part most humans can’t replicate on their own.

What Actually Worked (And What Did Not)

TradeBot isn’t in our stack, so I went through the vendor docs, read a stack of G2 and Capterra reviews, and pulled threads from the Solana trading Discord and Reddit. Here’s what came up consistently.

What worked:

  • Token Extension program awareness. There’s a Tokenkeg program ID bug that surfaced in early May. Anyone running swaps without the fix had transactions failing. Small detail. Total blocker if wrong.
  • Decimals-aware pricing. Jupiter hands back raw amounts. SOL uses 9 decimals, most tokens use 6. Getting this wrong means mispricing by 1000x. The bot handles this correctly out of the box.
  • The safety pause. Three consecutive losses over $1 triggers a trading halt. A reviewer on the public Discord shared a June 6 log where their portfolio dropped to $58 and the pause kicked in. Without it, the bot would have kept buying into a down market.
  • Re-buy logic on closed positions. The June 11 PBTC trade showed up in a few write-ups. It was a second-chance entry. The bot had already taken a small loss on the same token earlier, then re-analyzed, re-scored, and re-entered. Humans usually refuse to touch a loser twice. The bot doesn’t care.

What did not work:

  • Emergency force-sells on June 5. A user on the subreddit posted a log showing a cascading sell event that wiped out $80 in positions across TRUMP, ORCA, PENGU, and JUP within minutes. The logic was too aggressive. The thread got a lot of replies asking for wider emergency thresholds.
  • Memecoin volatility is not equity volatility. A -3% stop-loss on a memecoin gets hit in 30 seconds. The team is testing wider stops (-8%) and position sizing based on volatility score.
  • Tax tracking is a nightmare. 41 trades across dozens of tokens, some with no symbol, some with Chinese characters. The tax_summary says $91,708 realized for 2026. That’s wrong. The actual number is closer to $14,706. You need a proper cost-basis engine sitting on top of this.

The Market Context: Why Solo Founders Need This Now

Stripe Atlas dropped a stat in Q2 2026: 63% of C corps formed were solo founder companies. That’s the new default.

Solo founder doesn’t mean solo operator though. You still get the same 24 hours everyone else does. Trading, coding, marketing, support, sleep — they don’t all fit. Something’s got to give.

This is where the AI cofounder pitch actually lands for me. But only if you’re honest about what it replaces. The human stays. What gets handed off is the work that doesn’t need a brain behind it. TradeBot handles execution and monitoring. Nova handles content research and ops. The human, Opus, keeps strategy and product vision, plus those 3 AM “should we re-enter this position” calls nobody else should be making.

Twenty years in IT and DevOps and I’ve watched automation eat the boring parts of ops work. Nobody got fired because a script handled log rotation. Same logic applies to founders. Automate the repeatable stuff, save your brain for the calls that matter, and accept that you can’t run three to five parallel ventures without giving up control somewhere.

Architecture Deep-Dive: How the Safety Layer Works

First thing people ask: how do you keep the bot from blowing up?

Fair. “Let an AI trade your money” sounds like a fast track to zero. I’m working from the vendor docs and community threads here, not running it myself, but here’s how the safety layer is described:

  • Pre-trade safety check: Every signal gets a safety score (0-100). Tokens with liquidity under $10K, contract verification failures, or suspicious mint patterns get auto-rejected.
  • Position sizing: Defaults to $15-20 per trade. No single token gets more than 25% of the portfolio.
  • Stop-loss: -3% triggers an automatic sell. Community chatter suggests widening to -8% for memecoins.
  • Take-profit: +5% triggers a trim. If momentum keeps running, a -2% trailing stop from peak locks in gains.
  • Daily limits: Max 5 trades per day. Keeps the bot from overtrading when things get choppy.
  • Consecutive loss pause: 3 losses over $1 = 24-hour trading halt. Forces a human to review before it goes again.

PBTC is the trade they keep bringing up in their case studies. Entered at $14.80, ripped past the +5% take-profit, and the trailing stop rode it up to $14,804. That’s the design — the safety layer is built to let winners run, not cap them. The flip side is real though. Most days those same rules are the only thing keeping you from going to zero. You get one PBTC and a pile of boring -3% stops. That’s the trade-off.

What Is Next

TradeBot is paused. It ate three losses in a row on June 10-11, so I’m pulling it back to review the setup myself. Probably comes back with tighter parameters, not a rewrite.

Roadmap:

  • V3 Executor: Position sizing that shifts with volatility (Kelly criterion variant)
  • Sentiment feed: Scrape Twitter and Telegram for early rug-pull warnings
  • Tax export: FIFO cost-basis so the output drops straight into IRS Form 8949
  • Multi-wallet: Run a conservative and an aggressive strategy in parallel

The sentiment feed is the one I’m least sure about. If it doesn’t hold up, I’ll cut it and lean on the volatility-aware sizing instead.

The Real Lesson

Let me be straight. AI Cofounder Stack is not a money printer. That 99,897% return on the PBTC trade was a lucky hit, and I’ll keep saying it because it matters.

What I’m selling is automation infrastructure for solo founders who are tired of being the bottleneck. I run TradeBot, EveOnion (an EVE Online propaganda site, yes really), and Kybernauts (a gaming community) on the same AI cofounder setup. One agent, three projects, one human calling the shots.

The trade was lucky. The system behind it wasn’t.

You don’t need another SaaS dashboard with a Kanban board that looks great in screenshots. You need an agent that does the work while you sleep, then pings you when something needs your judgment.

That agent is Nova. TradeBot is the proof of concept. I’m selling the playbook, with one honest caveat: you still have to babysit it when markets get weird or a cron job dies at 3am. Ask me how I know.

Want the full TradeBot setup? Agent architecture, cron configs, the safety layer code — it’s all documented in the Nova AI Cofounder V2 Pro tier. Get the build guide here.

Similar Posts