A grid bot control center built for traders who want volume, automation, and risk visibility without babysitting every order. Futures is the default mode; spot grids are supported on major centralized exchanges.

Questions, deployment notes, exchange-specific fixes, and live trading lessons are easier when users are in one place. Community link: https://t.me/nexustradebot8.

English | 简体中文 | Русский | 한국어 | 日本語 | Español | Tiếng Việt | हिन्दी | Português | العربية | 繁體中文

If you are a trader, start with the one-command install, open the web console, add an API key with trading permission only, and create a small test bot before using real size.

If you are a developer, the useful path is: build from source, inspect config.example.yaml, run go test ./..., then use worker mode when you want to launch a bot from a specific config file.

The README is organized from practical use to technical detail: install, supported exchanges, what the bot does, strategy examples, parameters, manual installation, and live-trading checks.

Run this on a fresh Ubuntu server:

wget -O nexus-trade-bot.sh https://raw.githubusercontent.com/haohaoi34/nexus-trade-bot/main/scripts/nexus-trade-bot.sh && chmod +x nexus-trade-bot.sh && ./nexus-trade-bot.sh install && ./nexus-trade-bot.sh start

The server runner automatically:

• Installs missing Ubuntu dependencies.
• Installs Go if the server does not have a compatible version.
• Clones https://github.com/haohaoi34/nexus-trade-bot.git when it is not already running inside a source checkout.
• Builds the bot from source, or uses the bundled binary in a release package.
• Creates config.yaml from config.example.yaml if needed and keeps it local.
• Starts the web console in the background and writes logs to logs/.
• Prints a clear access block with the local URL, bind address, PID file, and log paths. Remote access stays off unless you explicitly bind a public address.

Useful server commands:

./nexus-trade-bot.sh install
./nexus-trade-bot.sh start
./nexus-trade-bot.sh status
./nexus-trade-bot.sh logs
./nexus-trade-bot.sh restart
./nexus-trade-bot.sh stop
./nexus-trade-bot.sh update

Default web login:

username: admin
password: admin

Change the default password immediately after your first login. The bundled server runner binds the web console to 127.0.0.1:8080 by default. For remote access, prefer SSH tunneling or a reverse proxy with firewall rules; only use NEXUS_TRADE_BOT_ADDR=0.0.0.0:8080 when you intentionally want a public bind.

• Binance ☑️
• Bitget ☑️
• Gate.io ☑️
• Bybit ☑️
• OKX ☑️
• Hyperliquid ☑️

nexus-trade-bot helps you run grid strategies from a clean web console:

• Add exchange APIs once and verify them before use.
• Create multiple bots for different symbols, accounts, and directions.
• Choose futures or spot. Futures is selected by default.
• Use long, short, or neutral mode on futures; use long mode on spot.
• Load Binance, Bitget, Bybit, OKX, Gate, and Hyperliquid spot symbols automatically.
• Watch balances, trading volume, bot status, and PnL in real time.
• Pause a bot, change parameters, and restart it with the latest settings.
• Let the risk monitor stop trading during abnormal market moves.

It is designed for traders who care about execution, turnover, and control, not for people who want to keep editing config files all day.

A grid bot places buy and sell orders at fixed price intervals. Instead of trying to predict the exact top or bottom, it keeps working around a price range:

• When price drops, the bot gradually buys according to your grid settings.
• When price rebounds, the bot sells higher levels step by step.
• In a sideways or upward-recovering market, this can turn volatility into repeated realized trades.
• In a one-way downtrend, the bot accumulates position and needs enough margin, risk limits, and patience.

The goal is not magic profit. The goal is disciplined execution: consistent order spacing, controlled order size, visible risk, and automatic reaction when the market becomes abnormal.

Here is a practical example to understand how traders use this type of bot.

Assume ETH is trading near 3000, and you configure:

With a tight 1 USDT interval and active ETH liquidity, the bot may generate very high turnover. In a busy market, this kind of configuration can reach millions of dollars in daily trading volume, and tens of millions in monthly volume, depending on volatility, fees, liquidity, and account size.

This is why many traders use grid systems for two purposes:

• Volume building: increasing futures trading volume for exchange VIP tiers or campaigns.
• Volatility harvesting: repeatedly buying lower and selling higher inside a range.

Grid trading must be planned around drawdown.

