RUN / EXCHANGE CONNECTIVITY

One strategy. Multiple execution destinations.

Connections to Binance USDⓈ-M Futures, Bybit, OKX, BingX and Bitget preserve one preflight, audit trail and state-control model.

ONE VERSION / ONE HISTORYcontrolled
BACKTESTSimulationLIVEObserve
3.4.1

Signals, fills, limits and reconciliation

HASH 8F2A·91C7
SYSTEM DOMAIN04 / RUN

Move one version from Simulation to available live

  1. DISCOVER
  2. OPTIMIZE
  3. VALIDATE
  4. RUN
  5. OBSERVE
BNAPI · supported

Binance USDⓈ-M Futures

Automated futures execution through the user's API.

BYAPI · supported

Bybit

Connect an exchange account and run validated rules.

OKAPI · supported

OKX

Exchange execution through API key, secret and passphrase.

BIAPI · supported

BingX

Connect trading to the kquant research workflow.

BIAPI · supported

Bitget

Automate rules and monitor execution in kquant.

DECISION FRAMEWORK

Does observed execution still match the frozen strategy?

Follow the chain from signal and preflight to order, actual fill, exchange state and reconciliation. A missing link is an operational exception.

01

Observe in Simulation first

02

Use minimum live size

03

Halt on critical mismatch

OUTPUT

Execution audit trail

Important

Historical, statistical and model results do not promise future returns. kquant provides computational tools and technical execution, but does not assess whether a specific trade is suitable for a user.