🪭 Takao is now live on Robinhood Chain.
This is our first step into a new ecosystem, bringing TakaoZone infrastructure to a market with fresh liquidity, new tokens and new trading opportunities.
For Robinhood chain, we are using @node_vision infrastructure. Their node gives us the speed and reliability we need to operate in fast-moving markets without compromising execution quality.
Solana remains our core, but the market is expanding. TakaoZone is expanding with it.
Same edge. New chain. TakaoZone. 2026.
i gave Grok Bot $75 and told it "earn your keep or get shut off"
48 hours later it's sitting on $6,140
still running
autonomous trading agent on the platform
I didn't touch a line of code - it lives on its own cloud box with its own browser and terminal, working while I'm asleep
every 20 minutes it:
> pulls every weather market with a resolution date inside the next 10 days
> cross-checks the current price against the latest forecast update
> only opens a position once the forecast and the market disagree by enough to matter
> sizes up based on how wide that disagreement is
> places the trade on its own, no approval step
> covers its own hosting bill straight out of profits
if it ever hits $0, the subscription gets cut - it's done for good
hour nine it was down to $14. it dropped every multi-day market it was holding and switched to same-day resolution only
so it changed its own strategy to stay alive
setup took one evening: spin up the bot, run one trade in front of it, put it on a timer, hook up a wallet
no VPS. no API keys. no dev on call.
I paid a freelancer $4,000 to build something like this last year. it never made it past a demo
Grok Bot did in one evening what two months of freelancers couldn't
$75 → $6,140 in 48 hours
what's it sitting at by Friday?
Day 78 — the RUN page is where users spend 80% of their time.
Every misplaced pixel is a problem they hit hundreds of times a day.
No logic changes today.
Just 12 passes on interactions and spacing — hover states, focus rings, animation timing, the stuff that doesn't show up in a changelog but makes the page feel alive or feel dead.
The RUN page is where everything converges:
Token info, trade controls, PnL, preset switching, stop button.
It's dense by necessity. Dense and cluttered are different things and for a long time this page was both.
12 passes to pull them apart.
The page isn't faster — the code didn't change.
It just responds exactly when you expect it to now, which turns out to feel like the same thing.
Boring work. Worth doing.
Profile wallet tab and volume surge watcher are next.
Day 77 — 14 passes to land on a referrals page that looks like it took one.
The data was always correct.
It just looked like a spreadsheet.
Everything in one block, numbers next to each other with no visual hierarchy, technically complete and completely unreadable at a glance.
Split it into three cards: your code, your earnings, your invitees.
Same information, three separate contexts.
Now you can land on the page and immediately see what matters without parsing a wall of stats.
Information density isn't always good — sometimes the right move is just to get out of the way of the data.
14 iteration passes to get there. That's not a typo.
The first few versions were technically fine.
The next few fixed the obvious problems.
The last few were just taste — spacing, hierarchy, which number leads and which ones follow.
The difference between pass 10 and pass 14 is invisible to anyone who didn't sit there making it.
RUN page rebuild is next.
@thsottiaux I've been using GPT-5.6 Sol on my Mac, and it just feels like a better experience. macOS seems much better suited for this kind of workflow than Windows. The interface is clean, user-friendly, and it makes it much easier to stay focused and vibe code without getting in the way.
Day 30 building Solana HFT trading bot
Buy Amount Presets + Buy/Sell Fee Split:
[x] Built buy amount presets panel — migrated quick presets to backend
[x] Split fee settings into buy/sell tabs with separate auto controls
[x] Added fee presets panel
[x] Fixed nil guard for unsafe atomic.Value type assertions
[x] Added missing HTTP server timeouts to prevent slowloris attacks
[x] Fixed userlog leaks + critical error handling bugs
[ ] Build referrals page
What I learned:
http.ListenAndServe without timeouts is basically an open door for slowloris.
A slow client can hold the connection forever and your server just sits there doing nothing.
Add ReadTimeout, WriteTimeout and IdleTimeout to the server and the problem is gone, no reverse proxy needed.
It Ain't Much But It's Honest Work
I'm currently ranked 103rd on the PolyTweet Leaderboard.
My goal is to break into the top 100 soon.
Just a tweet about @Polymarket.