Suppose ETH starts near 3000 and falls to 2700. A long grid will usually hold a floating loss because it has bought along the way down. But it has also accumulated lower entries. If price later rebounds from 2700 toward 2850, the average cost may be pulled down enough that the account approaches breakeven earlier than a single entry at 3000.

If ETH returns close to the original 3000 area, the strategy may benefit from both:

• inventory recovery from the rebound;
• realized grid spreads collected during the movement.

Some traders reserve a larger margin buffer, for example around 30,000 USDT, to design a grid that can tolerate a much deeper move such as a 1000 USDT ETH drawdown. Whether that is enough depends on leverage, margin mode, position size, fees, exchange maintenance margin rules, and how aggressive your grid is.

The important point: grid profit comes from preparation, not optimism. Before running size, calculate how far the market can move against you, how much position the bot can accumulate, and what happens if the market does not rebound quickly.

Fast one-way drops are the worst environment for an aggressive long grid. nexus-trade-bot includes a market risk monitor designed to reduce this problem:

• watches major symbols such as BTC, ETH, SOL, XRP, and DOGE;
• detects abnormal price and volume behavior;
• pauses trading when market conditions become dangerous;
• allows trading again only after enough monitored symbols recover.

This does not remove risk, but it gives the bot a chance to stop adding exposure during sudden liquidation-style moves.

Use tight intervals and controlled order size on deep-liquidity symbols. The goal is high turnover with predictable execution. Fee rates matter a lot here, so use low-fee pairs or maker-fee discounts where possible.

Start after a meaningful drop instead of chasing a vertical pump. The bot buys in layers and sells into rebounds. This style needs enough margin to survive deeper pullbacks.

Use spot mode when you want the bot to buy and sell actual coins instead of opening leveraged futures positions. Spot mode is long-only: the bot buys lower levels first and sells inventory into rebounds. It is simpler than futures, but it still needs enough quote balance and a plan for prolonged downtrends.

If you already hold a position, the bot can help sell it out gradually as price rises. When the position is fully reduced, you can stop the bot.

Use neutral mode when you want both long-side and short-side grid behavior. Start with smaller size and watch how the exchange handles position mode before scaling.

Classic grid is a futures-only neutral mode. It keeps 50 live buy orders below the current grid price and 50 live sell orders above it, with no upper or lower range. Filled grids are replenished automatically so the book stays close to 100 active orders. Hyperliquid futures currently does not support this mode because it does not expose the required neutral hedge behavior.

The console supports 11 languages:

English, Simplified Chinese, Russian, Korean, Japanese, Spanish, Vietnamese, Hindi, Portuguese, Arabic, and Traditional Chinese.

Web Console mode shows:

• API management
• bot creation and editing
• exchange logos
• real-time balances
• today and total realized PnL
• today and total trading volume
• running, paused, and stopped bot states

git clone https://github.com/haohaoi34/nexus-trade-bot.git
cd nexus-trade-bot
go mod download
go build -o nexus-trade-bot .

Start Web Console:

./nexus-trade-bot

Default local URL:

http://127.0.0.1:8080

Expose on a server:

NEXUS_TRADE_BOT_ADDR=0.0.0.0:8080 ./nexus-trade-bot

Only expose the console intentionally. Keep the port behind a firewall, VPN, SSH tunnel, or reverse proxy with authentication.

One-command server runner from a source checkout:

chmod +x scripts/nexus-trade-bot.sh
scripts/nexus-trade-bot.sh install
scripts/nexus-trade-bot.sh start
scripts/nexus-trade-bot.sh status
scripts/nexus-trade-bot.sh logs
scripts/nexus-trade-bot.sh stop

The runner works from both a source checkout and a release package. In source mode it builds ./nexus-trade-bot; in release mode it uses the bundled binary directly.

Run CLI worker mode:

./nexus-trade-bot worker config.yaml

Check these first:

• API key has trading permission but no withdrawal permission.
• Margin mode is what you expect.
• Leverage is not too aggressive.
• The symbol has enough liquidity.
• Order size meets exchange minimums.
• You understand how much position the grid can accumulate.
• You have a plan for one-way markets.
• Your server firewall exposes the web port only when intended.

Futures trading can cause significant losses. Grid strategies can perform well in range-bound or recovering markets, but they can also accumulate large positions during strong one-way trends. nexus-trade-bot is execution software; you are responsible for strategy settings, exchange configuration, account risk, and every trade placed through your API keys.