Crypto Analytics Platform

Crypto Analytics Platform interface
Role
Full-Stack Developer, lead frontend
Period
2024 - 2025
Private Build

A real-time analytics surface for fast-moving tokens, built around live market signals, sentiment overlays, watchlists, and chart workflows that help traders react before momentum stalls.

StackReact, Next.js, TypeScript
5

Synchronized chart layers

Price, hype, burn, supply and market cap, drawn on one custom engine.

0

Real money at risk

A full trading and analytics loop on a demo wallet, not a brokerage.

2

Surfaces, one codebase

The same charts and indicators ship to web and the Telegram mini-app.

A spike in social hype, a move on the chart.

What I built

Frontend-focused fullstack: the trading UI and how it reads on a phone, the custom charting layer, and the data flows behind token analytics.

Trading UI
Token cards
Token detail
Custom charts
MobX state
API integration
Social-signal ingestion
Mobile performance
The problem

Reading a fast-moving token means watching price, social chatter, supply and burns at once. The product needed one surface where all of that lived together, updated live, and stayed fast on a phone inside Telegram.

How I approached it
  1. 01
    Custom charts on a fast baseOff-the-shelf charting libraries wouldn't draw price, hype temperature, burn rate and supply together. Built a custom layer on TradingView Lightweight Charts to keep all of them on one synchronized view, so the link between social hype and token burns reads at a glance.
  2. 02
    A realtime layer that stays calm under loadCandles, ladder and sentiment flow into MobX stores with optimistic updates and Redis-backed reads, so the dashboard stays smooth even with frequent updates.
  3. 03
    Social hype, turned into mechanicsA background worker turns Twitter/X trend signals into a hype score, a temperature and a token ranking, decoupled from the UI cadence so the interface never waits on it.
  4. 04
    One engine, two surfacesThe same chart engine and indicators ship to the web dashboard and the Telegram mini-app, with no forked chart code to keep in sync.
How it helped
  • The custom chart engine became the production charting foundation and stayed in use after launch.
  • A token reads the same on web and inside Telegram.

The custom charting layer

Five layers, one synchronized chart

TradingView Lightweight Charts couldn't draw what this needed, so I built a custom layer on top: price, hype temperature, burn rate, supply and market cap, all synchronized on one chart and tuned for touch. It became the production charting foundation, and ships to web and the Telegram mini-app alike.

How social hype moves a token

From a trending topic to a token's rank

A background worker reads Twitter/X trends and turns them into a hype score, a temperature and, in the end, a token's rank — then feeds the result back in, so attention compounds. It runs decoupled from the UI, so the dashboard stays smooth.

Social signalsmentions & trends
Topic extractionkeywords & tickers
Hype scorecomputed from activity
Temperaturecold → super-hot
Burn ratesupply drops
Token rankingre-ranked live

Tech stack

ReactTypeScriptMobXTailwind CSSTradingView ChartsNestJSPostgreSQLRedis