Your QFEX session, from connection to Stop.
A practical guide to the QFEX mode released in Vesper. Follow the account and permission checks first, understand the settings, then learn how to recognise a running session and a completed stop.
Before connecting: separate the two accounts
You need an eligible QFEX account and a wallet for Vesper. Complete QFEX onboarding and check its current deposit instructions yourself. The Vesper wallet signature identifies your controls; it does not fund QFEX or replace the exchange API key.
Use a dedicated QFEX account or subaccount and avoid unrelated orders while assessing the bot. Shared collateral and manual trades can complicate both risk and accounting. This guide is educational, not a recommendation to deposit a particular amount or increase leverage.
Create a key for one QFEX account
On qfex.com, open your profile in the bottom-right corner, find Developer Settings, then choose Generate public and secret API Keys. Enable 2FA if required. Name the key Vesper and select one specific account, not All accounts.
Enable Execute orders, View orders, View positions and View balance. Leave Deposit and withdraw disabled. QFEX documents account scope and permissions separately; review both. Save the secret securely when it is shown and never paste it into messages or screenshots.
The current integration uses an API key. Do not follow a different provider’s authorization walkthrough. The official illustrated API-key instructions show the exchange screens; their appearance and requirements may change.
Select QFEX and bind the key in Vesper
Open the Vesper beta connection page, select the QFEX tile and connect the wallet you intend to use for session controls. The reviewed interface supports the wallet picker, including WalletConnect. Sign the account-view request when prompted.
Enter the public and secret API-key values only into the dedicated QFEX form on the correct SypherScore domain. Select Connect with API key, review the wallet request and sign to bind the key. Wait for validation before opening the cabinet. Neither a wallet connection nor a stored key starts trading.
Vesper requires access to this trading credential to act on your account; it is not a read-only connection. Do not provide your QFEX password, MFA code, wallet seed phrase or main-wallet private key. If access is refused, stop here and check the displayed reason rather than repeatedly replacing keys.
Choose the released mode and understand size
Open Strategy & settings. The reviewed release offers Risk core on SNDK-USD. GOLD and TAIEX are disabled with Soon labels. There is no supported instruction here for enabling them.
The allocation input multiplied by the Vesper leverage input gives a requested order-size budget. The current interface accepts a requested range of $40–$1,000. Its multiplier does not change leverage on your QFEX account. The exchange’s collateral rules and available balance still determine what it will accept.
Example, not a deposit recommendation: $20 × 2 gives a $40 requested size. It does not prove $20 is enough collateral for two resting sides, existing exposure or adverse movement. The engine may fit the size down to available margin. The allocation is not a loss limit or an isolated-margin guarantee; the reviewed mode uses cross margin.
Save first, then sign Start
Select Save settings and wait for confirmation. Check the saved market and size on returning to the cabinet. The interface says saved settings apply at the next Start; do not assume editing sliders changes a running session.
Press Start QFEX, read the requested action in your wallet and sign only if it matches your intention. Starting means the request is being processed. Wait for the session state and activity to confirm what the engine is doing. A refused signature or rejected request is not a successful Start.
Risk core may wait, reduce size or pause new entries in expensive conditions. Waiting is not a reason to increase exposure. Do not run a second session merely because the first has not produced a fill.
Read the live card without filling in missing data
TRADING describes an active session. ENTRIES PAUSED means new entries are blocked, not that the account is necessarily flat. STOPPING means cleanup is in progress. State unknown or unavailable data means the interface cannot confirm the current state; trading may still be running.
Volume counts reported filled turnover, not the deposit or unfilled quote size. The current CPM and Cycle result are cycle estimates excluding fees and funding. Missing fees or maker share are displayed as unavailable, not measured zeros. A favourable cycle estimate is not a reconciled net result.
The general net CPM methodology includes actual trading costs. Do not compare its numbers directly with this partial cycle metric. Review remaining inventory as well as completed cycles; an open loss can coexist with favourable closed cycles.
Account for fees, funding and position risk
Read the selected mode’s guide and review the actual wallet authorization before signing. Venue fees, funding and trading risks depend on your account and market.
QFEX documents hourly funding with symbol-specific active hours; 24/7 trading does not mean funding is charged continuously. Read the current fees and funding rules and use actual account records. Spreads, fills, collateral and liquidation risk remain separate considerations.
Stop, wait for cleanup and verify the account
Press Stop QFEX and sign the Stop request. The reviewed interface confirms acceptance before cleanup is finished. Wait through STOPPING; a successful request, a closed tab or lost connection is not proof of a flat account.
When the card returns to STANDBY, independently check the selected QFEX account for the actual position and outstanding orders. Confirm the bot’s exposure is flat and its orders are gone; inspect any other account activity separately. If state remains unknown or cleanup is delayed, inspect QFEX directly and contact support with the time and non-secret error text.
Do not revoke the key while expecting Vesper to complete an ordinary cleanup: removing authorization can prevent further cancellation or closing attempts. If credentials are suspected compromised, use QFEX’s own controls and support promptly. Revoking a key does not itself close a position.
History, reconnection and replacing a key
My results shows QFEX session records separately from other venues. An unavailable history is not an empty history, and historical CPM keeps the same cycle-only accounting limitation. Closing your browser is not a signed Stop; reconnect and read the state before issuing another Start.
For a planned key replacement, Stop first, confirm cleanup and return to Connect. Choose Use a different API key or Replace key, supply a dedicated replacement for the intended account and follow validation. Do not replace access while a session is still running.
If WalletConnect has expired, return to Connect and reconnect the same wallet. For rejected keys, review the selected account and four permissions. For margin warnings, distinguish your requested size from the exchange’s actual account leverage. Do not solve a warning by automatically increasing leverage.
Sources and scope of this guide
Reviewed 26 September 2026 against the public Vesper QFEX connection, settings and session interface. This review did not submit keys, sign wallet messages, place orders or independently audit engine behaviour. Availability and account checks can still reject a connection.
Primary references: API-key setup and scope, contract specifications, margin and liquidation. For general Vesper costs see Pricing; for other venues use their own guides.
Questions
Does connecting my wallet start QFEX trading?
No. The wallet connection, API-key validation, saved settings and signed Start are separate steps. Confirm the session state after Start.
Does the Vesper leverage slider change QFEX account leverage?
No. It multiplies the allocation to set requested size. Actual QFEX account leverage and collateral requirements are separate.
Why does QFEX show a different CPM from net CPM?
The current QFEX display is a cycle estimate excluding fees and funding. Net CPM needs a consistent result including costs and the treatment of remaining inventory.
When can I treat Stop as finished?
After cleanup is confirmed and you have checked the actual account for flat bot exposure and no remaining bot orders. Stop acceptance alone is not completion.