Extension Market User Guide

Risk notice: The Extension Market distributes strategies and tools. It does not guarantee returns. Before live trading, always backtest the extension, run it in simulation, and only then consider live trading with small size. Do not enable withdrawal permissions on exchange API keys.

After opening the app, go to Extensions from the top navigation.

The page has two main areas:

You can drag the divider between the left and right areas to resize the My Extensions panel.

The My Extensions panel is used to manage and inspect extensions related to your current environment.

Two types of items may appear here:

• Extensions already downloaded and installed on this machine.
• Extensions owned or added by the currently signed-in account in the cloud.

Important: the app determines whether an extension is "installed" mainly by checking whether the matching market blueprint file exists locally, not only by checking the cloud account list. Therefore, an extension may belong to you in the cloud, but if it has not been downloaded to the current computer, it may still be shown as not installed.

Common badges:

Common actions:

The market home page lists installable extensions. By default, extensions with higher download counts and ratings appear first.

You can narrow the list in these ways:

• Keyword search: enter a keyword such as extension name, author, summary, category, or market type, then click Search or press Enter.
• Category filter: view extensions by category, such as strategy, risk control, signal, or tool. The available categories come from the market backend.
• Market type filter: filter by supported market, such as Spot or Futures.

If no results appear, clear the keyword and switch both category and market type back to All.

Each card in the market list shows key information:

Blueprint extensions are usually intended for direct strategy workflows. For script or tool extensions, read the detail page for the specific usage.

Click an extension card to open its detail page. The detail page contains header information, documentation content, comments, and a right-side information panel.

Focus on these areas:

If the detail page shows "No extension details" or "No changelog", the publisher did not provide that content. Use extra caution and run sufficient backtests.

Installation steps:

1. Go to Extensions.
2. Search or filter for the target extension in the market list.
3. Click the extension card to open the detail page.
4. Read Details, Changelog, comments, and backtest information.
5. Click Install.
6. If the extension requires an access code, enter the code in the dialog and confirm.
7. Wait for the installation success message.
8. Go to Blueprint or Resource Management to view the newly installed market blueprint.

When installing a blueprint extension, the app downloads the package into the local market blueprint directory and refreshes the blueprint workspace. After installation, the extension keeps market source information, version information, package verification information, and download time so the app can identify installation state and future upgrades.

Installation may require the corresponding permission. If the current account does not have download permission, the app will show a permission prompt.

The Extension Market supports several download modes:

For code-protected extensions, an input dialog appears during installation. Installation will not continue if the access code is empty or incorrect. Check casing, extra spaces, and validity period.

Blueprint extensions support Backtest preview. This is useful for quickly deciding whether an extension is worth further evaluation before installation.

Backtest preview behavior:

• Only blueprint extensions support backtest preview.
• The preview fetches a remote blueprint from the market and does not write it directly into local blueprint files.
• The app checks whether the blueprint can compile before opening the backtest window.
• The backtest window starts automatically.
• The default symbol uses the blueprint's existing configuration first; if none exists, it uses BTCUSDT.

The default backtest range is based on the blueprint execution interval:

Preview results only represent one historical test. Before formal use, install the extension, then go to Blueprint and retest with your own symbol, interval, fees, slippage, capital, leverage, and a longer time range.

After a blueprint extension is installed, it is added to the local blueprint workspace. Recommended workflow:

1. Open Blueprint.
2. Find the installed market blueprint in the blueprint list or Resource Management.
3. Open the blueprint and check its node structure, parameters, execution interval, market type, and risk-control nodes.
4. Run historical backtests and review PnL, drawdown, win rate, trade count, and order logs.
5. On the Trade page, mount the blueprint to the target chart or account.
6. Run it in simulation mode first and observe signal triggers, order intents, and risk-control rejections.
7. After the behavior is stable, consider live trading with small size.

Before live trading, check:

• Whether the current account is correct.
• Whether the symbol and market type match, such as spot or futures.
• Whether leverage, margin mode, and position sizing are within your risk tolerance.
• Whether the strategy includes risk controls such as rate limits, maximum position size, stop loss, cooldown, and kill switch.
• Whether the API key only has necessary permissions and does not allow withdrawals.

