TNTX — social trading rebuilt into an onchain social layer

Problem

The founder had the right product idea in the wrong codebase. The original platform — one place to discover tokens, discuss them, and trade them — was slow, unstable, and hard to extend: legacy code, inconsistent multi-chain data, charts that stalled the page, real-time chat that buckled under load, and deploys with no observability behind them.

Approach

We re-architected the platform without losing the vision. The front end moved to Next.js App Router with a reusable design system; the back end became modular NestJS services with a WebSocket gateway handling presence and reconnects with backoff. Redis caching and normalized adapters for ETH, SOL, and BSC made multi-chain data consistent. Charts were reworked with lazy mounting, windowed lists, and skeleton states, and the whole system moved onto CI/CD with Docker, Nginx, health checks, and structured logs.

With the foundation stable, the product kept moving: token hubs with liquidity, holders, and audit data; a market view pairing TradingView-style charts with a swap panel; real-time token chats and notifications; staking with lock durations and a public leaderboard. The rebuild ran through 2025, and that work carried into the rebrand as TNTX, where the same real-time layer now runs tournaments, player lobbies, and onchain game rooms.

Outcome

A live product at tntx.ai where rooms spin up, players join, and the social layer is the app. The platform is faster, stable, and maintainable — and we now work as the client's development team, shipping new features as it scales.

Live

tntx.ai

Stack

• Next.js App Router and a shared design system
• NestJS services and a WebSocket gateway with presence and retry/backoff
• Redis caching, normalized ETH/SOL/BSC adapters
• Real-time lobbies, tournaments, and onchain-facing product UI
• Docker, Nginx, and CI/CD with health checks and structured logs