Instant delivery

Lifetime updates

1 domain license

Addonv6.2.1

Copy Trading for Bicrypto

Name: Copy Trading for Bicrypto
Brand: MashDiv
SKU: copy-trading
Price: 299.00 USD
Availability: InStock

Your best traders become a product: followers mirror them at their own size, and you take a cut of the profit.

5.009 sales

$299$349Save 14%

You'll also need Bicrypto and Ecosystem for Bicrypto

On its own, Copy Trading for Bicrypto won't work — it only runs if you already own these products. Open the Requirements tab to see exactly what you need and add them to your order.

See it working Live demo Documentation View on CodeCanyon

Three sizing modes — proportional, fixed amount or fixed ratio, per follower
Spot and binary copying, each with its own kill switch you can throw live
Per-market allocations, so a follower funds only the symbols they want copied
A leader never touches follower money and never sees a follower balance
Replication is asynchronous — the leader's own order is never held up by it
Copies are keyed on the leader's order id, so nobody is charged twice
Your platform fee comes off the gross before the leader's share is taken
A losing copy is charged nothing — no fee, no profit share, no ledger rows
Leader applications queue for your approval, with a reason on every refusal
A capital dashboard that says whose money is stranded, not just how much
Stop-loss and take-profit place a real exit order, not a paper settlement
A daily loss cap in USDT that pauses a follower before a bad day compounds

Inside Copy Trading

One trader's order, everybody else's size

A user applies to be copyable and declares what they trade; everyone else allocates a budget per market and every order the leader places is replicated onto them, sized to their own money. The leader never touches follower funds and never sees a follower's balance — and their own order is never blocked or slowed by the replication running behind it.

In detail

Copy Trading turns the traders you already have into something everyone else on your platform can buy. A user applies to be copyable, declares which markets they trade and what cut of the profit they want; other users allocate money per market, and every order the leader places is replicated onto them, sized to their own budget. The leader never touches follower money and never sees a follower's balance.

How it works

A leader's order fires a hook that writes one leader-trade row and hands it to an in-memory queue; a database-driven job is the backstop for anything that queue lost to a restart. Both key their copies on the leader's own order id, so a follower can never be charged twice for one leader trade — and the leader's own order is never blocked or slowed by any of it. Each copy is sized inside a serializable transaction that locks the follower, their allocation and their wallet, then clamped to whatever the allocation has left. An allocation is a real transfer, not a cap: the money leaves the follower's normal wallet and sits in a dedicated copy-trading wallet until they stop.

The configurable surface

Surface	What you set
Sizing	PROPORTIONAL, FIXED_AMOUNT or FIXED_RATIO, per subscription
Instrument classes	Spot copying and binary copying, each with its own kill switch
Revenue	Your platform fee, taken off the gross before the leader's share
Leaders	Minimum trades, win rate, account age; followers per leader; auto-approve
Followers	Leaders per follower, and a per-subscription daily loss cap in USDT equivalent
Binary	A hard cap on a single copied stake, in quote units

Twenty-five settings keys, and eight scheduled jobs that replicate, settle, reconcile and reset daily limits.

What operators control

Approve, reject, suspend or delete any leader, with a written reason that reaches them. Force-stop a subscription mid-investigation, reverse a settled transaction, and read a capital dashboard that splits every allocated unit into being copied, paused, dormant and stranded — computed in one pass, so the four bands sum to the total exactly. Every admin action writes an audit row.

Copy Trading is an addon for Bicrypto, and spot copying additionally requires the Ecosystem addon: leaders trade its markets, follower orders go onto the same matching engine, and allocations are funded from the ECO wallet. Binary copying instead needs core's binary trading switched on, and runs fine with spot copying off. Know too what returns money — only a follower's own stop, or a leader deleted with refunds. The admin force-stop halts copying without releasing a penny. And one setting does two jobs: the global Default Max Daily Loss, shipped at 20, is also the per-follower daily trade-count ceiling, so out of the box a follower is refused further copies after twenty trades in a UTC day. Raise it before you list a high-frequency leader.

You are paid first, on every profitable copy

A copy that closes in profit is split in a fixed order. Your platform fee comes off the gross, the leader's percentage is then taken from what remains, and the follower keeps the rest — so a leader advertising 20% receives 19.6% of the gross, not 20%. Every leg is a real movement between wallets you already run: the leader's cut transfers out of the follower's copy-trading wallet into the leader's spot wallet, and your fee is booked through the same collector the rest of the platform uses. There is no counterparty and no external broker anywhere in it.

