CubeTrade User Manual

The workflows, checks, and notes below focus on common execution problems:

• You can read direction, but position size, stop loss, and order action often drift apart.
• You switch between exchanges and accounts and may select the wrong exchange, account, or symbol.
• Chart analysis and order entry happen in different places, which can lead to "right idea, wrong order."
• Different exchanges have different precision, step size, and minimum order rules, so manual input can fail repeatedly.
• After placing an order, it is not always clear whether protection orders, conditional orders, and position state are actually correct.

CubeTrade does not try to judge the market for you. Its job is to expose execution errors, omissions, and ambiguity earlier, so your trading actions stay more consistent.

• Exchange selector: controls both the chart data context and the trading context on the right.
• Market selector: the interface shows Futures or Spot. Futures is the short UI label; the current crypto trading path primarily uses each platform's USD-margined perpetual or linear contracts. Check the platform section for the exact account, API permission, and product requirements. The selected market is saved locally and restored on the next launch.
• Symbol input: fuzzy-searches symbols supported by the current exchange. For example, entering BTC can match BTCUSDT; unsupported symbols will not appear.
• Load: loads data for the current exchange and symbol.
• Timeframe buttons: the top bar shows 1m / 3m / 5m / 10m / 15m / 20m / 30m / 1h by default. Use the timeframe settings button on the right to manage which ones are shown.
• Chart Layout: the drop-down beside the timeframe controls switches chart profiles. Each profile saves its pane arrangement, pane timeframes, crosshair sync, realtime indicator preview, and complete indicator visibility, parameters, and display styles; selecting a profile applies and saves it automatically.
• New Layout: select New Layout in the Chart Layout menu to create an independent profile from the default layout. The same menu can rename the active profile. Profiles are stored separately for each exchange + symbol, so Binance BTCUSDT and ETHUSDT do not overwrite one another.
• Derivatives Metrics: opens a read-only derivatives metrics view for the current exchange, symbol, and timeframe.
• Market-data status: the top-bar dot and text show the active market-data path. Green WS live means WebSocket data is active; yellow Connecting market-data WS means CubeTrade is connecting, while REST fallback means data has fallen back to REST and may be less timely; red Market data connection interrupted means the realtime market-data path is unavailable.

Timeframe settings are saved per exchange. Native K-line support differs by exchange, so the popup only shows items available for the current exchange.

• Selected: timeframes shown in the top bar. At least 1 item is kept, and up to 8 items can be shown. The default set is 1m / 3m / 5m / 10m / 15m / 20m / 30m / 1h.
• Available: timeframes supported by the current exchange but not currently shown in the top bar.
• Custom: adds aggregate timeframes that the current exchange does not provide natively but CubeTrade can build from nearby same-level candles, such as 10m or 20m. Minute timeframes are built only from minute candles, hourly timeframes only from hourly candles, and day/week timeframes only from daily candles.
• When switching to a custom aggregate timeframe for the first time, CubeTrade prioritizes local cache and the current visible range first; older history continues to fill in the background.

Timeframe settings example:

• Trade: Futures shows the order panel, positions, open orders, and detail dialogs. Spot shows asset balances, open orders, and its dedicated buy/sell panel.
• History: Futures shows fills, order history, and position history. Spot shows only fills and order history; Spot assets are shown in the trading panel instead of as leveraged positions.
• Tracking: order watch and price alerts. Order watch tracks limit entry orders and adds stop loss / take profit after the main order fills; price alerts are used to view, edit, and cancel chart alert lines.
• The panel button on the right side of the top bar hides or shows the right trading panel. When hidden, the chart area expands for single- or multi-chart analysis; the trading account, exchange, and symbol context is not changed, and showing the panel restores the same trading context. The hidden or visible state is saved locally and restored on the next launch.
• The restore default window size button on the right side of the top bar immediately returns the main window to the default size, useful after manually resizing the window too large or too small.
• When the main window closes, CubeTrade saves its current size and position and tries to restore them on the next launch. If the saved position is no longer available after display changes, the app falls back to the default window size and placement.

• Crosshair: shows the time label at the bottom and price or indicator value labels on the right.
• The latest price label also shows the candle countdown, using the same color as the price label. When realtime market events include exchange event time, the countdown is calibrated from exchange time so local clock drift does not make candle close display a few minutes early or late.
• Drag empty space to pan the chart horizontally.
• On initial load, timeframe switch, or split-layout entry, the chart keeps about six candles of reading space to the right of the latest candle. After you pan manually, realtime updates respect your last viewport instead of forcing the chart back to the far right.
• When the left side approaches the boundary, earlier historical data is loaded in the background.
• The left toolbar provides drawing, measurement, position, Fibonacci, text, and price-alert tools.
• When Trading Markers is enabled in System Settings, the chart shows matching positions and open orders for the current exchange, account, and symbol as horizontal reference lines. Positions and open orders can be toggled separately. These markers are visual references only; the right-side trading tables remain the source of truth.

• Chart Settings -> Chart Layout supports one to nine charts and 41 common geometries. Choose the chart count first, then choose an arrangement for that count; mirrored and rotated arrangements are grouped together, and pane timeframe fields expand and contract with the count.
• The top-bar layout menu switches, creates, and renames profiles. Each profile automatically saves its geometry, pane timeframes, crosshair sync, realtime indicator preview, and complete indicator visibility, inputs, and styles. There is no separate Save command.
• Layout profiles are isolated by exchange + symbol. Different symbols on the same exchange, and the same symbol name on different exchanges, do not overwrite one another.
• When an unconfigured multi-chart view is first created from a single chart, new panes use the current indicator settings as their initial settings. The next time the profile is opened, each pane restores its own saved timeframe and indicator settings.
• If the chart count stays the same and only the geometry changes, each pane keeps its stable identity, timeframe, indicator settings, and loaded data instead of being recreated.
• In a multi-chart layout, the pane with the thin highlighted border is the current action target. Top-bar timeframe buttons, drawing actions, and indicator changes while Sync Indicator Settings is off apply only to that pane. Changing one pane's timeframe does not reload the other panes. A single-chart layout has only one target and therefore does not show a selection border.
• When Sync Indicator Settings is on, indicator changes apply to every visible pane. When it is off, each pane can enable, hide, configure, or remove indicators independently. Crosshair sync shares only the time-axis vertical line, not a price-axis horizontal line whose meaning changes across timeframes.
• Multi-chart layouts show multiple timeframes for the current exchange and symbol. They do not turn the right trading panel into multiple trading contexts. Use multiple windows for cross-exchange, cross-symbol, or cross-account monitoring.
• Pane timeframes use the same capability set as Timeframe Settings and are grouped by Within 5m / Within 1h / Within 1D / Within 1W / Within 1M. Native exchange resolutions use native data first; local aggregation is used only for non-native resolutions that can be built from same-tier integer-multiple candles.
• With realtime indicator preview off, an unclosed candle updates only its candle body/wick, price line, countdown, and current volume; indicators update after candle close. When preview is on, unconfirmed indicator values are shown, which uses more CPU and may repaint or retract before close.
• When you switch exchange, market type, or symbol, the chart enters a loading state and starts a new chart context. Candles, indicators, sub-chart scales, viewport state, and WebSocket updates from the previous symbol are not written into the new context; in multi-chart layouts, each pane loads its own timeframe and returns to that timeframe's recent data tail when ready.

