BINANCE / OKX / GATE.IO / BITGET · QUANT LEAD PRODUCT

Connect an authorized quant source to your own lead-trader accounts.

Route quant-source activity under sizing and risk rules into lead accounts you control. Followers use the exchange's native relationship, and eligible profit share is settled by the platform.

BINANCEOKXGATE.IOBITGETPOLYMARKET

Current capabilities only.Review Shadow decisions and Demo outcomes first; unfinished controls remain clearly marked Planned.

Read the build log →
01 / PRIMARY PRODUCT

BINANCE / OKX / GATE.IO / BITGET · LEAD OPERATIONS

Four-Exchange Quant Lead-Trading Bot

The product is positioned for quant lead-trading operations, not trader recommendations. It connects authorized sources to owned lead accounts without providing a profit strategy or promising followers or profit share.

LOCAL-FIRST

The website never connects to an account or receives account data. Runtime state stays on the user's device; eligibility and profit-share settlement remain with the exchange.

01

Owned trading account

Use activity from an account you control and are authorized to operate.

02

Existing copy positions

Use positions already formed in your own account and process later changes.

03

Visible strategy source

Observe publicly visible positions, subject to platform availability.

04

Public on-chain position

Observe supported public perpetual positions while preserving market boundaries.

QUANT LEAD / STRATEGY IDENTITY

Build a verifiable record with your own strategy and lead accounts.

Operators use authorized quant sources and owned lead accounts while participants follow through the exchange. The software does not pool funds, recruit followers, or guarantee returns or platform profit share.

4source options
3validation stages
4exchange adapters
1local audit trail

02—03 / POLYMARKET

Wallet automation and read-only research, separated by purpose.

One product handles new public-wallet activity under explicit boundaries. The other remains read-only and builds explainable research profiles.

02

PUBLIC ACTIVITY · LOCAL CONTROL

Polymarket Local Wallet Copy

Observe new activity from selected public wallets, then record or act on eligible events within user-defined amount, price, and risk boundaries.

  • New activity only
  • Fixed or proportional sizing
  • Budget, price, and position boundaries
Explore Polymarket Copy
03

PUBLIC DATA · READ-ONLY

Polymarket Whale Wallet Research

Turn public activity into explainable account profiles, screening results, and an ongoing research record.

  • Public-data research
  • Explainable wallet profiles
  • Sample and concentration penalties
Explore Whale Research

PRODUCT COMPARISON

The three products solve different problems.

The four-exchange product routes authorized quant sources into owned lead accounts. Polymarket Copy handles new public-wallet activity. Whale Research remains read-only.

ProductProblemPrimary inputOutputNatureMaturity
01Four-Exchange Lead BotRoute quant trading activity into owned lead-trader accountsAn authorized quant source, account activity, or supported public sourceBudgeted lead-route decisions and a local audit trailStaged lead executionBinance / OKX supported; Gate.io / Bitget public interface and Shadow validated
02Polymarket CopyOngoing observation and bounded handling of new public-wallet activityPublic activity from wallets selected by the userRecords, block reasons, and guarded outcomesSimulation first; optional local executionSimulation and guarded flow validated
03Whale ResearchToo many public wallets and no explainable research orderPublic leaderboards and public activityProfiles, filters, and continuing research recordsRead-onlyWindows Beta; read-only flow validated

OPERATING MODEL

Prepare. Connect. Validate.

  1. 01

    Prepare a quant source

    Use an authorized strategy account, existing copy positions, or a supported public source. The product does not supply a profit strategy.

  2. 02

    Connect lead accounts

    For owned accounts with the required lead-trader status, define sizing, budgets, per-order limits, and allowed scope.

  3. 03

    Validate

    Establish a clean baseline, review Shadow and Demo, and enable live lead trading only by explicit user choice.

RISK CONTROL

Automation should make boundaries more visible.

Every route is constrained by current product capability. Stop-loss, take-profit, and maximum drawdown remain Planned.

Review the four-exchange lead boundary →
CONTROLCURRENT STATE
Per-order amount limitAVAILABLE
Lead-account daily budgetAVAILABLE
Allowed market scopeAVAILABLE
Account-mode preflightAVAILABLE
Stop-loss / take-profitPLANNED
Maximum drawdownPLANNED

BUILD NOTES

Product capability without invented traction.

Full changelog →
2026.07

Quant source to lead-account routes

Authorized trading changes can feed owned destination accounts with separate route decisions.

SHIPPED
2026.07

Four-exchange account adapters

Binance / OKX have supported workflows; Gate.io / Bitget public interfaces and Shadow are validated.

SHIPPED
2026.07

Public strategy and on-chain sources

Visible strategy sources and selected on-chain perpetual sources can enter the same route model.

BETA
NEXT

Expanded route protection

Route-level take-profit, stop-loss, maximum drawdown, and daily-loss controls remain planned.

PLANNED

START WITH THE PRODUCT

See what the four-exchange quant lead-trading bot is designed to solve.

The site explains current capability, use cases, known limits, and synthetic previews. It does not connect accounts or launch trading.