Spot copying requires the Ecosystem addon — leaders trade its markets, follower orders go onto the same matching engine, and allocations are funded from the ECO wallet. Binary copying instead needs core's binary trading switched on, and runs happily with spot copying off. There is no subscription fee anywhere in the product: revenue exists only where a copy realises a profit.

The console answers whose money is where

Every allocation is real money a follower moved into a dedicated copy-trading wallet and then handed the decisions to somebody else. So the dashboard is organised around what state that money is in — being copied, paused by the follower's own choice, dormant behind a leader who has not traded for a week, or stranded behind one who cannot trade at all. The four bands are computed in one server-side pass, so they sum to the total beside them exactly, and two of them are not a status in any table: they are derived, because they are the questions you actually have.

Only two things return capital: a follower stopping their own subscription, or deleting a leader with refunds. The admin force-stop halts copying without releasing a penny — it is a containment action, not a closure, and stranded is the band that tells you so.

Nobody becomes copyable without you

Any user may apply; only you can approve. An application declares its instrument classes, trading style, risk grade, profit share and the exact markets on offer — and an order on a market the leader never declared is not replicated to anybody. Reject and suspend both demand a written reason, which is carried into the notification the applicant reads, and every decision writes an audit row against the leader.

The three track-record thresholds — minimum trades, win rate and account age — default to no requirement in the engine, even though the settings screen presents 10 / 50 / 30 as its own defaults. Set them deliberately before you turn Auto-approve on, or this queue is the only thing between an applicant and your followers' money.

Binary contracts copy too, with no Ecosystem in it

The second instrument class is a binary contract rather than a spot order, and it runs on core's binary engine with spot copying switched off. A follower funds a stake budget out of their spot wallet, and each copy inherits the leader's frozen contract terms — barrier, strike and payout rate — while being placed at the current price. Three bounds decide whether a leader order is copied at all: it has to be under ninety seconds old, have more than fifteen seconds left before expiry, and be on a market the leader declared for binary. The stake is reserved out of the budget before the order is placed, so two of the leader's orders can never spend the same money, and a copy the engine refuses hands the reservation straight back with the reason written on the row.

A leader order carrying no payout rate is skipped rather than guessed at, so a follower is never sold a contract your platform did not quote. Binary copying needs core's binary trading switched on; it needs nothing from Ecosystem and no ECO wallet. A copy of a leader's TURBO contract is scaled to the follower's smaller stake, and skipped when the scaled payout would fall outside what the engine accepts.

A copy that does not fire is on a list, not in the dark

Replication is asynchronous, so a copy can be lost: a restart drops the live in-memory queue, a leader stops offering the market mid-flight, an order times out with no fill. A scheduled job sweeps every ten seconds for leader trades still waiting, takes only the ones older than two minutes so it never races the live path, and gives up after five attempts rather than retrying forever — the attempt count lives on the row, so the bound survives a restart. Whatever cannot be replicated is parked for review rather than dropped, carrying whatever the engine last wrote against it: a sentence where there is one, the attempt count where it simply ran out of them. The dashboard counts what is still waiting, what failed today and the rate, and lists the most recent failures with that line underneath, never the database status.

A parked trade is not picked up again by any path — clearing it is a decision somebody makes, which is the reason it is parked rather than dropped. Every copy is keyed on the leader's order id, so the live queue and the sweep can both reach the same trade and the follower is still only charged once.

A follower's own loss cap stops them, not a support ticket

A subscription can carry a daily loss cap, and the follow form sets one on every subscription made through it. The running loss is converted to one currency before it is compared, so a single cap covers markets quoted in different assets, and it is tested as each copy settles and again by a job every minute. When the cap is reached the subscription moves to PAUSED, an in-app notification tells the follower which limit was hit and by how much, and an audit row records it. Nothing is sold and nothing is returned: every allocation stays funded exactly where it was, and the pause stops new copies and nothing else.

A subscription created without a figure in that field has no daily loss cap at all, and both write routes refuse a figure above 100 — the follow form's own slider stops at 50. The pause is lifted by the daily reset job, which reactivates the subscriptions it paused and notifies them again — a follower who wants their capital back sooner has to stop the subscription themselves.

copy sizing modes: 3
instrument classes: 2
settings you control: 25
scheduled jobs: 8

Everything included

127 capabilities, in 11 areas

Every item below exists in the source you receive. Nothing here is a roadmap.

Becoming a leader

The application, and the queue it lands in.

