TradingView carries Hyperliquid's own market data natively (HYPERLIQUID: symbols,
since 2026-07-02) — you chart the exact venue we execute on. Your strategy runs on TradingView's
servers (not your machine); we are the execution layer. Proven end-to-end on a live alert 2026-07-06.
{"api_key": "vf_your_key", "position": "{{strategy.market_position}}", "ticker": "{{ticker}}", "risk_pct": 1.0, "sl_pct": 2.0, "client_id": "{{timenow}}"}
position = TradingView's after-order state (flat/long/short), maps 1:1 to what we execute ·
risk_pct = % of equity you LOSE if the stop hits (size is derived) · sl_pct = stop distance
from the mark at receipt (send an exact "sl" price instead if you have one) · optional "tp".
HYPERLIQUID:SOLUSDC.P (or BTC/ETH). Any timeframe — we never see your candles.strategy.entry/exit so {{strategy.market_position}} resolves) → Add to chart.https://vaultomate.xyz/v1/signal/tvGET /v1/vault/<your-vault>/log or the terminal —
you'll see the would-be order (size, stop, builder code) or the exact rejection. When it looks right, flip live from the terminal.{{ }}; the alert
still fires. Use the placeholder-alone message above to avoid it.