Selected systems
Built in public. Protected by default.
Capabilities and technology are shown here. Client identities, brand assets, and internal interfaces stay private.
How I work
From community problem to operating product.
The work crosses product design, backend systems, automation, data pipelines, security boundaries, and production interfaces.
01Discover
Map the real workflow
Translate Discord, wallet, reward, or trading operations into explicit rules, states, roles, and failure cases.
Build
Connect the system
Ship the bot, API, dashboard, database, chain data, scheduled jobs, and service integrations as one coherent product.
Protect
Design the safety boundary
Use scoped permissions, audit logs, rate limits, replay protection, wallet verification, and clear read-only or points-only modes.
Operate
Make it maintainable
Add health checks, durable state, admin controls, monitoring, deployment runbooks, and controlled rollout paths.
Operating principles
Evidence over hypePaper data, backtests, and live behavior are labeled for what they are.
Least privilegePublic wallet proof without custody, seed phrases, or unnecessary signing.
Durable systemsPersistent state, recovery paths, audit trails, and operational controls.
Client work
Built around distinct communities.
Each system reflects its client’s brand, audience, permissions, and operating model.
Velcor3
Staking, verification, NFT intelligence, and community tooling.
Unique Alpha
Raids, account linking, points, games, giveaways, shops, and auctions.
Kovari
Captcha access, waiting rooms, link protection, tickets, and operations.
Penni
A branded Discord economy with verification, raids, rewards, and auctions.
The common thread
Useful infrastructure with a clear brand.
The goal is never just another bot or dashboard. It is a system a community can understand, trust, and use repeatedly.
