Connectivity Guide Data feeds & trade execution

When enabled, after every losing trade the next trade size is increased to recover the loss faster. The base size is captured when you turn AUTO ON. This is high risk — a streak of losses compounds fast. Always pair with a daily loss limit.

Display shows current loss streak. Resets to base size after a winning trade. Configurable in the AUTO TRADE section of the EXECUTE panel.

Inverts every signal: SCALP/Oracle says BUY → bridge sends SELL, and vice versa. Useful when you suspect the signals are systematically wrong on a particular symbol or session, or for fading retail flow.

Toggle independently from SMART. Both can be on at once. The badge shows in the EXECUTE panel.

Auto-trader only fires when the signal's confidence score (computed by the SCALP or Oracle engines) exceeds your minimum. Default 65%. Range 50–95%.

Higher = fewer but stronger signals. Lower = more trades, more noise. Tune per instrument: BTC perps tolerate 60%, illiquid micros need 75%+.

Cooldown: minimum milliseconds between two auto-trades (default 15,000). Max positions: hard cap on simultaneous open trades. TP/SL ticks: take-profit and stop-loss distances in tick units — automatically scaled per symbol's native tick size.

Each open auto-position is tagged with the signal that triggered it, so you can audit which signals are profitable in your stats.

When the day's running PnL crosses your configured loss or profit cap, AUTO TRADE is force-disabled and a red LIMIT HIT badge appears next to the panel. You must manually re-enable next session.

This is the most important risk feature. Always set both — it protects you from blow-up days and locks in green days.

Tick which signal types the auto-trader is allowed to act on:

• Absorption — hidden buying / selling into walls
• Iceberg — replenishing limit orders
• Exhaustion — failed continuation
• Delta spike — sudden directional aggression
• Spoof — fake walls (often inverted)
• Smart money — large player accumulation/distribution
• Oracle prediction — AI agent consensus (off by default)

Cause: the file is opened directly with file:// (double-click on the HTML), so browsers block cross-origin fetches. NEXUS auto-falls-back to a CORS proxy chain (corsproxy.io, allorigins.win, cors-anywhere) — but proxies sometimes go down.

Fix: serve the file from a tiny local HTTP server. From the folder containing the HTML, run: python -m http.server 8000, then open http://localhost:8000/3D_NEXUS_META.html. WebSockets work fine in both modes; only REST needs the proxy.

Cause: server-time drift. Binance and similar exchanges reject requests whose timestamp is more than ±1 second off the server clock. NEXUS performs an automatic server-time sync on connect, but if your OS clock is badly wrong it can still fail.

Fix: sync your computer clock. Windows: Settings → Time & Language → Sync now. Mac: System Settings → Date & Time → set automatically. Re-save your keys after syncing.

Cause: API key was created without the right trading scope. Most common: you enabled Spot but try to trade Perps, or vice versa.

Fix: regenerate the key with the correct scopes ticked. For Bitget & OKX make sure passphrase is also pasted — these exchanges silently fail if it's missing.

Cause: NEXUS can't reach ws://localhost:55XX. Either the bridge isn't actually listening, or a firewall is blocking the local socket.

Fix: open the bridge GUI's log panel — you should see WebSocket server listening on 0.0.0.0:5555 (or the relevant port). If yes, allow python.exe through your firewall. If no, the bridge failed to bind — check whether another process owns that port (run netstat -ano | findstr 5555 on Windows).

Cause: you launched the Hyperliquid bridge without supplying a key. Market data works without it, but you cannot send orders.

Fix: launch with python hyperliquid_nexus_bridge.py --key 0xABC… or --key-file key.txt, OR paste the key in the GUI prompt. Use a dedicated trading wallet with limited funds — never your main wallet.

Cause: WebSocket disconnect, often due to laptop sleep, ISP hiccup, or upstream rate-limit. NEXUS has built-in auto-reconnect with exponential backoff, but the feed shows STALE while it reconnects.

Fix: usually self-heals within 5–10 seconds. If it persists, click the refresh icon next to the symbol or briefly switch to another symbol and back. For laptops, consider keeping the lid open and disabling sleep during long sessions.

Cause: SC requires explicit depth subscription per symbol. By default it streams last-trade only.

Fix: in Sierra Chart, go to Trade → Trade Service Settings and confirm DTC is enabled. Then in File → Symbols → Intraday File Update List, append |MDD after each symbol you want to stream depth for (e.g. ESM26-CME|MDD). Restart the bridge after changes.

Cause: when you signed up to Polymarket via Magic Link / email, your trading wallet is a proxy wallet contract distinct from your EOA. The bridge needs both: your private key (signs) AND the proxy address (where funds live).

Fix: in the bridge GUI, paste both. The Smart Wallet path is 0xYourProxy… — find it in your Polymarket profile under Settings → Funder address.

Cause: hot-reloads or page refreshes reset the running PnL counter. The hard limit only persists within a session.

Fix: after a limit hit, leave the page closed for the rest of the session. Or paste the limits into the AUTO TRADE config before opening positions so they survive a refresh.