Skip to main content
Use this guide to identify and fix the most common issues you may encounter while running unCoded.
Possible causes:
  • acceptTosAndStart is set to false in your configuration
  • API keys are missing, incorrect, or lack the required permissions
Solutions:
1

Enable acceptTosAndStart

In Telegram, send /start to open the control panel. Select Configurations, locate the acceptTosAndStart parameter, and set its value to true.
2

Verify your API keys

Confirm that your Binance API Key and Secret Key are correctly entered. Both must have Read Info and Spot & Margin Trading permissions enabled.
3

Check server requirements

Ensure your server meets the minimum specifications and has a static IP address assigned. An unstable or shared IP can prevent the bot from connecting to Binance.
Possible causes:
  • Trading pair is incorrectly configured
  • buyPercentage or sellPercentages are not aligned with current market conditions
  • Insufficient balance in your Binance account
Solutions:
1

Confirm your trading pair

Check that baseAsset and quoteAsset are set to the correct values — for example, PEPE and USDC for the PEPE/USDC pair.
2

Adjust buy and sell parameters

Review buyPercentage and sellPercentages and ensure they reflect realistic price movements for current market conditions. Values that are too tight or too wide can prevent orders from triggering.
3

Check your Binance balance

Verify you have sufficient USDC for trading and BNB to cover transaction fees in your Binance account.
Possible causes:
  • sellActivateDistancePercentage is set too high
  • sellCancelDistancePercentage is misconfigured
Solutions:
1

Lower the activation distance

Reduce sellActivateDistancePercentage so that sell orders are placed closer to the buy price. A high value means sell orders only activate when the price has moved significantly, which may rarely occur.
2

Review the cancel distance

Ensure sellCancelDistancePercentage aligns with your risk tolerance and trading strategy. If this value is too tight, orders may cancel prematurely before they can execute.
Possible causes:
  • Not using USDC as your quote asset, which is required to qualify for Binance VIP1 status
  • Insufficient BNB balance to cover fees at a discounted rate
Solutions:
1

Switch to USDC as your quote asset

Set your quoteAsset to USDC. Trading USDC pairs at sufficient volume qualifies your account for Binance VIP1 status, which meaningfully reduces your per-trade fees.
2

Maintain a BNB balance

Keep enough BNB in your Binance account to pay trading fees. Binance applies a discount when fees are paid in BNB, further reducing your costs.
Possible causes:
  • License balance has been depleted
  • Server downtime or interruption
Solutions:
1

Check your license balance

Open the unCoded dashboard and review your remaining license balance. If it’s depleted, top it up via Binance Pay. See License system for instructions.
2

Monitor server health

Log in to your server and verify it is running. If the bot process has stopped, restart it from the dashboard. Consider setting up uptime monitoring to catch interruptions automatically.
If the standard troubleshooting steps above don’t resolve your issue, use these resources:Bot logsOpen the dashboard and check the live log feed for detailed error messages. Logs provide the most direct signal for what went wrong and when.Community supportJoin the unCoded Telegram group to get help from other users who may have encountered the same issue.Contact supportIf you’re still stuck, email info@arrowtrade.ch with:
  • A description of the issue
  • A copy of your log file
See Contact support for more information.