F
Fand_igor

Cryptocurrency Trading Platform

I developed and deeply customized a major cryptocurrency platform that consolidated exchange trading, user wallets, a transactional circuit, P2P, investment modules, KYC, notifications, API access, CRM functions, and administrative management of the entire system into a single product. This is not a discrete exchange page but a large modular platform with two frontends, a custom backend engine in TypeScript, real-time logic, background task queues, a broad domain model, and a discrete processing environment for trading operations.

The strength of the project is that it covered several levels simultaneously:

  • user circuit with trading, wallets, and a personal portal;
  • administrative circuit with management of markets, transactions, permissions, KYC, content, and system settings;
  • server circuit with API, WebSocket, queues, caching, and background handlers;
  • domain circuit with a large number of financial and infrastructure entities.

Project Context

  • The project developed as a full-fledged crypto-financial platform, rather than a discrete exchanger or landing page.
  • Discrete frontends were allocated for the administrative panel and the user portal.
  • The architecture was designed for expansion via discrete modules and additional product blocks.
  • The platform combined an exchange circuit, wallets, investment products, a P2P direction, ecosystem extensions, and support tools.
  • A discrete calculation and execution environment was used for the trading circuit, replacing direct calls to binance.com.

What has been implemented

  • Developed the platform with two discrete frontends: www as the administrative and main product circuit on Next.js 14, React 18, TypeScript; and www_users as the user portal and exchange interface on Next.js, React, TypeScript, Redux.
  • Implemented a custom backend circuit in TypeScript with HTTP and WebSocket processing.
  • Used uWebSockets.js as a high-performance foundation for the server.
  • Built a custom routing system, middleware, and request/response processing.
  • Implemented authentication via tokens, sessions, Redis, and API keys.
  • Added role-based and permission-based access for both regular users and integration access via API keys.
  • Implemented rate limits, CSRF checks, and protection for high-risk operations.
  • Built a domain model on Sequelize and MySQL with a broad set of entities.

Core Product Circuits

Exchange and Trading

  • Implemented a trading circuit for spot/exchange operations.
  • Supported trading pairs, markets, orders, watchlists, tickers, and charts.
  • In the platform's earlier layer, discrete entities for buy, sell, stop limit, conditional orders, favorite trading pairs, and favorite order books were also confirmed.
  • In the user portal, an exchange dashboard was implemented with pair selection, an order book, and real-time data updates.
  • Supported a real-time circuit for trading events and order book updates via WebSocket.
  • On the backend side, I worked on a discrete request and integration layer between the platform and an external processing environment that replaced direct work with the binance.com API.
  • The computing trading circuit itself was written by a discrete developer in C++, while I implemented and evolved the server logic for platform interaction with this environment.
  • In the administrative panel, there is management of exchange providers, markets, fees, balances, orders, and service analytics.

Wallets and Financial Operations

  • Implemented a wallet circuit with user balances and wallet types.
  • Supported deposits, withdrawals, internal transfers, and operation history.
  • Includes management of currencies, deposit methods, withdrawal methods, and gateway settings.
  • Implemented discrete administrative scenarios for approval and processing of withdrawal operations.
  • Includes PnL calculation and clearing, as well as discrete background processes for balance management.

P2P and Advanced Financial Scenarios

  • Implemented a P2P circuit with offers, trades, escrow, fees, dispute scenarios, reviews, and payment methods.
  • Includes discrete user and administrative screens for P2P mechanics.
  • In the platform, binary orders and discrete interfaces for binary trading are implemented.
  • Added a futures circuit with discrete markets, positions, and trading screens.
  • A discrete referral and affiliation circuit with bonus logic, accrual history, and networking scenarios is also present in the platform.

Investment and Expandable Modules

  • The platform includes modules for general investments, AI investment, forex, staking, and ICOs.
  • Each direction has its own plans, durations, logs, analytics, and administrative sections.
  • Implemented background processes for processing active investments, accruals, period completion, and result post-processing.
  • Supported modular activation of additional directions via extensions.

Ecosystem and On-chain Circuit

  • Implemented a discrete ecosystem circuit.
  • It includes markets, tokens, UTXOs, a private ledger, master wallets, and custodial wallets.
  • On the server side, there is work with addresses, networks, blockchain explorer APIs, and smart contracts.
  • For some deposit and withdrawal scenarios, the system switches to ecosystem routes and discrete business logic.

