01ACCOUNT
An account you control
The destination account must be user-controlled and eligible for the required lead-trading function.
FOUR-EXCHANGE GUIDE
Prepare account authority first, then validate every route in order.
This guide puts prerequisites, current exchange support, route rules, and the Shadow-to-Demo sequence on one page. The website never receives account data or starts the local product.
01 / PREREQUISITES
Do not enter production until these four conditions are clear.
These checks apply to every exchange. Available permissions and lead-trader eligibility still depend on the user's own account.
02ACCESS
Minimum necessary access
The connection is limited to reading and trading, with no withdrawal use.
03RULES
Explicit amount boundaries
Define fixed or proportional sizing, per-order limits, daily budgets, and allowed scope.
04BASELINE
A clean initial baseline
Confirm current state on first run so existing history is not treated as new activity.
02 / EXCHANGE STATUS
Prepare each exchange separately instead of treating four platforms as one account type.
Similar interfaces do not mean identical permissions, account modes, or validation outcomes. Review every destination independently.
01Supported workflow
BINANCE
Prepare lead-trader eligibility, read and trade access, and confirm that account mode matches route settings.
02Supported workflow
OKX
Prepare lead-trader eligibility, read and trade access, and review position mode and destination state separately.
03Public interfaces and Shadow validated
GATE.IO
Customer-private accounts should complete Demo review in their own environment before proceeding.
04Public interfaces and Shadow validated
BITGET
Customer-private accounts should complete Demo review in their own environment before proceeding.
03 / ROUTE SETUP
One route should answer only four things: source, rules, destination, and result.
- 01
Select an authorized source
Use an owned trading account, existing copy positions, or a currently supported public source you are authorized to use.
- 02
Define sizing rules
Choose fixed or proportional sizing and configure per-order limits, daily budgets, and allowed scope.
- 03
Connect an owned destination
Create each exchange route separately. Do not reuse permissions or modes that have not been reviewed.
- 04
Review the outcome
Check whether activity was processed, why it was skipped, and the final state before adjusting rules.
04 / STAGED VALIDATION
Shadow → Demo → production, without skipping a stage.
Do not advance while source state, amounts, limits, or failure reasons remain unresolved.
SHADOW
→Calculate and record route decisions without sending production actions.
DEMO
→Review amounts, limits, outcomes, and failures in a simulated environment.
LIVE
Never started from the public site; it requires explicit confirmation in the local product.
KEEP READING
Open the relevant page only when you need deeper boundaries.
PRIMARY PRODUCT