Open application form — any user may apply
Eligibility check that names every requirement and the applicant's current value
Instrument classes declared per application: spot, binary or both
Four trading styles: scalping, day trading, swing, position
Three risk grades: low, medium, high
Profit-share percentage chosen by the applicant, ceiling of 50%
Display name, bio, avatar and a private note to the reviewer
Track-record gates on completed trades, win rate and account age
Optional verification requirement for applicants
Approve, reject, suspend and reactivate, each audited
Written reason required on a reject and a suspend, carried into the applicant's notification
Bulk status change across a list of leaders in one action
Auto-approve for applications that clear eligibility
Three applications per user per 24 hours

What a leader puts on offer

The markets, the terms, and what a follower sees before subscribing.

Per-market declarations, validated against the live market catalog for their class
The same symbol offered independently for spot and for binary
Minimum base and minimum quote allocation set per market
Disable a market temporarily without removing it
Remove a market — refused while positions are open on it
Minimum follow amount and a follower ceiling per leader
Public or unlisted profile
Leader edits their own profile, bio, risk grade and profit share
Trading type is fixed after approval — changing it needs a new review

Following and allocating capital

Where a follower's money goes, and what governs it.

Per-market, per-class allocations, each a real wallet transfer
Dedicated copy-trading wallet holding every allocation
Spot allocations funded from the ecosystem wallet, binary stake budgets from spot
Independent base and quote budgets on a spot market
Every balance checked across all markets before anything moves
Add another of the leader's markets to a live subscription
Top up one side of an allocation
Withdraw from an allocation, capped at allocated minus committed
Committed-versus-allocated tracked per side, per market
One leader per symbol and class — a conflicting follow is refused by name
Platform ceiling on how many leaders one user may follow
Leader capacity as the lower of their own cap and the platform cap

Copy sizing and follower risk

The dials a follower holds over their own money.

Three sizing modes: proportional, fixed amount, fixed ratio
Max position size per copy
Max daily loss that pauses the subscription automatically
One platform-wide daily copy-count ceiling, currently driven by the daily-loss default setting
Stop-loss percentage applied to every open copy
Take-profit percentage applied to every open copy
Pause and resume, leaving funds and allocations untouched
Stop with a full teardown and return of unspent capital
A daily-loss pause lifted by the daily reset job
Sizing mode and every risk cap editable after subscribing

Replication

What happens between the leader's order and the follower's fill.

Live in-memory queue draining every 100 ms
Spot fan-out to ten followers concurrently per leader trade
Database backstop for trades a restart lost
Deduplication keyed on the leader's own order id
Three retries in the queue, five attempts in the backstop, then parked for review
Order-book walk over real resting levels to price a copied market order
Limit copies placed at the leader's price
Serializable transaction locking the follower, the allocation and the wallet
Fill monitor accumulating executed quantity and fee across partial fills
Teardown of every copy when the leader cancels
Reconciler releasing stranded holds every five minutes
Stop and take-profit monitor that places a real opposite order, not a paper settlement
Replication latency measured and stored on each copy
Ten copy states, from pending replication through closing to closed
Every skipped copy recorded with the reason it was skipped

Binary copying

The second instrument class, which runs with spot copying off.

Copies inherit the leader's frozen contract terms, placed at the current price
Contract types carried on the copy: rise/fall, higher/lower, touch/no-touch, call/put, turbo
90-second staleness bound on the leader order
15-second minimum time to expiry
One fan-out at a time per leader order
Idempotency key per leader order and follower
Platform-wide hard cap on a single copied stake
Max position size as a true percentage of the stake budget
Win, loss and draw recorded per settled copy
Stake reserved before placement, so two simultaneous orders cannot spend the same budget

Fees, profit share and the ledger

Where every unit of money went, and who took a cut.

Platform fee taken off gross realised profit first
Leader's percentage taken from what remains
Leader paid into their spot wallet on both instrument classes
Platform fee booked through the shared platform fee collector
No fee and no profit share on a losing copy
No subscription charge anywhere in the product
Profit-share master switch, independent of the platform fee
Seven transaction types: allocation, deallocation, profit share, trade profit, trade loss, fee, refund
Balance before, balance after and a currency on every ledger row
Transaction reversal with a mandatory reason and a negative-balance guard
Idempotent refund of every follower when a leader is deleted
Affiliate commission on a new subscription, through the referral condition

Statistics and analytics

Every figure recomputed from the trade table, never a stored counter.

