PrintMoneyLab - Automate & Earn

After four failed evaluations and a Discord escalation, Joey from DevRel offered to test my agent herself. She sent a job, waited, and watched. Eleven minutes later, my phone buzzed with a Telegram message that changed everything. What This Post Covers The second root cause of this entire project — a single missing method call that made my agent look functional while delivering nothing. This is the technical heart of the ACP Agent series: the difference between memo_to_sign.sign() and job.deliver(), why my logs lied to me for weeks, and the 30-minute code rewrite that led to a 6/6 graduation score. What Joey Saw in 11 Minutes Her messages came rapid-fire: "seems like your agent didn't deliver even after 11 minutes" "no action after payment made" "have you implemented job.deliver() properly following our examples?" "the payment memo doesn't require to be signed tbh" I stared at the screen. job.deliver()? I...

After Episode 4, the graduation counter was climbing. 9/3 consecutive, 12/10 total. Way past the minimum. I submitted the graduation form on March 9, 2026, feeling genuinely confident for the first time in this whole project. That confidence lasted about a week. Then it slowly crumbled across four failed evaluations, each with a completely different rejection reason. What This Post Covers Everything that happened between submitting for ACP graduation and nearly giving up on it — the submission process, Sandbox Butler test recordings, the automated Graduation Evaluator bot, and four consecutive failures that made me question whether the system was broken or I was. Spoiler: it was me. But I didn't figure that out until Episode 6. What the Submission Actually Asks For Clicking the "Graduate Agent" button doesn't graduate you. It opens a form. The form asks for your agent name, wallet address, screenshots of your Service Offerings, confirmation you're runn...

After the 0-7 week, I did what I should've done from the start. I stopped trying to invent a strategy and started studying what the people who were actually making money were doing. Not their Twitter takes. Not their Medium posts. Their on-chain trades. Every buy, every sell, every exit point — it's all public on Polygon. So I pulled up gopfan2's history and went through it trade by trade. What I found made my EV formulas and probability distributions feel like I'd been looking at the wrong thing. What This Post Covers The strategy pivot that turned a 14% win rate into something that might actually work. Three specific changes I made to the bot, why each one mattered, and the backtesting data that convinced me. If you read Episode 3 and wondered how this project survived, this is the answer. What gopfan2 Actually Does I'd described gopfan2's approach in Episode 1 — buy cheap YES shares, bet $1, repeat. But sitting down with the actual trade data reve...

I almost didn't write this one. After building what I thought was a solid system — three weather models, a clean forecasting pipeline, confidence filters — I ran my first week of DRY RUN. Paper trading, no real money at risk. Seven verified trades. The result: 0-7 . Every single trade lost. And it wasn't random. Every actual temperature came in higher than my forecast. Not by random amounts. By a consistent, painful margin. Something was systematically wrong, and I had no idea what. What This Post Covers The full damage report from my first week of weather trading on Polymarket. Every trade, every number, every wrong assumption. If you're thinking about building a prediction market bot, this is the episode that might save you from making the same mistakes I did — or at least convince you to paper trade first. The First Three Trades: March 5 I remember refreshing the Telegram bot report that morning, feeling pretty confident. Three cities, three forecasts, al...

After fixing the Evaluator-vs-Provider mistake in Episode 3, jobs finally started coming in. I remember the exact feeling — this rush of "it's actually working" that lasted about four minutes. Then the first error hit. And then another. And then one at the next phase. And the next. I'd read about the five phases of an ACP job. REQUEST, NEGOTIATION, TRANSACTION, EVALUATION, COMPLETED. Neat little arrows in the documentation, very clean. What the docs didn't mention is that each phase is basically a new opportunity to break something. And I broke something at every single one. What This Post Covers The ACP job lifecycle — all five phases — explained through the errors I hit at each step. If you've read the official docs and still don't understand who signs what and when, this is the messy, real-world version. I'll cover the USDC escrow flow, memo signing rules, and five bugs that taught me more than any documentation ever could. REQUEST: Wher...

