Where Should I Start with NavaX?

Risk notice: This app provides market data, trading, blueprint backtesting, and automation features. It does not guarantee returns. Before live trading, validate any strategy with small size, paper trading, or backtesting. Do not enable withdrawal permission on API keys.

After opening NavaX Crypto, the top navigation shows several main areas:

• Trade: View market data, open charts, manage accounts, and review positions and orders.
• Market Quotes: Browse trading-pair quotes.
• Blueprint: Create, import, edit, backtest, and debug strategy blueprints.
• Extensions: Browse and install extension blueprints, tools, or components.

For your first session, start from the Trade page and confirm that the quote list loads correctly.

If you only want to view market data, you do not need to add an account. If you want to place orders, view assets, or mount blueprints for trading, add an exchange API account.

Steps:

1. Open Resource Management on the left side of the Trade page.
2. Find the Account area and click add account.
3. Select an exchange, such as Binance, OKX, Bybit, Bitget, or HTX.
4. Enter an account remark, API Key, and API Secret.
5. If the exchange requires a Passphrase, such as some OKX or Bitget accounts, enter it as well.
6. Click Verify and wait for the app to confirm the API is usable.
7. After verification succeeds, save the account.

Recommended API permissions:

• Enable read permission to sync assets, positions, and orders.
• Enable trading permission only if you need manual trading or live blueprint trading.
• Do not enable withdrawal permission.
• If the exchange supports an IP whitelist, bind it to your current public IP.

The quote list shows prices, percentage change, volume, and other market information. You can search by trading pair, switch between spot and futures, or change the exchange data source.

Common actions:

• Double-click a trading pair in the quote list to open its chart.
• Switch the chart timeframe from the top of the chart, such as 1m, 5m, 15m, or 1h.
• View candles, current price, mounted blueprint markers, and trade lines on the chart.
• If the chart has no data, check the network, data source, and whether the trading pair supports the current market type.

After adding and logging in to a trading account, you can trade manually from the chart or trading panel.

Before placing an order, confirm:

• The current logged-in account is correct.
• The trading pair belongs to the market you intend to trade, such as spot or USDT futures.
• Futures leverage matches your risk tolerance.
• Order quantity, direction, take-profit price, and stop-loss price are correct.

After trading, review the bottom lists:

• Current Positions
• Current Orders
• Order History
• Position History
• Trade History

If account data is not refreshed in time, refresh manually or log in to the account again.

Blueprint is the visual strategy system in NavaX Crypto. You can think of it as a strategy flowchart: market nodes read data, indicator nodes calculate values, logic nodes make decisions, risk nodes limit exposure, and order nodes generate trading actions.

On the Blueprint page, the left panel contains My Blueprints, the center area is the blueprint canvas, and the right panel shows properties and parameters.

Common actions:

• Double-click a blueprint name on the left to open it.
• Click a node to view or edit its parameters.
• Connect market, indicator, logic, and order nodes with lines.
• Save changes to the local workspace after editing.
• To import a .fsvb file, use the import function in the blueprint list.

If you only use an existing blueprint, you usually do not need to edit the node structure. Check the parameters, backtest result, and mount settings instead.

Backtesting is recommended before live trading. It helps you understand historical trade count, profit and loss, win rate, drawdown, and order behavior.

Basic workflow:

1. Open the Blueprint page.
2. Open a blueprint.
3. In the backtest settings, choose the trading pair, timeframe, date range, initial capital, leverage, and related parameters.
4. Start the backtest.
5. Review logs, order records, chart markers, and statistics.

Backtest notes:

• Results depend on historical data quality.
• Market orders, limit orders, slippage, and fees all affect results.
• A short test window may not represent long-term behavior.
• A profitable backtest does not guarantee live profit.
• If compilation fails, first check whether node connections and parameters are complete.

Mounting a blueprint binds a strategy to a specific account and trading pair, allowing it to run with market data like an EA.

Use Paper mode first to confirm the blueprint behaves as expected before considering live trading.

Mounting workflow:

1. Open the target trading-pair chart on the Trade page.
2. Find the blueprint in Resource Management on the left.
3. Double-click the blueprint, or drag it onto the chart.
4. In the mount window, confirm the trading pair, leverage, runtime mode, and order direction.
5. Check the exposed blueprint parameters on the parameters page.
6. Set risk limits, such as max order value and max daily orders, on the risk page.
7. Enable auto trading and save.

Runtime modes:

• Paper: Simulates strategy triggers and order results without sending real orders to the exchange.
• Live: Sends real orders through the current logged-in exchange account when the strategy triggers.

Before live mounting, verify the account, trading pair, leverage, position size, and risk limits.

Mounted blueprints appear under the account node in Resource Management and as a mount indicator on the chart.

You can:

• Double-click a mounted instance to reopen its settings.
• Save updated parameters or risk settings.
• Reload the blueprint so the runtime instance uses the latest blueprint file.
• Disable auto trading to stop future live orders.
• Review mount logs to inspect recent triggers, risk rejections, or order failures.

If you change the blueprint structure, stop the mount first, save the blueprint, and then mount it again.

The Extensions page lets you browse installable blueprints and tools. Extension details usually include version, description, author, backtest information, or recommended trading pairs.

After installation, extension blueprints appear in the blueprint list or Resource Management. Before using an extension blueprint, backtest it first, then run it in Paper mode, and only then consider Live mode.

Check your network connection, exchange data source, and whether the trading pair supports the current market type. You can also switch data sources and retry.

Check whether API Key, Secret, and Passphrase are correct. Confirm that exchange API permissions are enabled. If an IP whitelist is used, make sure your current public IP is included.

Confirm that you are logged in to a trading account, the API has trading permission, the trading pair supports the current market type, futures leverage does not exceed the exchange limit, and the account has sufficient balance or margin.

Open and save the blueprint first, then confirm that no required node connections are missing. Also check the backtest trading pair, timeframe, date range, and network data availability.

A blueprint triggers only when its event timeframe and signal conditions are met. Confirm the chart timeframe, blueprint execution timeframe, trading pair, account, and runtime mode, then inspect mount logs to see whether risk controls rejected the signal.

For first-time use, follow this order:

1. View quotes and get familiar with trading pairs and charts.
2. Add an account with read-only permission first, and confirm assets and orders sync correctly.
3. Test manual opening and closing with very small size.
4. Import or create a blueprint and run historical backtests.
5. Mount the blueprint in Paper mode and observe triggers and order records.
6. After the strategy is stable, consider small-size live trading.
7. Regularly check mount logs, account risk, and exchange API status.

This separates “can I use the software,” “is the account connected,” “does the strategy make sense,” and “is live risk controlled,” reducing the uncertainty of going live too early.