DoQuant
SECURITY
The platform does not custody funds and has no permission to withdraw or transfer from a user account. It sends orders to the exchange with trade permission only. User assets always remain at the exchange.
From key storage to strategy execution, what the platform does and what the strategy process may do.
Depends only on the Harbor SDK
Cannot read keys · No network access
Not placed in the strategy process
Decrypted only while an order is sent
Executes the order and keeps the assets
The network limit applies to the strategy process. The platform still sends orders to the exchange with trade permission.
Keys are stored encrypted and decrypted only while an order is sent.
Not written to logs, and not placed in the strategy process.
The only dependency is the Harbor SDK. CCXT, network access, the filesystem, and subprocesses are blocked.
These limits apply to the strategy process.
A strategy that fails the static scan cannot enter paper trading.
Log fields that look like keys are dropped.
The signal secret and the receiving address each have their own boundary for use and change.
Every instance keeps a signal secret of its own.
The full value is shown once, at creation or rotation.
Only an administrator can change the receiving address.
A change requires a second verification.
Risk notice: funds you commit can be lost entirely.
Register, connect an account, check the preview, then start on paper. Live trading comes after that.