← Legal & Privacy

Terminal Beta — Risk & API Keys

Last updated: 2026-08-09

VoltArb Terminal is an invite-only beta for manual Futures–Futures hedging. This page covers trading risks, API key permissions, and position states for support.

1. Risk disclaimer (Terminal beta)

Terminal beta is invite-only. Access may be revoked without notice. Live trading uses real margin on your exchange accounts — you can lose some or all of the allocated notional.

VoltArb Terminal is not a trading bot, signal service, or investment advice. Every Live Open requires an explicit confirm in the ticket (including hotkey O). Paper mode simulates fills; Live sends real market orders.

Only manual Market Futures–Futures (F–F) Open/Close is supported. Spot, transfer, withdrawal, or cross-venue funding arb is out of scope.

Live Open / Paper tradeable allowlist is Binance, OKX, Bybit, Bitget, Gate, MEXC, BingX, Aster, GRVT, Hyperliquid, KuCoin, Phemex (USDT perps). Open still requires fresh server-side permission proof — currently proven for Big4 + Gate + BingX + Hyperliquid (agent) + Aster (V3 agent) + KuCoin (`GET /api/v1/user/api-key`) + Phemex (futures account + withdraw-history 403). MEXC/GRVT remain fail-closed (no introspectable withdraw-proof). Hyperliquid/Aster: store master address as API key and approved agent private key as secret.

Stop-loss / take-profit auto-close runs in Paper only. On Live, SL/TP levels (if shown) are monitor/warn only — they do not protect the position; you must Close manually.

Concurrent Live Opens are capped on the Terminal desk (default 3). Close or reconcile before opening more.

Scout Live execution is disabled (post-beta). Scout, if shown, is Paper-only and is not Live auto-trading. API keys require Test→Save with Read+Trade only (Withdraw off).

Quotes and books can lag or disconnect. Stale or thin-book guards block Live Opens but do not guarantee fill quality. Partial fills and one-sided legs are possible.

Operators may engage a durable kill switch that blocks new Opens only; Close and reconciliation remain. Beta software may contain defects — use restricted keys and small size.

2. API key permissions

Required exchange permissions: Read + Trade (Futures/perpetuals). Withdraw, Transfer, and Wallet permissions must be OFF.

Never paste keys into chat or tickets. Keys are encrypted per-user on the server; validation checks Read+Trade and rejects withdraw-enabled keys.

OKX, Bitget, and KuCoin require an API passphrase in addition to key and secret.

Hyperliquid and Aster Live Open use wallet-agent credentials: api_key = master 0x address, api_secret = approved agent private key (Aster: canPerpTrade, canWithdraw=false). HMAC-only Aster keys are not accepted for Open.

Use separate sub-accounts or restricted keys where your exchange allows. Rotate keys if exposed.

Test → Save flow in Terminal Execute checks permissions before storing. Unsupported or inconclusive checks require manual review — do not proceed with unsafe keys.

3. Unknown, Reconcile, and support

Unknown: local journal lost sync with one or both venue legs. Do not assume flat — use Reconcile or contact support.

ReconciliationRequired (recovery_required): operator action is needed to match durable order IDs on both venues before new Opens on that route.

Partial / Stuck / Error: treat as live risk — close residual manually or reconcile. Copy diagnostic from the Dock or ticket and send via support Telegram (no secrets).

Support contact: Telegram hub linked in the site header. Include the redacted diagnostic JSON (position id, symbol, venues, status, lifecycle, order ids).

4. Eligibility

You must be legally allowed to trade crypto derivatives in your jurisdiction. Beta access does not waive local restrictions.

Continued use after policy updates constitutes acceptance. See also the general Legal & Privacy page for data handling.

Support: @VoltArbitrage

We use cookies only for essential UI functionality. No analytics or marketing is enabled. You can accept or decline cookies to continue.