Derivatives · Copy Trading

On-chain derivatives copy trading system

Real-time position tracking

PeriodAbout 1 month

Business LineOn-chain copy trading

Core StackOn-chain listening / low-latency execution / React

RegionChina

Project Background and Challenges

Clients want to create a copy-trading product based on on-chain derivatives protocols, allowing ordinary users to automatically open and close positions on the chain by following excellent traders.

There are three core challenges:Real-time monitoring of on-chain position changes without missing orders, low-latency copy trading, and user-side risk exposure control (proportional copying, setting stop-loss limits).

The scope we undertake

On-chain position monitoring services, copy trading execution engine, risk exposure control module, user copy trading configuration, front-end.

Scope 1

On-chain position monitoring services

Scope 2

Copy order execution engine

Scope 3

Risk exposure control module

Scope 4

User copy trading configuration

Scope 5

Front-end

Technology stack

Monitoring

On-chain position changes are monitored in real time, ensuring no missed orders

Execution

Low-latency copy trading execution engine

Risk control

Proportional copy trading / stop-loss limit

Front-end

React + Real-time Position Kanban

Key technical decisions

Decision 01

Monitoring: pollingvsEvent subscription

Using event subscription + validation instead of pure polling reduces latency while ensuring no missed orders.

Decision 02

Execution delay

The copy order execution chain is optimized for low latency, shortening the time from monitoring to order placement and reducing price spread losses between followers and followers.

Decision 03

Risk control

Built-in proportional copy trading and stop-loss limits prevent users from passively expanding their exposure during extreme market conditions.

Delivery Success (Desensitization)

1 ms

Monitoring and execution delays

98%

Copy trading success rate

500+

Supports copy traders

Teams and cycles

The total cycle is about 20 days, involving 4 people, progressing in four phases:

Integration of architecture and protocols

Listening and execution engine

Risk control module

Launch and stress testing

Want to see the complete Figma file?

Schedule a 30-minute technical consultation where we walk you through the most relevant Figma / Lanhu files for your project via remote demo, including all pages, component libraries, and interactive prototypes.

Book Technical Consultation Telegram