#backend

data models, APIs, and a bot that watches a blockchain

0pedev1:05 PM

I started on the front end, and it's still where I'm fastest. But the problems I keep choosing lately are behind the interface: what the schema should be, what happens when two requests hit the same row, and what a service should do when the data it needs isn't there yet.

Two projects taught me most of it — one a database exercise dressed up as a fan site, the other a bot that watches Base for new tokens and has to be right about money.

2 attachments

Canary2026

Rug-risk scoring for every new token on Base and Solana — plus a live web scanner, no Telegram required.

TypeScriptTelegrafviem

Aang vs Korra — 1000 Reasons2026

1,000 rows, a Prisma schema, and the API to page through them.

PrismaPostgreSQLNext.js

→ web work the stack

Canary

2026 · TypeScript · Telegraf · viem · SQLite · Node.js · Next.js

Every other sniper bot competes on speed — who buys a new token first. Canary competes on not losing your money. It polls Base's Uniswap V2/V3 and Aerodrome factories plus pump.fun on Solana for new launches, then scores each token 0–100 for rug risk with plain-English reasons: honeypot checks, mint rights, ownership, hidden taxes, LP lock status, and holder concentration. The bot is the product; the site turns the same scoring engine into a public /scan tool — paste any address, get the score and reasons in the browser, no signup — then hands off to @BaseCanaryBot for live alerts.

What it does

Watches two chains — Base and pump.fun on Solana — for new pools, roughly 35+ launches an hour on Base alone.

Blends three sources: GoPlus for contract security, on-chain RPC for liquidity, DexScreener for market data.

Reads liquidity straight from the pool's quote-token balance, because DexScreener doesn't index brand-new pairs for hours.

Refuses to score a token until its data is actually readable — a wrong score is worse than no score.

The web scanner shares the bot's exact scoring code, mirrored into a stateless Next.js API route — same result, no server or DB needed.

Tiered delivery with subscription access control and expiry, backed by SQLite.