Complete geometry catalog (the left number is the chart count; the small number beside each thumbnail is its arrangement number):

Chart layout settings example:

Hiding the right trading panel gives multi-chart layouts more horizontal room. A single chart is best for close reading of one timeframe. Dual and asymmetric layouts are useful for primary-versus-secondary timeframe comparison. Regular grids work well for structures such as 1m / 5m / 10m / 15m.

• Hover over a main-chart or sub-chart indicator row to reveal three controls: the eye temporarily hides or shows the indicator, settings opens that indicator's configuration page, and remove disables it in the current pane.
• Multiple series from one indicator share a single legend row. For example, enabling EMA 21 / 55 / 100 shows EMA 21/55/100 instead of one row per average. SMA, Vegas, and similar grouped indicators follow the same rule.
• Hide and remove are different. Hide changes only visibility and preserves the indicator configuration. Remove disables the indicator; enable it again from Chart Settings when needed.
• The toggle below the main-chart indicator list collapses or expands the entire main indicator legend. The exchange, symbol, and timeframe title remains visible. Sub-chart legends stay with their panes and do not have a group-collapse control.
• Move the pointer over the main chart's right price scale to reveal A / L at the bottom. A toggles automatic scaling so visible data fits the current height. L switches between normal and logarithmic price scales. A highlighted letter means that mode is active.

The current version provides seven themes, grouped as dark and light choices in the selector:

• Midnight Blue: preserves the earlier deep-blue chart and interface palette for users accustomed to the previous appearance.
• Classic Dark: uses a neutral charcoal background for low-light environments and everyday charting.
• High Contrast Dark: the default theme, with a near-black background, clear boundaries, and highly legible text for dense charts and long sessions.
• Ink Teal: combines ink-like surfaces with restrained teal accents to reduce large bright areas.
• Classic Light: uses a cool gray-white background for daytime work, document comparison, and screenshots.
• Daylight: provides a brighter neutral white background and crisp separation for well-lit environments.
• Soft Light: reduces white-background glare while preserving necessary contrast among axes, candles, and controls.

The three swatches on the right of each theme preview the chart background, bullish candle, and bearish candle colors. They come directly from that theme's current defaults; after you choose a Market Color Scheme manually, the actual candles continue to follow your selection. Crosshair contrast also adapts to each theme. High Contrast Dark gives the horizontal and vertical lines different emphasis and uses a more clearly spaced vertical dash pattern so it does not look solid.

The following screenshots show three representative themes:

Classic Dark example:

Classic Light example:

Ink Teal example:

• Main Wallet Address is required.
• Without it, CubeTrade cannot correctly fetch balance information, risk calculations cannot be trusted, and entry-related features may not work.

Hyperliquid account configuration example:

1. Enter credentials.
2. Click "Test Trading Connection".
3. Then click "Test Trading Credentials".
4. Start trading only after both tests pass.

CubeTrade supports a futures and cash-spot trading workstation. It does not provide withdrawals, transfers, internal transfers, fund collection, or any workflow that moves assets out for the user.

Spot trading is currently connected for Binance, OKX, Bybit, Bitget, Gate, HTX, Deribit, Kraken, and Hyperliquid. Public market data being visible does not prove that the current account has Spot enabled or that its API key has the required permissions; rely on the credential tests and the trading-panel response.

When creating API credentials, use the least-privilege model:

• For Futures: derivatives account read permission, used to read balances, positions, open orders, and order history.
• For Futures: derivatives trading permission, used to place orders, cancel orders, adjust leverage, and manage position-protection orders.
• For Spot: Spot account read and trade permission, used for asset balances, open orders, order history, fills, spot orders, and cancellations. Spot does not need leverage or position permissions.
• Not required: withdrawals, on-chain transfers, account transfers, sub-account fund transfers, or fund-management permissions.
• Not required: margin trading permission. CubeTrade does not currently connect Spot margin trading.

Use this table as the platform-specific reference:

If you are unsure whether the permission names you see match what CubeTrade needs, check in this order:

1. Look for derivatives/futures account read, balance, position, and order-view permissions.
2. Then look for derivatives/futures order placement, cancellation, position settings, and order-management permissions.
3. Do not enable withdrawals, transfers, fund management, or sub-account fund transfers.
4. If the exchange only exposes Read / Trade / Withdraw, CubeTrade needs only Read + Trade.
5. If the exchange uses scopes like Deribit, prefer read-only wallet scopes such as wallet:read, not wallet write scopes.

Stock / TradFi perpetuals are derivatives that track stock prices; they do not give you shares or shareholder rights. Availability depends on account region, KYC level, futures-account status, and exchange eligibility. Finding a symbol or loading its chart does not prove that your account may trade it.

Before the first trade:

1. Open the required futures account on the exchange website or app.
2. Complete required KYC, risk quizzes, and regional eligibility checks.
3. Read and accept the stock / TradFi perpetual terms on the exchange. CubeTrade never accepts legal or product agreements for you.
4. Grant the API key only derivatives read and trade permissions. Do not grant withdrawal, transfer, or wallet-write permissions.
5. If the API key uses an IP allowlist, add the public outbound IP used by CubeTrade trading requests.
6. Return to CubeTrade, rerun both trading tests, then verify with a small order.

