RUN / SECURITY

Limit system access to exactly what execution requires.

Credentials are encrypted, permissions are minimized, withdrawal access is not required and critical uncertainty moves automation into halt.

Launch research Explore the details ↓

SYSTEM DOMAIN04 / RUN

Move one version from Simulation to available live

DISCOVER
OPTIMIZE
VALIDATE
RUN
OBSERVE

Encrypted credentials

Sensitive exchange credentials are stored encrypted.

Minimum permissions

Trading access does not require withdrawal permission.

Isolation

Use a dedicated subaccount and IP whitelist.

Fail closed

Critical divergence stops new automated actions.

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.

Observe in Simulation first

Use minimum live size

Halt on critical mismatch

OUTPUT

Execution audit trail

Before connecting

Minimum API credential checklist

Exchange account settings remain part of the security model even when kquant verifies the connection.

01
Create a dedicated subaccount for automation.
02
Issue a separate API credential only for kquant.
03
Do not grant withdrawal permission.
04
Add an IP whitelist where supported.
05
Verify market and position mode.
06
Start in Simulation and with minimum size.
07
Keep independent exchange access and a kill switch.

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.