Prime Spot Grid Trading Bot - FAQ

Mainnet (Live Trading)

1. Log into Binance → Dashboard → API Management.
2. Create a new API key (e.g., PrimeGridBot).
3. Set Permissions:
   • Enable Spot Trading
   • Disable withdrawals
   • (Optional) Enable Read Only
4. Copy and securely save your API Key and Secret Key.

Testnet (Sandbox Trading)

1. Go to Binance Testnet.
2. Register or log in and create a Testnet API Key.
3. Use endpoint https://testnet.binance.vision/api.
4. Paste keys into PrimeTradingBot config.

⚠️ Note: Make sure you use the correct environment (Mainnet vs Testnet).

If you prefer a GUI over command-line tools (scp, sftp), you can connect to your EC2 instance using FileZilla with your PEM key file.

Steps to connect with FileZilla (EC2 + Key File)

1. Install FileZilla Client.
2. Open FileZilla → File → Site Manager → New Site.
3. Set:
   • Protocol: SFTP – SSH File Transfer Protocol
   • Host: your EC2 IPv4 (e.g., 18.222.33.44)
   • Port: 22
   • Logon Type: Key file
   • User: ubuntu (or your AMI default user)
   • Key file: your .pem file from EC2 setup

Refer to:

• EC2 Installation Guide

Once connected, use the left panel for local files and the right panel for EC2 files. Drag & drop to upload or download.

💡 Tip: Ensure your EC2 instance is running. If FileZilla rejects your key, set the PEM file to read-only.

If you connected successfully in the GUI (via the Connect button) but the bot does not start when you press Start Bot – or the GUI shows no activity even though the server is running – this likely means the trading service is stuck or needs a refresh.

✅ To fix this, restart the bot service manually:

sudo systemctl restart primespotgrid

This will restart the background process and re-sync the GUI connection without affecting your active grid limit orders on the exchange.

There are two easy ways to find your server's public IP address:

Method 1 – Check the autoscript log

When you run the Auto Script via SSH, it usually outputs your connection details at the end. Look for a line showing your public IPv4 address, for example:

Server IP: 18.222.33.44

Method 2 – EC2 Console

1. Sign in to the AWS Management Console and open the EC2 Console.
2. In the left menu, choose Instances.
3. Select your instance; the Public IPv4 address appears in the details pane.

In rare cases, when a grid is stopped or liquidated, the bot may not be able to sell the asset completely due to the minimum order size limit on Binance (5 USDT). As a result, a very small remaining balance – commonly referred to as dust – may remain in your account.

If such dust remains, the bot cannot place a sell order for it because it is below Binance’s minimum trade limit.

🛠️ How to fix this:

• Step 1 (In the Bot): Select the pair and use the “Panic Sell” command in the client application. This will force the bot to release the stuck asset state internally and allow you to configure a fresh grid.
• Step 2 (On Binance) - Highly Recommended: Periodically log into your Binance account and use the "Convert Small Balance to BNB" feature. The bot cannot sell dust for you. Converting dust to BNB manually cleans up your wallet and gives you BNB to pay for future trading fees (which also grants you a 25% trading fee discount on Binance).

🎯 The v5 Solution: Pro Features & Auto Range

Unlike basic grid bots that simply stop working when the price leaves the range, Prime Spot Grid Bot provides advanced tools to maintain profitability while protecting your capital.

⚙️ Recommended Configurations by Market Phase:

• Sideways Market (Balanced): Use Arithmetic Mode with Bollinger Bands Auto Range. The bot will automatically calculate a safe upper and lower bound based on recent volatility. Keep Grid Count moderate (e.g., 20-40) to ensure profit per grid covers exchange fees.
• Bull Market (Aggressive): Use Geometric Mode and enable Sliding Grid (Infinity Grid). If the price pumps above your ceiling, the bot will shift the entire grid upwards automatically, meaning you never miss out on a massive rally.
• Bear Market (Defensive): Enable the DCA Safety Net. If the price drops below your Grid Floor, the bot will stop standard grid trading and deploy DCA Safety Orders to aggressively average down your entry price, allowing you to escape at a profit on the next bounce.

💡 Risk Management:

Always set an Equity Stop Loss (e.g., -15%). This ensures that if the market undergoes a catastrophic flash crash, your total portfolio exposure is capped, and the bot will liquidate to protect your remaining balance.

Unfortunately, if you have lost the .pem key file that was created when you launched your EC2 instance, you cannot recover it. AWS does not store or back up private keys for security reasons – the key file is only available once when the key pair is created.

🔒 1. Why the key file cannot be recovered

When you create a key pair in AWS, the private key (.pem) is generated once and immediately downloaded. AWS never keeps a copy of it. Without that file, SSH or SFTP (FileZilla) access to the current instance will no longer work – unless you had a backup.

🛠️ 2. How to regain access

You can create a new key pair and attach it to your instance using one of the methods below.

Option 1 – Create a new key pair and launch a replacement instance

1. Create a new key pair:
   Go to AWS Console → EC2 → Key Pairs → Create key pair.
   Name it and download the new .pem file securely.
2. Stop your current instance:
   EC2 → Instances → Select your instance → Stop instance.
   (Do not terminate it.)
3. Create a snapshot and AMI:
   From the instance’s root volume, create a snapshot.
   Then create a new AMI (Amazon Machine Image) from that snapshot.
4. Launch a new instance:
   Use that AMI to launch a new instance.
   When prompted, select your new key pair.
5. Connect using the new key:
   

   ssh -i new-key.pem ubuntu@<public-ip>

6. Optional: After confirming the new instance works, you may terminate the old one to avoid additional costs.

⚠️ Best Practice

Always back up your .pem key file securely – store it in an encrypted folder, password-protected cloud drive, or external device. Once lost, AWS cannot recreate or resend it.

🏗️ Architecture & Privacy

Prime Spot Grid Bot is self-hosted – it runs on your own server (e.g., AWS, local PC). You have full control over execution, and your API keys never leave your server. Exchange bots run entirely on the exchange’s infrastructure, giving them total visibility over your strategy.

⚙️ Advanced Pro Features (Sliding & Trailing)

Most exchange grid bots are "static". If the price pumps above your grid, they sell everything and sit idle. If the price dumps below, they become bag holders. Prime Spot Grid Bot features Sliding Grid (automatically shifting your grid up during bull runs) and Trailing Down / DCA Safety Net (adapting to market crashes to recover losses quickly).

🛡️ Equity Risk Management

Exchange bots often struggle to provide clear Stop Loss mechanisms because the bot holds a mix of Base Asset and Quote Asset. Prime Spot Grid utilizes Total Grid Equity tracking, allowing you to set a definitive Portfolio % Take Profit or Stop Loss, ensuring you know exactly when the bot will cash out.

💰 Cost & Independence

Prime uses a one-time license purchase – no recurring subscription or platform fees. Because it runs on your own server, you maintain complete independence and can run the bot 24/7 without being subject to hidden exchange-side strategy throttling.

📊 Live Paper Trading

Prime Spot Grid includes an integrated Live Paper Trading engine that lets you test your Grid Ranges in real-time against the live order book without risking a single dollar. Most exchanges do not offer realistic grid paper trading environments.