Exchange notes:

• Binance: open Futures -> USDⓈ-M Futures -> TradFi, select a contract such as NVDAUSDT, and finish any agreement, activation, or quiz. The API key needs Enable Reading + Enable Futures. Error -4411: Please sign TradFi-Perps agreement means the TradFi agreement must be completed on Binance first.
• Bybit: use the master account to open the native stock perpetual on the website or app and accept its terms. This is separate from MT5 CFDs under Trade -> TradFi. Normal trading requires ContractTrade: Order, Position; do not grant CubeTrade wallet-transfer or withdrawal permissions to accept terms through an API.
• OKX: complete KYC Level 2, confirm the stock perpetual appears in the account-eligible SWAP list, and enable Read + Trade. Live API error 59113 means the KYC level is insufficient. Withdraw is not needed.
• Bitget: confirm regional and futures-account eligibility, then enable Trade read-write access for futures / USDT-FUTURES. Codes 40000, 40040, 40301, and 40916 indicate region, API permission, product access, or futures-service restrictions.
• Gate: initialize and fund the perpetual account for the settlement currency, and set perpetual contract to Read-write. USER_NOT_FOUND means that futures account is not initialized.
• HTX: open the USDT-M futures account, complete at least KYC Level 2, and enable readOnly + trade. Level 2 API leverage is capped at 20x; higher leverage requires Level 3.
• Kraken xStocks and Hyperliquid HIP-3 stock perpetuals are not yet connected to CubeTrade's current symbol and order routes. Deribit is not currently a stock-perpetual route either.

Product activation, regional restrictions, KYC, agreements, and futures-account initialization must be completed on the exchange. CubeTrade cannot perform them for you.

• Mainnet credentials cannot be used directly on testnet or demo networks.
• Testnet credentials cannot be used on mainnet.
• If an exchange has multiple networks, credentials and network route must match exactly.

• Many exchanges support or require an IP allowlist for trading credentials. This checks the public outbound IP used by trading requests, not the private address shown on your local machine.
• If you enable an IP allowlist on the exchange, CubeTrade trading requests will be accepted only when the outbound IP is on that list.
• You usually have two options:
• Run CubeTrade from a network whose public IP is already allowlisted.
• Configure a proxy for the trading route in exchange settings, forwarding right-side trading requests through an allowlisted public IP.
• Market data, candles, and charts on the left follow the system proxy: Windows network proxy settings, macOS network settings, or Linux proxy environment variables. They connect directly when no system proxy is set.
• CubeTrade account-level proxy settings affect only the right-side trading interface. When no account proxy is configured, trading follows the system proxy too; an account proxy overrides it.
• If a proxy is needed, prefer SOCKS5 or HTTPS. Use plain HTTP only when you know the route requires it.
• After configuring a proxy, run "Test Trading Connection" and "Test Trading Credentials" again.

Useful exchange differences:

• Binance: if trusted IPs are enabled and your outbound IP is not listed, requests are rejected. Binance Support also explains that withdrawal permission requires IP access restriction; CubeTrade does not need withdrawal permission.
• OKX: OKX Help recommends binding API keys to IP addresses. API keys that are not IP-bound and have Trade or Withdraw permission may be deleted after long inactivity. CubeTrade does not need Withdraw, but if Trade is enabled, an IP allowlist is still recommended.
• Bybit: the official API key pages separate Mainnet and Testnet, and keys must be created on the website. Use the permission groups shown on the current page to enable contract/derivatives trading and the necessary account-read items; do not enable transfer or withdrawal permissions.
• Bitget: demo trading uses the main API host, but private requests require demo API keys and the demo-trading marker. A mainnet credential cannot be used as a demo credential.
• Gate: the brand site currently uses gate.com, while API routes still follow the official mainnet/TestNet API hosts. Mainnet keys and TestNet keys cannot be mixed.
• HTX: CubeTrade cannot automatically complete write verification against a unified HTX test network. When enabling HTX trading for the first time, verify reads, order placement, cancellation, and protection orders with a small mainnet account.
• Deribit: Deribit Support explains that API keys can be configured with scopes. CubeTrade recommends only the trading read-write scope and wallet read-only scope it needs.
• Kraken Futures: Kraken Support separates General API from Withdrawal API. CubeTrade needs General API trading access, not Withdrawal API access.
• Hyperliquid: official materials focus on the API wallet / agent wallet signing model rather than a traditional centralized-exchange API-key allowlist model. Do not mix up the main wallet address and API wallet address.

Account configuration example:

• Lines: trend line, ray, horizontal line, horizontal ray, vertical line, cross line, extended line, info line, trend angle.
• Channels: parallel channel, regression channel, flat-top/flat-bottom channel, disjoint channel.
• Shapes: rectangle, triangle, path, up arrow, down arrow.
• Patterns: XABCD, ABCD, three-wave, five-wave, eight-wave, custom wave.
• Analysis: measurement, Fibonacci, Fibonacci trend extension, Fibonacci channel, Fibonacci time zone.
• Positions: long position, short position.
• Alerts: price alert.

• Two-point tools complete after two clicks.
• Three-point tools complete after three clicks.
• Sequence tools, such as waves and paths, can be ended early with right-click after at least two points.
• After one object is completed, CubeTrade returns to cursor mode. Select the tool again when you intentionally want another object of the same type.
• Hold Shift while placing a two-point tool or dragging an endpoint to constrain it horizontally, vertically, or diagonally. Hold Cmd/Ctrl during placement for temporary strong magnet; releasing it restores the previous magnet mode.
• A drag still completes when the pointer leaves the chart before mouse release, so objects do not remain in a half-finished drag state.
• Position tools support entry, target, stop-loss area, and risk/reward information. When selected, key anchor points can be dragged.
• Price alert: click a chart price level to add an alert line. Alerts are bound to exchange, account, and symbol, not timeframe.
• Text tool: click to type directly; double-click existing text for quick text editing. Submitted text stays at its creation anchor instead of being pushed to the chart's left edge when it is long. Callout and arrow-marker targets can be dragged independently from their text anchors; moving the whole object moves both. Select one text object and open Properties to edit text, font, position, background, border, coordinates, and visibility.
• Trading markers: position and open-order lines come from the right-side trading panel query results and appear only when exchange and symbol match. They move with chart zooming, panning, and price-scale changes instead of staying fixed on the screen.

