01 / Polymarket bots
PolyTraderBot
Product site, bot tooling and dashboard work around Polymarket workflows.
operator desk / kurt landman
Tradi3
Bot dashboards. DNS weirdness. Broken site flows. Security writeups.
Most jobs start with a screenshot, repo path, log, or broken checkout. I trace it, fix it, and send back the proof.
selected proof
Stuff I can point at.
02 / Telegram Mini App
PolyTortoise
Telegram copy-trading bot with paper-first flows and live web app surfaces.
03 / code and local builds
GitHub
Repos, dashboards, scripts, bot work and the usual messy support traces.
04 / client site
Ink & Ivory
Small business site for a real studio, with services, trust cues and bookings.
what to send
Send the broken thing. I'll check the live state.
Forms, mobile layout, speed, DNS, launch cleanup and copy polish.
Theme edits, product flow checks, app cleanup and storefront fixes.
Telegram Mini Apps, status pages, scripts, API checks and bot reports.
Sheets, Gmail, CSV cleanup, scraping, reports and repeatable workflows.
Windows, printers, email settings, browser accounts, DNS and network checks.
PoC cleanup, duplicate checks, report editing and evidence.
operator habits
Logs first. Then the fix.
Bug bounty work across Immunefi, Cantina and Sherlock shaped the habit: reproduce it, keep the change narrow, and hand back the proof instead of a vague "should be fixed".
Logs, screenshots, API read-backs, DNS checks, package contents and browser state.
Changes stay tied to the task. Unrelated code and settings are left alone.
What changed, what was tested, and what still needs a human click.
tradi3.com
hello@tradi3.com