When an installed extension shows the Update available badge, you can click Upgrade from the detail page or the My Extensions panel.

Before upgrading, do three things:

1. Read Changelog to understand what changed.
2. Stop any running blueprint mounts.
3. Record the current version's key parameters and backtest results for comparison.

Upgrade rules:

• Only blueprint extensions support version-upgrade detection in the current installed workflow.
• If the current version is already the latest version, the app shows that no upgrade is needed.
• If this blueprint extension has a running mount, the app refuses to upgrade until you stop the mount.
• If there are stopped mounts, the upgrade confirmation dialog shows their count; after confirmation, the app syncs the blueprint version snapshot in those mounts.
• Upgrading keeps the local blueprint ID and removes old version files for the same market extension.

After upgrading, do not immediately resume live trading. Backtest the new version first, then run it in simulation to confirm that behavior matches expectations.

Uninstalling removes the matching local market blueprint file and removes the extension from the current user's extension relationship.

Uninstall steps:

1. Find the target extension in My Extensions or on the detail page.
2. Click Uninstall.
3. Read the confirmation dialog.
4. Confirm and wait for the uninstall process to finish.

Uninstall rules:

• If the extension has a running mount, the app refuses to uninstall it. Stop the mount first.
• If the extension has stopped mounts, confirming uninstall will also remove those mounts.
• After uninstalling, the blueprint workspace is refreshed and the extension is no longer shown as locally installed.

If you only want to stop a strategy temporarily, stop the mount or turn off automated trading first. Uninstall only when you are sure you no longer need the extension.

Installed extensions can be rated from the detail page by clicking Rate.

Rating rules:

• You must select 1 to 5 stars.
• You must enter comment content.
• After successful submission, the comments section refreshes.
• If the comment API has a short delay, the app temporarily shows your new comment locally and later replaces the list with server data on refresh.

The comments section may show regular users, authors, and administrators. Author or administrator labels only identify the comment source and do not guarantee strategy returns.

Check your network and sign-in status, then click the refresh button next to My Extensions or re-enter Extensions. If the market API is temporarily unavailable, the list may be empty.

Clear the keyword and switch category and market type back to All. Search only matches fields available in the current market list, such as name, author, summary, category, download mode, and market type.

This usually means the current computer does not have the local installation file. Click Download and install. It becomes Installed only after installation succeeds.

Possible causes include unavailable download URL, network issues, incorrect access code, missing account download permission, invalid package format, or blueprint compile validation failure. Refresh the market and retry; for code-protected extensions, confirm that the access code is correct.

Switch to Blueprint and refresh Resource Management first. If it still does not appear, return to Extensions and refresh. Installation state depends on local market blueprint files; deleted files or an unwritable directory can affect display.

The remote preview blueprint may fail to load, the blueprint may fail to compile, the backtest window may not be ready, or current market data may be unavailable. Try Backtest preview again from the detail page, or install the extension and backtest manually from the blueprint page.

If there is no Update available badge, the current version is already the latest version, or the version number cannot be compared reliably. If a mount is running, stop it before upgrading.

If the extension has a running mount, the app blocks uninstall. Stop the matching mount from Trade or Resource Management, then return to the Extension Market and uninstall it.

Confirm that the current account has rating permission and check the network. You must select a star rating and enter comment content.

For your first time using the Extension Market, use this sequence:

1. Search or filter for a target extension in Extension Market.
2. Open details and read the documentation, changelog, comments, and backtest information.
3. Run Backtest preview for blueprint extensions.
4. Install the extension.
5. Go to Blueprint, retest it, and check parameters and risk controls.
6. Mount it in simulation mode.
7. Observe logs, orders, risk-control rejections, and account changes.
8. After multiple rounds of validation, consider small-size live trading.
9. Stop running mounts before upgrading, then backtest again after upgrading.
10. When you no longer need it, stop mounts first, then uninstall the extension.