Promo Trader
Legitimate Binance Spot promotional trading volume platform
Paper trading by default · Live trading only with explicit opt-in · No withdrawals · No market manipulation
Overview
Promo Trader is a full-stack trading operations platform built for legitimate participation in Binance Spot promotional volume campaigns. Users configure promotions, strategies, and risk limits, then run automated paper or live bots that execute real market-facing buy/sell round-trips to accumulate qualifying volume—without wash trading, spoofing, or withdrawal capability.
The product prioritizes safety and transparency: deployment-level kill switches, per-bot risk engines, consecutive-failure guards, exposure caps, and clear LIVE vs PAPER modes.
Problem
Binance and similar venues run time-bounded spot trading volume promotions (eligible pairs, target volume, rewards). Participating manually is tedious and error-prone; naive bots often ignore lot-size filters, fees, residual exposure, or risk limits. Promo Trader turns that into a controlled ops workflow: define the campaign, attach a strategy, set hard risk bounds, and monitor fills, fees, and volume progress.
Key Features
| Area | Capabilities |
|------|----------------|
| Accounts | Encrypted API secret storage, permission-aware live mode (spot trading, no withdrawals) |
| Promotions | Campaign windows, eligible pairs, target volume, progress tracking |
| Strategies | Interval round-trip, liquidity-aware, multi-pair rotation, lowest execution cost, volume-target scheduler |
| Bots | Create / start / pause / stop / emergency stop; paper or live; auto-resume after deploys |
| Risk engine | Max capital, order size, daily volume, daily loss, exposure, spread, slippage, consecutive failures |
| Execution | Market (and limit) orders with LOT_SIZE / PRICE_FILTER handling, quote-sized buys, fee-aware sells |
| Analytics | Filled volume, fees, success rate, recent order history |
| Ops | Health endpoint, keep-alive friendly, structured logging, WebSocket-oriented status updates |
Architecture
``
┌─────────────────────┐ HTTPS / WS ┌──────────────────────────────┐
│ Next.js Frontend │ ◄─────────────────► │ FastAPI Backend (Render) │
│ (Vercel) │ │ │
│ • Auth (JWT cookie)│ │ • REST API + /health │
│ • Bots / Risk UI │ │ • Async SQLAlchemy + Alembic│
│ • Analytics │ │ • Per-bot asyncio workers │
└─────────────────────┘ │ • Risk engine + strategies │
│ • Binance Spot client │
└──────────────┬───────────────┘
│
┌──────────────▼───────────────┐
│ PostgreSQL │
│ users, accounts, promotions │
│ strategies, bots, orders │
│ risk events │
└──────────────────────────────┘
│
┌──────────────▼───────────────┐
│ Binance Spot API │
│ depth, exchangeInfo, orders │
│ (paper = no signed orders) │
└──────────────────────────────┘
`
Backend
- Framework: FastAPI, lifespan hooks, CORS from env
- Data: PostgreSQL via SQLAlchemy 2.0 async (
asyncpg), Alembic migrations
- Workers: In-process asyncio bot runners with DB status sync (RUNNING / PAUSED / STOPPED)
- Security: JWT auth, Fernet-encrypted API secrets,
ALLOW_LIVE_TRADING master switch
- Integrations: Binance REST (order book, filters, place order), optional egress IP debug for allowlists
Frontend
- Framework: Next.js (App Router), React, TypeScript, Tailwind
- UX: Dark trading dashboard—accounts, promotions, strategies, bots, analytics
- Session: HTTP-only cookies; configurable token lifetime
Deployment
| Layer | Host |
|-------|------|
| API | Render (web service + Postgres) |
| UI | Vercel |
| Keep-alive | External
/health pings (free-tier sleep mitigation) |
Functionality (user flow)
Register / log in → JWT session
Connect Binance account → API key + encrypted secret; live requires appropriate key scopes
Create promotion → time window, eligible pairs, target volume
Configure strategy → type + parameters ( eligible_pairs, order_size, intervals, etc.)
Create bot → link account, promotion, strategy; set risk limits; PAPER or LIVE
Start bot → worker loop: market data → strategy intent → risk check → execute → record order
Monitor → filled volume, fees, success rate, pause / stop / emergency stop
Risk stops → exposure, daily volume/loss, consecutive execution failures, inactive promotion/account
Strategy model (shared idea)
All strategies implement legitimate round-trips (buy then sell roughly the same notional) so promotional volume accrues from real, undisguised market orders. They differ in timing and pair selection, not in order type abuse.
Safety model
- Default PAPER (no signed live orders)
- LIVE requires env
ALLOW_LIVE_TRADING=true` and explicit bot mode
- No withdrawal flows in the application
- Quantity/price formatting against Binance filters; sell size capped to free balance after fees
- Dust/exposure tolerance so residual fills do not permanently stall the cycle
Tech stack
| Layer | Technologies |
|-------|----------------|
| Backend | Python, FastAPI, SQLAlchemy 2 async, Alembic, asyncpg, httpx, Pydantic Settings |
| Frontend | Next.js, React 18, TypeScript, Tailwind CSS, Recharts |
| Database | PostgreSQL |
| Infra | Render, Vercel, Uptime-style health monitors |
| Exchange | Binance Spot REST API |
Highlights for portfolio
- End-to-end trading system design: market data → strategy → risk → execution → analytics
- Production issues solved in the wild: LOT_SIZE/filter rejects, fee-aware sells, exposure dust, worker resume after deploy, CORS multi-origin, free-tier sleep
- Clear product ethics: promotional volume participation without manipulation primitives
- Full ops surface: bots as long-running jobs with pause/stop, structured events, risk audit trail
Status
Deployed backend and frontend with paper and live paths exercised on real Binance Spot symbols under strict risk limits. Suitable as a reference architecture for exchange-connected automation with human-visible controls and hard safety bounds.
Personal project. Not affiliated with Binance. Trading involves risk; live mode is opt-in and operator-controlled.