• Magnet: supports weak and strong magnet modes.
• Lock: locked objects cannot be deleted by button or keyboard.
• Hide/show: toggles object visibility.
• Delete: applies only to unlocked objects.
• Context menu: right-click a drawing object for common actions such as copy, delete, lock, and properties.
• Multi-select: hold the system multi-select modifier and click objects.
• Marquee select: in cursor mode, hold Shift and drag from empty chart space to add fully enclosed objects to the current selection.
• Handles: rectangles and full measurement boxes expose four corner and four edge handles. Price Range changes only price, Time Range changes only time, and Regression Channel exposes separate upper/lower deviation handles while endpoints change the regression interval.
• Fibonacci Retracement: configure levels, colors, trend line, and reverse direction in Properties. Press R on a selected Fibonacci object to reverse its level direction. Extended lines, rays, and channels can be selected from their currently visible segment even when original endpoints are off-screen.
• Properties panel: select a single object, then open it by double-clicking, except for text objects, or through the object menu. Common settings include color, line style, width, fill opacity, coordinates, visibility, and lock state; text objects use the same properties panel.

Main-chart indicators:

• Bollinger Bands: used to observe price volatility range and band width changes. Common use is checking whether price is near the upper/lower band and whether band width is contracting or expanding.
• EMA: currently available in 12 / 21 / 34 / 55 / 100 / 200 groups, with only 21 enabled by default. EMA reacts faster to new price data and is useful for short, medium, and long trend direction and moving-average alignment.
• SMA: currently available in 12 / 21 / 34 / 55 / 100 / 200 groups, with only 21 enabled by default. SMA is smoother and can be useful for steadier trend structure and support/resistance reference.
• Vegas: provides 144 / 169 and 576 / 676 channel groups. Useful for medium-to-long trend bands, channel compression/expansion, and price location relative to the channel.
• SuperTrend: controlled by period and multiplier, commonly used to read trend switches and dynamic trailing lines.
• Donchian: shows highest/lowest ranges and midline for the configured period. Commonly used for breakouts, pullbacks, and range boundaries.
• VWAP: accumulates typical price and volume by natural day to show the volume-weighted average price. It helps read intraday price location relative to volume-weighted cost.
• Pivot Points High Low: confirms local highs and lows from closed candles, then marks regular pivots and missed-reversal structures. A larger pivot length confirms later but filters more short-term noise; an unclosed tail is never treated as a completed pivot.
• Key Levels: builds support and resistance zones from confirmed price pivots. Zones can be aligned when they overlap, extended to the right, and labelled. Level count limits the active recent zones; zone width and maximum-zone percentage prevent overly wide or dense zones. After a confirmed candle close breaks a support or resistance zone, that level is invalidated and stops extending to the right; later confirmed pivots can create new levels. With realtime indicator preview enabled, only levels affected by the unclosed tail are previewed incrementally; candle close confirms the result.
• TD Sequential: counts 1 ~ 13 with the configured comparison period to show consecutive buy/sell-pressure rhythm. You can show or hide in-progress counts. When zoomed out and labels overlap, the chart prioritizes key 9 / 13 labels; zooming in reveals more count labels. Tail counts in realtime preview may change with the unclosed candle; the closed-candle sequence is final.
• Smart Money Concepts (SMC): marks internal and swing structure, BOS/CHoCH, order blocks, equal highs/lows, fair value gaps, strong/weak highs and lows, and premium/discount zones on the main chart. Historical or recent mode can be selected, with separate controls for structure lengths, order-block count and filter, mitigation basis, equal-high/low threshold, and FVG extension. You can also choose colored or monochrome rendering, filter bullish and bearish internal/swing structures independently (all, BOS only, or CHoCH only), and adjust internal, swing, and EQH/EQL label sizes. Display filtering affects rendering only; it does not change structure confirmation or order-block mitigation. SMC organizes market structure; it is not an automated trading signal.
• Trading Sessions: draws the actual price-range boxes for the three default Asian, European, and North American sessions, with an optional Sydney session disabled by default. The Asian window connects Tokyo, Shanghai, and Hong Kong and is labelled Tokyo & Hong Kong; Europe uses London; North America covers core New York trading plus Chicago daytime activity and the settlement tail, labelled New York & Chicago, without the near-24-hour CME Globex overnight session. Default UTC standard-time windows are 00:00-08:00, 07:00-16:00, 13:00-22:00, and 21:00-06:00. Asia keeps a fixed UTC window, while Europe, North America, and Sydney shift one hour earlier during local daylight saving time. Each session can be enabled, named, timed, and colored independently. Price Range tracks session highs and lows dynamically; the label below the box can show cumulative volume and average close. Mid-range, forward extension, history retention, weekdays, and weekends are enabled by default. Disabling weekdays or weekends filters complete sessions by their opening date. The chart display timezone does not change session ownership; this indicator is intended for intraday timeframes.

#### SMC Zone Alerts

• Select an Alert Timeframe in Smart Money Concepts settings and enable sound or popup alerts. The background runtime subscribes only when SMC is enabled, an alert timeframe is selected, and that timeframe is currently present in the single- or multi-chart layout. Removing the timeframe from the layout also stops its alerts.
• Alerted regions include internal order blocks, swing order blocks, premium, equilibrium, and discount zones. Closed-bar SMC output supplies the regions. Between candle closes, live WebSocket data only consumes this fixed snapshot; it does not recalculate, move, or rewrite the indicator regions shown on the chart.
• When a candle starts outside a region, its first wick or body touch/entry triggers the alert. If that candle opens inside the region, it does not produce an entry alert. Historical loading, refresh, and snapshot replay do not backfill old alerts.
• Invalidation is evaluated from live data without waiting for candle close. Order blocks use the configured SMC mitigation basis (wick high/low or close). A move above the premium-zone upper boundary or below the discount-zone lower boundary triggers invalidation; equilibrium provides touch alerts only. Live invalidation ends only the current alert context and does not delete or redraw the indicator region. The next closed-bar SMC calculation remains authoritative for retaining or updating that region.
• By default, each region lifecycle alerts once. With Alert Again After Exit enabled, price can trigger again on a later candle after leaving the region. Repeated WebSocket updates within the same candle do not produce duplicate alerts, and an invalidated region cannot produce another entry alert.