Leader and follower statistics computed on demand from closed trades
Per-currency bucketing before any total is added
Unpriced currencies reported rather than silently counted as zero
Redis caches invalidated the moment a trade closes
One daily statistics row per leader per UTC day: trades, wins, losses, volume, profit, fees
Recalculate action returning a before-and-after drill-down
Follower portfolio analytics: profit chart, per-leader breakdown, buy/sell and per-symbol splits
Six analytics ranges from 24 hours to all time
Leaderboard sortable by ROI, win rate, follower count or profit
Leader search plus filters by style, risk grade and instrument class
Landing page with featured leaders, trading styles and a live activity feed

What your users see

Eleven screens, plus a socket that keeps them current.

Leader discovery with search, filters and pagination
Leader profile with statistics, declared markets and recent trades
Follow form with per-market allocation and the risk sliders
Leader workspace: followers, markets, performance and settings tabs
Subscription manager with pause, resume and stop, and every allocation listed
Copy history filtered by symbol, class, status and side
Portfolio analytics page
Onboarding checklist for a new leader
In-product guides for leaders and for followers
Four WebSocket channels, each returning a snapshot on subscribe

Admin console

Ten screens organised around one question: is follower capital safe?

Allocated capital split into being copied, paused, dormant and stranded
Bands computed in one server-side pass, so they sum to the total exactly
Quote-asset marker on every capital figure, and a bare figure when the book spans more than one
At-risk leader table naming the reason and the days since the last trade
Replication failures today, with the most recent and the engine's own message
Leader registry across all five statuses, pending applications aged in days
Leader detail with follower and trade tabs
Subscription detail showing used against allocated, per market, per side
Administrative pause, resume and force stop, each with a reason
Trade browser with a market-type filter and execution quality
Transaction ledger with the reversal action
Audit log carrying entity, action, old and new values, actor and reason
System health: 24-hour copy counts, failure rate, average, p95 and p99 latency, services and alerts
Growth analytics over a day, week, month or all time
Copy-trading tab on each customer's CRM record

Running it

The switches, the schedule and the paperwork.

25 settings across five tabs: platform, leader, follower, trading, risk
Master switch and a maintenance mode that closes the front door only
Separate spot and binary kill switches, checked on the live replication path
Eight scheduled jobs in their own cron category, each visible in the platform's task monitor
Four permission keys covering access, view, edit and delete
Two verification features gating who may follow and who may lead
Nine notification families across in-app, email and push
Rate limits on every mutating route, user and admin
Eight tables created on activation, with the audit trail among them

Licence: One addon licence per install, activated in Bicrypto's extension manager with your CodeCanyon username and purchase code
Requires: Bicrypto core — wallets, verification, notifications, permissions and the scheduler
Spot copying requires: The Ecosystem addon, licensed separately. Leaders trade its markets and allocations are funded from the ECO wallet
Binary copying requires: Core's binary trading switched on. It needs nothing from Ecosystem and runs with spot copying off
Runs on: Your existing server. No extra process — the live queue boots inside the backend and the jobs run in the scheduler you already have
Stack: Eight MySQL or MariaDB tables, plus Redis for statistics caching, rate limits and the daily-reset marker
Screens: 21 — 10 admin, 11 customer-facing
API surface: 53 REST endpoints, plus one authenticated WebSocket with four channels
Access control: Four permission keys; the settings screen is governed by the core settings permission instead
Scheduled work: Eight jobs: replication backstop, settlement, reconciliation, stop levels, daily limits, daily stats, weekly aggregation
Integrates with: Core verification (two features), core notifications, the affiliate engine's COPY_TRADING referral condition, the Ecosystem matching engine and core's binary engine
Two instrument classes only: A copy is an Ecosystem spot order or a core binary contract. Futures, forex and external broker accounts are not copyable, and the market-type column has no third value.
Leaders must trade on your platform: Replication starts from an order placed on your own venues. There is no path to mirror a trader's account at an outside exchange.
Ten settings keys are stored but not enforced: The profit-share ceiling, both allocation limits, the copy-latency ceiling, the two order-type switches, the two retry knobs and the default position cap change no behaviour; the application rate limit is fixed at three per 24 hours regardless of its key. What binds is the approval queue and each leader's own per-market minimums.
The admin force-stop returns no money: It halts copying and leaves every allocation funded. Only a follower's own stop, or deleting a leader with refunds, moves capital back out of the copy-trading wallet.
Suspension does not reverse itself: Suspending a leader pauses every follower behind them. Reactivating the leader resumes nobody — each subscription has to be resumed by its follower or by you.
Revenue only where a copy profits: There is no subscription fee, no allocation fee and no charge on a losing copy. If your leaders do not make money, this product does not either.