docs/guides/faq.en.md
Quick answers to common questions. For detailed troubleshooting, see Troubleshooting Guide.
NOFX is an AI-powered cryptocurrency trading bot that uses large language models (LLMs) to make trading decisions on futures markets.
AI trading is experimental and not guaranteed to be profitable. Always start with small amounts and never invest more than you can afford to lose.
Yes! NOFX supports running multiple traders with different configurations, AI models, and trading strategies.
No! NOFX has a web UI for all configuration. However, basic command line knowledge helps with setup and troubleshooting.
Recommended: Yes, use a subaccount dedicated to NOFX for better risk isolation. However, note that some subaccounts have restrictions (e.g., 5x max leverage on Binance).
Common reasons:
Configurable! Default is every 3-5 minutes. Too frequent = overtrading, too slow = missed opportunities.
Yes! You can:
Default: 3 positions. This is a soft limit defined in the AI prompt, not hard-coded. See decision/engine.go:266.
Error: Order's position side does not match user's setting
Solution: Switch to Hedge Mode (双向持仓)
Why: NOFX uses PositionSide(LONG/SHORT) which requires Hedge Mode.
See Issue #202 and Troubleshooting Guide.
Solution:
# Check what's using port 8080
lsof -i :8080
# Change port in .env
NOFX_BACKEND_PORT=8081
Quick Check:
# Is backend running?
curl http://localhost:8080/api/health
# Should return: {"status":"ok"}
If not, check Troubleshooting Guide.
Solution:
# Stop all NOFX processes
docker compose down
# OR
pkill nofx
# Restart
docker compose up -d
Depends on your model and decision frequency:
Estimates based on typical usage. Actual costs vary by provider and usage.
Yes! Each trader can use a different AI model. You can even A/B test different models.
Yes, to some extent. NOFX provides historical performance feedback in each decision prompt, allowing the AI to adjust its strategy.
All data is stored locally in PostgreSQL (Docker volume postgres_data) plus:
decision_logs/ - AI decision recordsAPI keys are stored in local databases. Never share your databases or .env files. We recommend using API keys with IP whitelist restrictions.
Yes! Use pg_dump or psql to export data:
docker compose exec postgres \
psql -U nofx -d nofx -c "SELECT * FROM trades;"
See the comprehensive Troubleshooting Guide for:
Yes! We welcome contributions:
Open a Feature Request with your idea!
Last Updated: 2025-11-02