Sub-chart indicators:

• Volume: shows volume for each candle.
• Volume SMA: moving average of volume; meaningful only when volume is enabled. If volume is hidden, Volume SMA is hidden too.
• RSI: used to read strength and overbought/oversold zones. The UI can configure both RSI period and RSI SMA period.
• RSI Swing Filter: a custom sub-chart indicator based on RSI12 and optional SMA14. It helps inspect swing baselines, divergence lines, and labels after overbought/oversold moves. It does not replace classic RSI; it is meant to assist with swing turns, repeated divergence, and potentially invalidated structures. When realtime indicator preview is enabled, the unclosed tail previews RSI/SMA, reference lines, and structure labels that may become valid; formal divergence and reset annotations are still based on closed-bar confirmation.
• MACD: used to read trend momentum changes; fast, slow, and signal lines can be configured separately.
• KDJ: used for short-term swings and turning-point rhythm; period, K smoothing, and D smoothing can be configured.
• ATR: measures volatility itself, not direction. It is useful alongside stop distance and risk calculations.
• OBV: accumulates price movement and volume into one line, often used to check whether price and volume agree.
• DMI / ADX: uses +DI, -DI, and ADX to observe directional movement and trend strength. Each line can be shown or hidden separately.
• Stoch RSI: applies stochastic processing to RSI for a more sensitive oscillator view. RSI period, stochastic period, and K/D smoothing can be configured.
• CCI: observes how far typical price deviates from its recent average range.
• Williams %R: uses a 0 ~ -100 range to show where the close sits relative to recent highs and lows.

#### RSI Swing Filter Symbols

RSI Swing Filter is a CubeTrade custom sub-chart indicator. It does not replace classic RSI. It adds structure labels on top of RSI, including baselines, divergence points, hidden divergence, invalid/reset hints, and completion hints, to help read swing rhythm after overbought or oversold moves.

In short, B / T are baseline points, B1 / T1 and later labels are formal divergence points, and BX-B / TX-T means the old structure was invalidated and a new baseline was established. These labels are structure hints, not direct trading advice. They still need to be read together with trend, candle location, volume, and risk control. During realtime unclosed bars, preview labels may appear before confirmation; preview labels are only early structure hints and do not trigger sound or popup alerts. Sound and popup alerts are fired only for newly confirmed realtime labels after closed-bar confirmation, usually 1-3 bars after the preview; labels produced by historical loading, refresh, or backfill do not alert.

The chart settings dialog includes Chart Layout, main-chart indicators, and sub-chart indicators. Indicator settings show one indicator per row. Each indicator can configure visibility, inputs such as period or multiplier, line colors, and visible series. Bollinger, Donchian, Smart Money Concepts, RSI, RSI Swing Filter, MACD, KDJ, DMI / ADX, and Stoch RSI can separately control bands, zones, structures, histograms, sub-lines, baselines, and divergence line / label display scope. Channel or zone indicators can configure fill colors. Disabled indicators do not enter the calculation or rendering path. Use Reset to restore the recommended inputs and colors.

Indicator configuration example:

The top-bar Derivatives Metrics button opens a separate read-only window with chart-style views for funding rate, account long/short ratio, top account long/short ratio, and top position long/short ratio.

For futures and perpetual derivatives, candles show what has already traded. Derivatives market-statistics series are closer to the leveraged positioning layer: where funding cost sits, how crowded one side is, and whether large accounts are aligned with the broader account base. They should not be used as standalone trade signals, but they are useful as part of the pre-trade market context check:

Support matrix (current implementation):

• Funding rate: perpetual contracts do not expire, so exchanges use funding to keep contract prices anchored to spot or index prices. When funding is positive, longs usually pay shorts; when funding is negative, shorts usually pay longs. Funding is both a carrying cost and a crowding clue. Persistently high positive funding suggests crowded longs and higher cost to chase long exposure; persistently negative funding suggests crowded shorts and higher cost for short exposure.
• Account long/short ratio: shows how many accounts are net long versus net short for the current symbol. It reflects account-count sentiment, not position size. Many small accounts on one side do not necessarily mean most notional exposure is on that side.
• Top account long/short ratio: shows the account-count direction of large traders. Compare it with the broader account ratio; if general accounts lean strongly long while top accounts do not, retail-style sentiment and large-account direction may be diverging.
• Top position long/short ratio: shows the position-size direction of large traders and is closer to notional weight than account count. If top account ratio and top position ratio disagree, large-account headcount and actual position size are not aligned, so the signal should be read carefully.

Boundaries:

• These series come from the exchange's official statistics endpoints. They are not indicators calculated from OHLC candles.
• The view loads data for the current exchange, symbol, and timeframe. Supported series differ by exchange, and unsupported items are shown as unsupported.
• Historical depth, supported periods, and pagination limits differ by exchange. Some exchanges return only a small number of long/short ratio points, and funding rate history may use a different time granularity from ratio series.
• This page only reads data. It does not place orders, cancel orders, or change chart indicator settings.
• Derivatives metrics are not placed inside sub-chart indicators, so discrete market-statistics series are not mixed with continuous candle indicators.

References: [1] Binance Funding Rate History [2] Binance Long/Short Ratio [3] Binance Top Trader Account Ratio [4] Binance Top Trader Position Ratio [5] Bybit Funding Fee Calculation

• Main-chart indicators render below candles; candles remain the primary visual layer.
• Sub-chart indicators share the same time axis as the main chart. When disabled, their panes collapse instead of leaving long empty space.
• If you are new to the app, do not enable every indicator at once. Start with one or two trend indicators, then add one sub-chart indicator if needed.

• macOS: Command + Shift + N; Windows / Linux: Ctrl + Shift + N: open a new CubeTrade window.

