Copy Trading
Let followers mirror your expert traders — leader applications and approval, per-market allocations funded from a dedicated wallet, three sizing modes, profit share and platform fees, and the admin console that watches the money.
Copy Trading turns your platform into a social trading venue. One user — a leader — applies to be copyable, declares which markets they trade and what cut of the profit they want. Other users — followers — allocate money against those markets, and from then on every order the leader places is replicated onto the follower's account, sized to the follower's own budget and risk settings.
The leader never touches follower money and never sees a follower's balance. They place their own orders as normal; replication happens behind them, asynchronously, and their own order is never blocked or slowed by it.
What it requires
| Requirement | Why |
|---|---|
| Bicrypto core | Wallets, KYC, notifications, permissions, the cron manager, the settings store |
| Ecosystem addon | Spot copying only. Leaders trade ecosystem markets, follower orders go onto the same matching engine, and allocations are funded from the ECO wallet |
| Platform Binary Trading (core) | Binary copying only. Copied binary orders are refused by the binary engine if the platform-wide feature is off |
| Redis | Statistics caching, rate limits, the daily-reset marker |
Every spot copy path checks that the ecosystem extension is enabled before
it writes anything — not merely that its files resolve. Disable Ecosystem and spot
replication stops cleanly rather than writing copy-trade rows for orders that were
never placed.
Binary copying needs nothing from Ecosystem. A binary-only deployment can switch spot copying off entirely and the product still works end to end.
The two instrument classes
Every leader declares a trading type when they apply — SPOT, BINARY or
BOTH — and every market they list is tagged with its own class. A follower
allocates per market and per class, so the same symbol can carry a spot
allocation and a binary stake budget at the same time without the two spending
each other's money.
| Spot | Binary | |
|---|---|---|
| Venue | Ecosystem matching engine | Platform binary engine |
| Funded from | The follower's ECO wallet | The follower's SPOT wallet |
| Allocation shape | A base budget and a quote budget | A single quote-denominated stake budget |
| What a copy is | A real limit or market order on the book | A contract inheriting the leader's frozen terms, placed at the current price |
| Admin switch | copyTradingEnableSpot |
copyTradingEnableBinary and platform binary trading |
How money moves
Three wallet types are involved, and mixing them up is the most common support ticket this addon produces.
The dedicated wallet every allocation is held in. Funds are transferred here when a follower subscribes and transferred back when they stop.
Where the money comes from and returns to. Spot allocations move to and from ECO; binary stake budgets move to and from SPOT.
Where profit share lands. Both the spot and the binary path pay the leader into SPOT, so a leader has one payout destination whatever their followers copied.
An allocation is a real transfer, not a cap. The moment a follower subscribes, the money leaves their ECO or SPOT wallet and sits in COPY_TRADING, where the matching engine (or the binary engine) can hold it against open orders. Stopping the subscription tears down live orders first, then returns whatever is unspent.
Replication is asynchronous, and there are two writers
A leader placing an order does not wait for anything. The order is created, a hook
notices the user is an active leader with active followers, a leader-trade row is
written with status PENDING, and that row is pushed onto an in-memory queue that
drains every 100 ms.
A second, database-driven cron job is the backstop. It picks up leader trades that
are still PENDING after two minutes — the case where the process restarted before
the queue drained — and replicates them itself. Both writers key their copies on the
leader's own order id, so whichever runs second finds the existing copy and
stops. A follower can never be charged twice for one leader trade.
Where things live
The public landing page and leader discovery, plus the follower's own dashboard, subscriptions, trades and analytics.
The leader application form — trading type, style, risk grade, profit share and the markets on offer.
The subscribe form: per-market allocation, copy mode and the two risk sliders.
The operator console: the capital dashboard, leader approvals, subscriptions, trades, transactions, the audit log, system health and settings.
Two in-product guides ship as well, at /copy-trading/guide/leader and
/copy-trading/guide/follower.
What an operator is responsible for
Followers hand real money to the platform and then hand the decisions to somebody else. Every allocation on the admin dashboard is money held on trust, which is why the console is organised around what state that money is in rather than around how large the product has grown:
- being copied,
- paused by the follower's own choice,
- sitting behind a leader who has not traded for a week,
- stranded behind a leader who cannot trade at all — suspended, rejected, still pending, or removed.
Two of those four states do not exist as a status anywhere in the database. They are derived on the server for exactly this reason.
Start here
Prerequisites, activation, the eight tables, permission keys, KYC features and the eight cron jobs.
Eligibility, the application, market declarations and the approval queue.
Allocating capital, choosing a copy mode, setting risk caps, and stopping cleanly.
The replication path, the three sizing formulas, market-order pricing and the binary fairness window.
The exact split, who pays what, and where each leg lands.
Approving leaders, monitoring capital, forcing a stop and reversing a transaction.
All 25 keys — including the six that are read but never enforced.
Every endpoint, the permissions, the WebSocket channels and the tables.
"Nothing is copying", "the follower stopped after 20 trades", and every funds-related report.