[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-81719":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":15,"stars30d":13,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":16,"rankGlobal":10,"rankLanguage":10,"license":17,"archived":18,"fork":18,"defaultBranch":19,"hasWiki":20,"hasPages":18,"topics":21,"createdAt":10,"pushedAt":10,"updatedAt":42,"readmeContent":43,"aiSummary":44,"trendingCount":15,"starSnapshotCount":15,"syncStatus":45,"lastSyncTime":46,"discoverSource":47},81719,"nexus-trade-bot","haohaoi34\u002Fnexus-trade-bot","haohaoi34","Nexus Trade Bot is an open-source millisecond-level high-frequency crypto market-making and grid trading system for major exchanges, with web console, automated order management, WebSocket sync, risk controls and one-click server deployment. 开源毫秒级高频加密货币做市与网格交易系统，支持主流交易所、网页控制台、自动挂单、风控、自托管部署。","",null,"Go",39,1,38,0,41,"GNU General Public License v3.0",false,"main",true,[22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"algo-trading","binance","bitget","bot","bybit","crypto","futures","gateio","golang","grid","hft","hyperliquid","market-maker","okx","quant","risk-management","self-hosted","spot","trading","websocket","2026-06-12 04:01:35","# nexus-trade-bot\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"logo\u002Flogo.png\" alt=\"Nexus Trade Bot\" width=\"720\">\n\u003C\u002Fp>\n\n**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.**\n\n[![Go](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FGo-1.26%2B-00ADD8?logo=go&logoColor=white)](https:\u002F\u002Fgo.dev\u002F)\n[![License](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-GPL--3.0-green)](LICENSE)\n[![One Command](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Finstall-one%20command-blue)](#one-command-install)\n[![Languages](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flanguages-11-orange)](#languages)\n\n## Community\n\nQuestions, deployment notes, exchange-specific fixes, and live trading lessons are easier when users are in one place. Community link: [https:\u002F\u002Ft.me\u002Fnexustradebot8](https:\u002F\u002Ft.me\u002Fnexustradebot8).\n\n## Languages\n\nEnglish | [简体中文](docs\u002Freadme\u002FREADME.zh-CN.md) | [Русский](docs\u002Freadme\u002FREADME.ru.md) | [한국어](docs\u002Freadme\u002FREADME.ko.md) | [日本語](docs\u002Freadme\u002FREADME.ja.md) | [Español](docs\u002Freadme\u002FREADME.es.md) | [Tiếng Việt](docs\u002Freadme\u002FREADME.vi.md) | [हिन्दी](docs\u002Freadme\u002FREADME.hi.md) | [Português](docs\u002Freadme\u002FREADME.pt.md) | [العربية](docs\u002Freadme\u002FREADME.ar.md) | [繁體中文](docs\u002Freadme\u002FREADME.zh-TW.md)\n\n## Read This First\n\nIf 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.\n\nIf you are a developer, the useful path is: build from source, inspect `config.example.yaml`, run `go test .\u002F...`, then use worker mode when you want to launch a bot from a specific config file.\n\nThe 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.\n\n## One-Command Install\n\nRun this on a fresh Ubuntu server:\n\n```bash\nwget -O nexus-trade-bot.sh https:\u002F\u002Fraw.githubusercontent.com\u002Fhaohaoi34\u002Fnexus-trade-bot\u002Fmain\u002Fscripts\u002Fnexus-trade-bot.sh && chmod +x nexus-trade-bot.sh && .\u002Fnexus-trade-bot.sh install && .\u002Fnexus-trade-bot.sh start\n```\n\nThe server runner automatically:\n\n- Installs missing Ubuntu dependencies.\n- Installs Go if the server does not have a compatible version.\n- Clones `https:\u002F\u002Fgithub.com\u002Fhaohaoi34\u002Fnexus-trade-bot.git` when it is not already running inside a source checkout.\n- Builds the bot from source, or uses the bundled binary in a release package.\n- Creates `config.yaml` from `config.example.yaml` if needed and keeps it local.\n- Starts the web console in the background and writes logs to `logs\u002F`.\n- 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.\n\nUseful server commands:\n\n```bash\n.\u002Fnexus-trade-bot.sh install\n.\u002Fnexus-trade-bot.sh start\n.\u002Fnexus-trade-bot.sh status\n.\u002Fnexus-trade-bot.sh logs\n.\u002Fnexus-trade-bot.sh restart\n.\u002Fnexus-trade-bot.sh stop\n.\u002Fnexus-trade-bot.sh update\n```\n\nDefault web login:\n\n```text\nusername: admin\npassword: admin\n```\n\nChange 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.\n\n## Supported Exchanges\n\n- Binance ☑️\n- Bitget ☑️\n- Gate.io ☑️\n- Bybit ☑️\n- OKX ☑️\n- Hyperliquid ☑️\n\n\n## What It Does\n\nnexus-trade-bot helps you run grid strategies from a clean web console:\n\n- Add exchange APIs once and verify them before use.\n- Create multiple bots for different symbols, accounts, and directions.\n- Choose futures or spot. Futures is selected by default.\n- Use long, short, or neutral mode on futures; use long mode on spot.\n- Load Binance, Bitget, Bybit, OKX, Gate, and Hyperliquid spot symbols automatically.\n- Watch balances, trading volume, bot status, and PnL in real time.\n- Pause a bot, change parameters, and restart it with the latest settings.\n- Let the risk monitor stop trading during abnormal market moves.\n\nIt is designed for traders who care about execution, turnover, and control, not for people who want to keep editing config files all day.\n\n## The Core Idea\n\nA 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:\n\n- When price drops, the bot gradually buys according to your grid settings.\n- When price rebounds, the bot sells higher levels step by step.\n- In a sideways or upward-recovering market, this can turn volatility into repeated realized trades.\n- In a one-way downtrend, the bot accumulates position and needs enough margin, risk limits, and patience.\n\nThe 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.\n\n\n## Example Strategy: ETH Grid With High Turnover\n\nHere is a practical example to understand how traders use this type of bot.\n\nAssume ETH is trading near `3000`, and you configure:\n\n| Parameter | Example |\n| --- | --- |\n| Symbol | `ETHUSDT` or `ETHUSDC` |\n| Direction | Long grid |\n| Price interval | `1 USDT` |\n| Order amount | `300 USDT` per grid order |\n| Market style | Sideways or upward-recovering market |\n\nWith 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.\n\nThis is why many traders use grid systems for two purposes:\n\n- **Volume building**: increasing futures trading volume for exchange VIP tiers or campaigns.\n- **Volatility harvesting**: repeatedly buying lower and selling higher inside a range.\n\n\n## Example Drawdown Logic\n\nGrid trading must be planned around drawdown.\n\nSuppose 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`.\n\nIf ETH returns close to the original `3000` area, the strategy may benefit from both:\n\n- inventory recovery from the rebound;\n- realized grid spreads collected during the movement.\n\nSome 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.\n\nThe 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.\n\n\n## Built-In Risk Protection\n\nFast 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:\n\n- watches major symbols such as BTC, ETH, SOL, XRP, and DOGE;\n- detects abnormal price and volume behavior;\n- pauses trading when market conditions become dangerous;\n- allows trading again only after enough monitored symbols recover.\n\nThis does not remove risk, but it gives the bot a chance to stop adding exposure during sudden liquidation-style moves.\n\n\n## Common Ways To Use It\n\n### 1. Volume and VIP Tier Building\n\nUse 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.\n\n### 2. Long Grid After a Market Pullback\n\nStart 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.\n\n### 3. Binance Spot Grid\n\nUse 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.\n\n### 4. Inventory Exit\n\nIf 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.\n\n### 5. Neutral Grid\n\nUse 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.\n\n### 6. Classic Grid\n\nClassic 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.\n\n\n## Parameter Guide\n\n| Setting | What It Means | Practical Tip |\n| --- | --- | --- |\n| `symbol` | Trading pair | Start with liquid pairs such as BTC or ETH. |\n| `app.market_type` | `futures` or `spot` | Defaults to `futures`. Spot live trading supports Binance, Bitget, Bybit, OKX, Gate, and Hyperliquid through dedicated adapters. |\n| `mode` | `normal`, `aggressive`, or `classic` | Use `classic` for the fixed 50-buy\u002F50-sell grid. It forces futures + neutral mode and targets 100 live orders total. |\n| `direction` | `long`, `short`, or `neutral` | Long grids need margin for drawdowns. Existing exchange positions are restored as bot inventory at startup. |\n| `price_interval` | Distance between grid levels | Smaller interval means more trades and more fees. |\n| `order_quantity` | Amount used per order | Larger amount increases turnover and drawdown. Confirm whether the UI is showing quote value or base quantity for your exchange and market type. |\n| `min_order_value` | Minimum order notional | Must satisfy exchange minimums. |\n| `risk_control.enabled` | Market abnormality protection | Keep it enabled unless you know exactly why not. |\n\n\n## Web Console\n\nThe console supports 11 languages:\n\nEnglish, Simplified Chinese, Russian, Korean, Japanese, Spanish, Vietnamese, Hindi, Portuguese, Arabic, and Traditional Chinese.\n\nWeb Console mode shows:\n\n- API management\n- bot creation and editing\n- exchange logos\n- real-time balances\n- today and total realized PnL\n- today and total trading volume\n- running, paused, and stopped bot states\n\n\n## Manual Installation\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fhaohaoi34\u002Fnexus-trade-bot.git\ncd nexus-trade-bot\ngo mod download\ngo build -o nexus-trade-bot .\n```\n\nStart Web Console:\n\n```bash\n.\u002Fnexus-trade-bot\n```\n\nDefault local URL:\n\n```text\nhttp:\u002F\u002F127.0.0.1:8080\n```\n\nExpose on a server:\n\n```bash\nNEXUS_TRADE_BOT_ADDR=0.0.0.0:8080 .\u002Fnexus-trade-bot\n```\n\nOnly expose the console intentionally. Keep the port behind a firewall, VPN, SSH tunnel, or reverse proxy with authentication.\n\nOne-command server runner from a source checkout:\n\n```bash\nchmod +x scripts\u002Fnexus-trade-bot.sh\nscripts\u002Fnexus-trade-bot.sh install\nscripts\u002Fnexus-trade-bot.sh start\nscripts\u002Fnexus-trade-bot.sh status\nscripts\u002Fnexus-trade-bot.sh logs\nscripts\u002Fnexus-trade-bot.sh stop\n```\n\nThe runner works from both a source checkout and a release package. In source mode it builds `.\u002Fnexus-trade-bot`; in release mode it uses the bundled binary directly.\n\nRun CLI worker mode:\n\n```bash\n.\u002Fnexus-trade-bot worker config.yaml\n```\n\n\n## Before You Trade Live\n\nCheck these first:\n\n- API key has trading permission but no withdrawal permission.\n- Margin mode is what you expect.\n- Leverage is not too aggressive.\n- The symbol has enough liquidity.\n- Order size meets exchange minimums.\n- You understand how much position the grid can accumulate.\n- You have a plan for one-way markets.\n- Your server firewall exposes the web port only when intended.\n\n\n## Disclaimer\n\nFutures 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.\n","Nexus Trade Bot 是一个开源的毫秒级高频加密货币做市与网格交易系统，支持主流交易所。其核心功能包括网页控制台、自动挂单管理、WebSocket 实时同步、风险控制及一键服务器部署。采用 Go 语言编写，具备高性能和低延迟的特点。适用于希望实现自动化交易并需要对订单量、自动化程度以及风险有高度可见性的交易者。无论是期货还是现货网格交易，在主要的中心化交易所上都能得到良好支持。",2,"2026-06-11 04:06:06","CREATED_QUERY"]