• Delete / Backspace: delete selected drawings. Locked objects are not deleted.
• Esc: cancel the current drawing tool or return to cursor mode.
• Cmd/Ctrl + Z: undo.
• Cmd/Ctrl + Shift + Z or Ctrl + Y: redo.
• Cmd/Ctrl + C / V: copy / paste drawing.
• Cmd/Ctrl + Shift + C / V: copy / paste style.
• Cmd/Ctrl + A: select all drawings.
• Shift + drag empty chart space: marquee-select and add drawing objects.
• Cmd/Ctrl + ]: bring to front; Cmd/Ctrl + [: send to back.

• M: toggle magnet.
• Shift + M: strong magnet mode.
• Hold Cmd/Ctrl during placement: temporary strong magnet; release to restore the previous mode.
• L: lock selected objects.
• U: unlock selected objects.
• R: reverse the selected Fibonacci direction; for a selected risk/reward position tool, switch long/short direction.

• V cursor
• ⌥T trend line
• ⌥H horizontal line
• ⌥J horizontal ray
• ⌥V vertical line
• ⌥C cross line
• ⌥P parallel channel
• ⌥B rectangle
• ⌥G triangle
• ⌥M measurement
• ⌥⇧R price alert
• ⌥F Fibonacci
• ⌥L long position
• ⌥S short position
• ⌥X XABCD
• ⌥A ABCD

• The entry window combines entry price, stop price, account balance, leverage, and risk tier to calculate risk budget, stop-loss risk, stop distance, estimated position size, notional value, and margin.
• Risk Management is enabled by default and derives entry quantity from the selected risk tier and stop distance. The quantity input and position-size slider remain directly adjustable: a manual change automatically exits risk management, while adjusting the risk tier enables it again. It only performs risk calculation and local constraints; it does not mean CubeTrade is judging market direction.
• The entry window reads quantity precision, step size, minimum quantity, and minimum notional from the current exchange and symbol, and reapplies the matching rules after a symbol switch. If the risk-derived size is below the exchange minimum, the window shows the minimum tradable quantity. If that quantity exceeds your risk budget, skip or redesign the trade instead of increasing size only to pass validation.
• The default Risk Management settings are 0.5% single-trade risk, 0.5% stop offset, and 1.5R reward-to-risk. If you do not adjust them, the entry window uses this default profile to calculate allowed size and the first take-profit reference.
• The main adjustable controls are Stop Offset and Risk Tier: stop offset is usually available from 0.5% to 2.5%, with the usable range constrained by current leverage; risk tier ranges from 0% to 2.0%, so the maximum single-trade risk is capped at 2.0% of account equity.
• Enable Stop Loss is treated as protective position stop loss by default. Stop-loss quantity does not scale with the take-profit percentage; when triggered, it follows whole-position protection semantics.
• Enable Take Profit is enabled by default. The default risk/reward is 1.5R, and the default take-profit percentage is 80%. The take-profit price is calculated from the current entry side and stop distance: long is entry + risk distance * R, short is entry - risk distance * R.
• The take-profit percentage slider controls the first take-profit level and provides 0% / 25% / 50% / 75% / 100% reference marks. CubeTrade currently manages only the first take-profit level; it does not automatically split second or third targets.
• After a market entry succeeds, CubeTrade immediately attempts to add protective stop loss and reduce-only limit take profit.
• For limit entries, CubeTrade first checks native exchange capability. If the exchange can safely express the requested protection, CubeTrade uses exchange-side binding. If not, CubeTrade uses order watch and waits for the main order to fully fill before adding protection.

• Native-support exchanges: the limit main order and protection parameters are submitted through exchange-native capabilities, and protection is handled by the exchange after fill.
• OKX: can express the limit main order, limit first take profit, and stop loss through native attached algo orders, including partial-position take-profit quantity.
• Bybit: can attach TP/SL to a limit main order request, but the first take-profit quantity is generated from the actual filled quantity of the main order. Therefore only 100% take-profit percentage uses the native path; the default 80% uses CubeTrade order watch.
• Exchanges or scenarios requiring CubeTrade order watch: the limit main order is submitted first. Before it fills, CubeTrade does not pretend that server-side protection is already bound. After fill, CubeTrade adds stop loss / take profit through order watch.
• Exchanges that do not meet safe-watch requirements: the UI asks you to disable the corresponding protection before submitting, then set it manually from position protection or standard TP/SL after fill.
• When using CubeTrade-managed protection, keep the CubeTrade process running. Minimizing or closing the primary window moves it to the system tray, and order watch continues.

Notes:

• Market orders usually execute immediately and should be understood as immediate execution, not as orders waiting on the book.
• Limit orders usually enter open-order state first and fill only when market price reaches your limit and matching succeeds.
• The value of the entry window is that it turns "how much risk do I want to take" into concrete position size, stop price, first take-profit price, and the post-order protection flow, reducing manual calculation and missed protection orders.

Entry:

Exit:

• The Position PnL field at the top shows floating PnL for the whole current position.
• The summary area estimates Est. Fill, Close Ratio, and ClosePnl from the current Position Qty.
• Use the Position Ratio slider and Size buttons to quickly choose 25%, 50%, 75%, or 100% of the closeable position.
• Limit exits also show Px Off. and Offsets, which generate a limit price from the current reference price. You can still type the price manually.

• The Spot panel is separate from the Futures panel. It provides market buy, limit buy, market sell, and limit sell, without leverage, short selling, futures positions, close-position actions, or position protection.
• Buying exchanges quote currency for base currency; selling disposes of base currency already held. A market buy submits a quote-currency budget, while a market sell submits a base-currency quantity. Limit orders also require a price and use base-currency quantity for order size.
• Orders are constrained by real available assets. Buys check available quote balance, sells check available base balance, and assets frozen by existing orders cannot be spent again.
• CubeTrade applies the current exchange and symbol's price precision, quantity precision, step size, minimum quantity, and minimum notional. If an order cannot satisfy the exchange rules, the UI blocks submission or shows the explicit exchange error.
• CubeTrade does not currently connect Spot margin, borrowing, naked short selling, reduce-only, or Futures-style TP/SL. Spot risk comes from actual holdings and available balances, not the leveraged-position risk model used by Futures.
• After a market switch, assets, open orders, fills, order history, and local tracking records remain isolated by market type. Spot never reuses Futures accounts, positions, or open orders.

• Shows key fields for the current position: side, leverage, entry price, mark price, PnL, margin, account balance, stop-loss/take-profit status, and more.
• Provides entry points to:
• Position Protection
• Standard TP/SL
• Market Close All
• Market Reverse
• Market Close All opens a confirmation window showing current position, entry price, current price, and PnL; after confirmation, CubeTrade submits a reduce-only market close order.
• Market Reverse opens a confirmation window showing current position, reversed position, reverse stop loss, maximum single-trade risk, notional value, and balance checks; after confirmation, CubeTrade first closes the current position at market, then opens the opposite position at market and places a reverse stop loss.
• Reverse stop loss defaults to 0.5% away from current price in the opposite direction, used to estimate the risk ratio of the reversed position.

Example:

Market close confirmation example:

The market close confirmation window lets you re-check the close action before submission. Focus on three things: whether this is the position you intend to close, whether current price and estimated PnL match your expectation, and whether the action button clearly says "Confirm Market Close". After confirmation, CubeTrade submits a reduce-only market order whose goal is to close the current position, not open an opposite one.

Market reverse confirmation example:

The market reverse confirmation window has more risk checks than market close because it is not just an exit. It closes the current position, opens a new position of equal size in the opposite direction, and attempts to attach a reverse stop loss. The window shows current position, reversed position, reverse stop-loss price, available balance, required margin, risk budget, and current reverse risk. If minimum notional value, balance, or risk checks fail, the confirm button remains disabled until position or risk parameters are adjusted.

• Used to set, modify, and cancel position stop loss and position take profit.
• Position stop loss and position take profit are trigger execution orders for the current position. When triggered, they execute with position-protection semantics and close the whole position; they are not normal entry orders.
• The most important rule is trigger direction:
• For a long position:
• Position stop loss should be below current price.
• Position take profit should be above current price.
• For a short position:
• Position stop loss should be above current price.
• Position take profit should be below current price.
• If the price direction is wrong, the most common result is immediate trigger or an order that does not fit the position-protection semantics.
• The current UI uses a two-column information area and grouped buttons, making it easier to inspect current protection state and set take profit or stop loss separately.

Example:

Stop-loss setting example:

Take-profit setting example:

• Used to input and submit standard take-profit/stop-loss parameters.
• Standard take-profit is a limit reduce order, while standard stop-loss is a conditional reduce order. Neither is a normal entry order.
• The key difference from position protection is the execution result:
• Position protection focuses on protecting the whole current position and executes a full close when triggered.
• Standard TP/SL is more suitable for partial position handling and reduces by the quantity you enter.
• Because it reduces by quantity, always re-check side, price / trigger price, and reduce quantity before use.
• In English UI, labels are longer, so check that fields are not truncated.

Example:

• Used to view and handle current unfinished orders.
• Common fields include symbol, order ID, side, type, trigger price, order price, quantity, filled quantity, reduce-only, close position, trigger type, and status.

Example:

• Records fill-level information such as time, symbol, side, type, quantity, and price.

• Records order lifecycle changes such as submission, fill, cancellation, and other status transitions.

• Records position-level events such as opening, closing, sync records, and notes.
• The realized PnL note must remain visible because it is important for review.
• Spot has no long/short position or position history in the Futures sense. View Spot asset quantity, available balance, and frozen balance in the trading panel; fills and orders remain available in the first two tables.

Order watch is mainly used when a limit entry enables stop loss / take profit but the exchange cannot safely bind that protection server-side before the main order fills.

Flow:

1. Enable stop loss or take profit in the limit entry window.
2. If the current exchange requires CubeTrade handling, the window shows that protection will be added after the main order fills.
3. After submitting the main order, the task appears in the Order Watch table.
4. CubeTrade periodically checks the main order status.
5. After the main order fully fills, CubeTrade uses exchange-native interfaces to add protective stop loss and / or reduce-only limit take profit.
6. While a partially filled main order remains active, CubeTrade updates its status and keeps waiting. A full fill is protected using the complete filled quantity. If a partially filled main order is canceled, expires, or otherwise terminates, CubeTrade places TP/SL for the actual filled quantity; the watch task ends directly only when the terminal order has zero fill.

Notes:

• Order watch depends on a running CubeTrade process. It is not an exchange-side pre-bound stop.
• Minimizing or closing the primary window hides it in the system tray. Switching symbols, timeframes, or layouts also does not cancel order watch.
• If the main order is temporarily unavailable or the exchange briefly returns an empty status, CubeTrade keeps the watch task and retries instead of ending it automatically.
• Only a main order that is still waiting with zero filled quantity can use Cancel Main Order and Stop Watch in details. The local task ends only after the exchange reports a successful cancellation.
• Partially filled, filled, protection-submitting, or manual-review tasks are never withdrawn by the exit flow. Keep order watch running or handle the position and protective orders manually first.
• If adding protection explicitly fails, Order Watch Details shows the reason. If the submission result cannot be confirmed safely, CubeTrade stops automatic retries to avoid duplicate protection orders and asks you to verify exchange orders manually. Both states require manual handling.
• Click an item in the order watch table to view exchange, account, main order ID, stop-loss order ID, take-profit order ID, quantity, order price, stop-loss price, take-profit price, and notes.

Add price alerts from the chart:

1. Select Price Alert from the left chart toolbar.
2. Click the target price level; an alert line appears on the chart.
3. The alert appears in Tracking -> Price Alerts on the right.
4. When triggered, CubeTrade plays the sound in the background, the UI removes the chart alert line, and the item is removed from the active alert list.

Price alert rules:

• Alerts are bound to exchange + account + symbol.
• Alerts are independent of timeframe. Switching between 5m, 15m, or 1h does not change the alert.
• Creating an alert records its arming time and the current price. Only realtime data observed after arming can trigger it; older candles loaded later cannot trigger it retroactively.
• For a new candle that starts after arming, either the candle body or wick reaching the trigger price is valid, even when the close does not cross the trigger price.
• The background tracking service subscribes realtime prices for active alerts, so you do not need to keep the corresponding chart or symbol open.
• Click an item in the right-side table to view details.
• Details allow you to modify trigger direction and trigger price, or cancel the alert. Changing the direction or trigger price re-arms the alert using the price and time of that edit.
• Modify and cancel actions from the right-side details sync back to the chart without refreshing the whole chart page.
• Alert sound and volume are configured in System Settings -> Alerts; custom sounds currently support only .wav/.wave files.

One primary CubeTrade window process owns the single system tray entry and the background tracking owner. Additional windows do not create duplicate tray entries or execute the same task twice.

• Minimizing or clicking the primary window close button only hides it to the system tray. Price alerts, order watch, market subscriptions, and background workers keep running.
• The tray menu can reopen CubeTrade, show order-watch and price-alert counts, and start a true exit through Exit CubeTrade.
• On macOS, clicking the CubeTrade Dock icon also restores a hidden main window.
• While the window is hidden, price alerts and order fills use system tray notifications. A foreground window keeps the existing in-app notification without duplication.
• On true exit with active local tracking, CubeTrade lists the exchange, account, symbol, and task summary and offers Keep Running in Background, Keep Watch Records and Exit, and Return to Tracking.
• If records are kept, they remain local, but no watch runs between exit and the next launch. Exchange orders may fill during that gap without CubeTrade adding protection.
• To stop rather than retain watch, return to Tracking -> Order Watch and cancel each still-unfilled exchange main order. Local watch stops only after the exchange reports cancellation success; never delete only the local record.
• Partially filled, filled, or protection-submitting tasks cannot be canceled by the exit flow. Keep the background runtime alive or manually confirm that positions and protection are safe first.
• If a Linux desktop does not expose an available system tray, CubeTrade preserves normal window-close behavior. Resolve every task that depends on the local runtime before exiting.

• First check whether the network route matches mainnet, demo, or testnet.
• Check whether you copied the API key or secret from the wrong account.
• Check whether API permissions cover the actions you want to perform, such as read, trade, and futures permissions.

• Market-data route and trading route are separate. Being able to view charts does not mean trading credentials work.
• Return to exchange settings and run trading connection test plus trading credential test.

• Public market data only confirms that the symbol exists. Private orders must also pass region, KYC, product agreement, futures-account, API-permission, and IP-allowlist checks.
• For Binance -4411, open the target contract under Futures -> USDⓈ-M Futures -> TradFi, complete the required agreement or activation, then retry in CubeTrade.
• For Binance -2015, verify the account and network, enable Enable Reading + Enable Futures, and check Trusted IPs against the current trading outbound IP.
• Bybit 110123 / 110125 requires the master account to accept the contract terms; 110132 means the product is unavailable in the region; 10005 / 10010 indicate contract permission or IP allowlist problems.
• For OKX 59113, complete KYC Level 2. For permission failures, enable Read + Trade and use the API domain matching the account region.
• For Bitget 40000 / 40040 / 40301 / 40916, or Gate USER_NOT_FOUND / READ_ONLY / IP_FORBIDDEN, follow the exchange-specific prerequisites in Section 4.4.
• HTX API futures orders require at least KYC Level 2, an active futures account, and readOnly + trade permissions.
• CubeTrade does not accept agreements, activate products, complete KYC, or change API permissions. It never needs withdrawal or fund-transfer permission.

• This is normal semantics: market orders usually have no cancelable waiting state.
• Cancel limit orders or conditional orders, not already-filled market orders.

• First check whether a very large historical range is still loading.
• Reduce the number of active layers and indicators, then test again.
• Wait for historical loading to finish before dragging quickly and repeatedly.

• If the current exchange or current take-profit percentage uses CubeTrade-managed protection, no take-profit / stop-loss order is created before the main order fully fills.
• After the main order fully fills, CubeTrade adds stop loss and / or the first take profit.
• Check Tracking -> Order Watch to see whether the task is still waiting for the main order to fill or has already submitted the protection order.

• This is normal behavior: after an alert triggers, the alert line is removed and the active alert list removes the item.
• Add a new price alert if you need another reminder.

• First confirm the matching Positions or Orders item under System Settings -> Chart -> Trading Markers is enabled.
• Markers appear only for data matching the current chart exchange and symbol. After switching exchange, account, or symbol, wait for the right-side trading panel to finish the next position/open-order query.
• If the right-side trading panel itself has no matching position or open order, the chart will not create extra markers.
• If you temporarily want a cleaner chart, turn off the matching Positions or Orders marker; this does not cancel real open orders and does not change position state.

• During normal realtime market data, the candle countdown is calibrated from exchange WS event time and does not depend on the local system clock.
• If the current platform does not provide realtime event time, or the chart is still showing historical cache/offline data, the countdown falls back to a local-time estimate.
• If the countdown remains visibly different from the exchange, first confirm the market data connection is live, then check whether the local system clock is severely off.

• In a multi-chart layout, the pane with the thin highlighted border is the current target. Top-bar timeframe buttons change only that pane.
• Click the target pane before choosing a timeframe. Configure each pane separately when you want several timeframes on screen.

• Check Chart Settings -> Chart Layout -> Sync Indicator Settings. When it is off, indicator enablement, visibility, parameters, and styles change only for the selected pane.
• When it is on, subsequent indicator changes apply to all visible panes. Existing independent pane settings are not overwritten while synchronization is off.

• REST fallback means WebSocket data is currently unavailable and CubeTrade has fallen back to REST. The chart can still update, but it is usually less timely than WS live.
• Market data connection interrupted means the realtime market-data path is unavailable. Check the network and exchange status, then reload the current symbol. The right-side trading API and left-side market-data API are separate, so a market-data fault does not necessarily mean the trading credentials are invalid.

• CubeTrade does not write your trading credentials in plain text to local config files. In the current version, saved keys, secrets, passphrases, and related credential data are encrypted before storage.
• Venue config files are stored under the platforms subdirectory, such as binance.json, okx.json, and similar files. Credential fields inside these JSON files are encrypted.
• CubeTrade is a local desktop app. It does not provide an online service for collecting, syncing, or hosting user trading credentials.
• Your trading credentials are used mainly for local trading authentication, such as testing credentials, querying accounts/positions, placing orders, canceling orders, and setting protection orders.
• When you explicitly perform those actions, the relevant credentials participate in signing or identity checks according to the target exchange API and are used directly when communicating with the selected exchange.
• For safety, use this software only on trusted devices and avoid casually sharing the config directory, log directory, or whole-machine backups.

• Order watch and price alert records are stored under the trade_tracking subdirectory in the app data directory.
• These records are used to recover unfinished tracking tasks locally. They are not uploaded to an online managed service.
• If you manually delete this directory, historical watch tasks and price alerts in the Tracking panel are lost.

• Logs are mainly used to troubleshoot connection, request, UI state, and runtime errors.
• If you plan to send logs to someone for help, review and redact sensitive information such as account names, proxy addresses, and order IDs first.
• Trading credentials should not be shared as troubleshooting material.