Support

Get help and find answers to common questions.

📚 Documentation

The best place to start is our comprehensive documentation covering setup, configuration, and usage.

View Documentation →

🐛 Report Issues

Found a bug or have a feature request? Open an issue on GitHub. Our community and team can help troubleshoot problems.

GitHub Issues →

💬 Community

Join discussions with other EDISON users. Share strategies, ask questions, and learn from the community.

GitHub Discussions →

Common Questions

Q: Is EDISON free?

Yes! EDISON is completely free and open-source. You can download it from GitHub and run it on your own system.

Q: Do I need to provide my API keys to anyone?

No! API keys should only be stored locally on your system. EDISON is self-contained and does not send your keys to any server.

Q: Which exchanges are supported?

EDISON currently integrates with Bybit. The architecture supports adding more exchanges. Check the documentation for details.

Q: Can I run EDISON on the cloud?

Yes, you can deploy EDISON on any server or cloud platform (AWS, DigitalOcean, Heroku, etc.) that supports Node.js. Ensure the server is secure and monitor it regularly.

Q: How do I backtest strategies?

EDISON includes backtesting functionality. See the documentation for instructions on how to backtest strategies using historical data.

Q: What if the bot crashes or loses connection?

EDISON includes error handling and recovery mechanisms. However, you should monitor it regularly and have a plan to stop trading immediately if issues arise. Review logs for troubleshooting.

Q: Can I modify the source code?

Absolutely! EDISON is open-source. You can read, modify, and customize it for your needs. Check the GitHub repository for the license terms.

Q: Is there a Discord or Telegram community?

Currently support is provided through GitHub Issues and Discussions. Check the repository for the latest community channels.

🛡️ Security Best Practices

  • ✓Store API keys securely - never commit them to version control
  • ✓Use testnet/demo trading before using real funds
  • ✓Monitor logs and bot activity regularly
  • ✓Test configuration changes on paper trading first
  • ✓Have a kill switch to stop trading immediately if needed
  • ✓Keep your system and Node.js dependencies updated
  • ✓Review the source code if you're unfamiliar with it

Need More Help?

Check the GitHub repository for issues, discussions, and documentation updates.

Visit GitHub Repository →