CRM, Security, and User Circuit

  • Implemented a user portal with profiles, KYC, notifications, operation history, and settings.
  • Supported registration, login, access recovery, email verification, Google login, wallet login, and OTP/2FA scenarios.
  • Includes KYC profiles, templates, verification levels, and administrative application processing.
  • Implemented API keys with a set of permissions for integration access to trading and financial operations.
  • The administrative panel includes modules for users, roles, permissions, support tickets, and KYC management.

Content and Service Blocks

  • A CMS circuit is implemented within the platform: pages, posts, categories, tags, sliders, media, authors, and comments.
  • FAQ, announcements, notification templates, and mailwizard campaigns are implemented.
  • Includes a storefront/ecommerce circuit with products, orders, discounts, shipping, wishlists, and review mechanics.
  • KYC and wallet balance constraints are utilized for some purchases and investment scenarios.
  • Custom pages, landing blocks, multi-language support, translations, and discrete public content entities for the platform's marketing circuit are also confirmed.

Technical Highlights

  • The server part was built not on a typical Express stack, but on a custom overlay on top of uWebSockets.js, providing a higher level of control over performance, routing, and WebSocket communication.
  • A key technical circuit of the project was that trading calculations and execution were moved to a discrete environment, replacing direct calls to an external exchange.
  • On my side, the backend layer for requests, routing, integration, and data exchange between the platform and this processed trading circuit was developed.
  • The low-level trading engine itself was implemented discretely in C++, and my area of responsibility lay in integrating this environment with the web platform and applied business logic.
  • Bull and BullMQ with Redis were used for background tasks.
  • Implemented a set of cron/worker processes for updating rates and currencies, processing pending orders, processing pending deposits and withdrawals, calculating wallet PnL, clearing old PnL records, as well as processing staking, forex, ICOs, investments, AI investments, and mail campaigns.
  • Roles, permissions, and discrete API key permissions are combined in the access model.
  • The backend circuit supports both user requests and integration calls with a discrete permission map for trading, futures, deposit, withdrawal, and transfer operations.
  • Redis is used for sessions, tokens, rate limiting, and caching scenarios.

What the project demonstrates

  • Ability to work with a large product involving simultaneous frontend, backend, real-time, security, queues, financial logic, and a complex domain model.
  • Experience designing and evolving a major modular platform rather than just individual screens.
  • Ability to build and maintain a financial backend with orders, wallets, transactions, API keys, and access constraints.
  • Experience integrating a web platform with a discrete computing trading environment rather than just a public API of an external exchange.
  • Experience building an administrative panel with a very broad scope of responsibility.
  • Experience with WebSockets, background jobs, Redis, ORM, tokens, KYC, and permission systems.
  • Experience assembling a product where trading, wallets, content, CRM, and system administration reside within a single architecture.

Technologies

  • TypeScript
  • Node.js
  • Next.js
  • React
  • Redux
  • uWebSockets.js
  • WebSocket
  • Redis
  • Bull
  • BullMQ
  • Sequelize
  • MySQL
  • Tailwind CSS
  • Pusher / real-time updates
  • ORM models and custom API layer

My role

My role in this project involved deep development and customization of the platform itself: server architecture, user and administrative circuits, trading and financial logic, roles and permissions, real-time scenarios, background tasks, wallets, transactions, KYC, API keys, expandable modules, and support tools. Separately, from my side, the backend layer for requests and integration with an external processed trading environment that replaced direct work with binance.com was fully developed. The trading engine itself in this environment was developed by a discrete specialist in C++, and my responsibility lay in the server linkage, data exchange, and applied logic on the platform side. This is the type of project where value was not in a single function but in the ability to maintain and evolve an entire large system.

Practical value of the project

This case demonstrates several strengths:

  • working with a large and dense domain area;
  • developing a platform rather than a single feature;
  • combining backend, frontend, real-time, and background processing;
  • ability to build a permission-based and role-based access system;
  • experience with financial modules, transactions, wallets, and trading scenarios;
  • integration of a web platform with a discrete trading environment and development of a backend request layer instead of direct dependency on a public exchange API;
  • experience designing a major admin panel with a large number of managed sub-systems;
  • ability to maintain the architecture of a complex product and evolve it further.