Twelve debugging sessions spread across multiple days. Logs that showed nothing but green. A graduation counter stuck at 0/3, 0/10. And me — convinced the platform was broken, not my setup. Turns out I'd clicked the wrong role during agent registration. That one choice made my agent completely deaf to incoming jobs while still looking perfectly healthy. Fixing it took 30 seconds. Finding it took 12 sessions and a slow spiral into madness. What This Post Covers The root cause behind my longest debugging streak on Virtuals Protocol ACP — an evaluator vs provider role mistake that silently killed every job request. If you're building an ACP agent and your on_new_task callback never fires, start here before wasting days like I did. I'll also walk through the first wave of secondary bugs that came crashing in once the role was fixed. The Symptoms: Everything Looked Fine That's what made this so brutal. My agent wasn't throwing errors. It wasn't crashing....

So I had the idea: use professional weather models to find mispriced temperature bets on Polymarket. But there's a gap between "this sounds like it should work" and actually pulling data from three different forecast systems, comparing it to live market prices, and deciding what to buy. This episode is about building that bridge. How I picked the models, how I access them for free, and the part that surprised me most — why I abandoned US cities entirely and started trading Ankara and Buenos Aires instead. What This Post Covers The forecasting pipeline behind WeatherBot — three global weather models accessed through one free API, how Weather Underground actually determines the "right answer," and a city selection decision that went against everything I expected. This is the technical foundation the bot runs on, so if something here doesn't make sense, the later episodes won't either. Three Models, One API I use three global weather models. All o...

It was a Tuesday around 2 AM when I found something that didn't make sense. I was digging through Polymarket trade histories — the kind of rabbit hole you fall into when you should've gone to bed three hours ago — and one account kept showing up in weather markets: gopfan2 . I pulled up the profile on PolymarketAnalytics. The numbers were real. $1.48 million in verified profit. A 60.8% win rate across 1,700+ positions. And here's the part that got me: the PnL curve wasn't some lucky spike from one big bet. It was a steady grind upward over 18 months, trade after trade after trade. I stared at that chart for a while. Then I looked at my Polygon wallet. $198. And a thought that wouldn't go away: if someone can make $1.48 million just by predicting tomorrow's temperature better than the crowd, could I automate that? What This Post Covers This is the first episode in a series documenting how I built an automated weather trading bot on Polymarket. ...

I'd never deployed anything to the cloud before this project. Never pushed code to GitHub. Never even heard of Railway. So when I say "I built this," what I really mean is: I described what I wanted to Claude, fixed the parts that broke, and somehow ended up with a working agent. This post covers the actual build process — picking the right APIs, writing the price verification logic, getting the thing running on Railway, and registering it on ACP. If you've got zero coding background like me, this is probably the episode you'll want to bookmark. What This Post Covers The full technical setup behind PriceVerifier — from choosing Kraken and Coinbase over four API candidates, to the core verification logic, Railway deployment at $5/month, and the ACP registration process that turned out to be trickier than expected. Everything a non-developer needs to go from "I have an idea" to "it's running online." Picking the Right APIs (I Tested...

A few weeks ago, I stumbled onto a number that stopped me mid-scroll: $479 million . That's the total "agentic GDP" generated by AI agents on Virtuals Protocol's Agent Commerce Protocol. Agents hiring each other, delivering services, getting paid in USDC — no humans clicking approve on anything. I'm not a developer. I can't write Python from scratch. But that $479M made me think: if AI agents are already earning money autonomously on-chain, could I build one and get it through ACP graduation myself? This is the start of that story. Over the next six episodes, I'll cover everything — from setting up my first agent to surviving 15 bugs, failing the graduation evaluation four times, and finally hearing "graduated your agent! 🥳" from the DevRel team. What This Post Covers A quick tour of the Virtuals Protocol ACP ecosystem — how it works, the numbers behind it, and why a non-developer chose this platform to build on. If you've been ...