Free, open source crypto trading bot
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
Matthias d9e83cc4e2
Run CI on windows python 3.8
6 years ago
.dependabot Add dependabot config yaml 7 years ago
.github Run CI on windows python 3.8 6 years ago
bin Break the old binary file so users are forced to reinstall 6 years ago
build_helpers Run CI on windows python 3.8 6 years ago
docs Merge pull request #3000 from freqtrade/fix/jupyter_example 6 years ago
freqtrade Merge pull request #3003 from Fredrik81/cores-and-arguments 6 years ago
scripts Merge pull request #2540 from freqtrade/rpc/fixes 6 years ago
tests Merge pull request #2995 from freqtrade/stake_curr_empty 6 years ago
user_data Remove unused directory from user_data 6 years ago
.coveragerc Update documentation for create-userdir util 6 years ago
.dockerignore Add unnecessary files to .dockerignore 8 years ago
.gitignore Don't gitignore sample_strategy 7 years ago
.pylintrc ignore talib.abstract in pylint 8 years ago
.readthedocs.yml adding readdoc config 7 years ago
.travis.yml Update documentation 6 years ago
CONTRIBUTING.md Lowercase freqtrade 6 years ago
Dockerfile Bump python from 3.8.1-slim-buster to 3.8.2-slim-buster 6 years ago
Dockerfile.develop Base dev Docker image on freqtradeorg/freqtrade:develop. 7 years ago
Dockerfile.pi Update Actions CI to new subcommands 6 years ago
Dockerfile.technical Replace technical link 7 years ago
LICENSE Initial commit 9 years ago
MANIFEST.in Fix paths in setup and travis 7 years ago
README.md Add official support for Kraken 6 years ago
config.json.example Merge pull request #2831 from xmatthias/feat/new_config 6 years ago
config_binance.json.example Fix small json formatting issue 6 years ago
config_full.json.example Merge branch 'develop' into data_handler 6 years ago
config_kraken.json.example Fix small json formatting issue 6 years ago
docker-compose.develop.yml use .develop dockerfile, move docs to develop.md, add freqtrade_bash 6 years ago
docker-compose.yml Improve docker-compose file to be ready to use 6 years ago
environment.yml Reorg dependencies to have hyperopt seperated 7 years ago
freqtrade.service Update documentation to use subcommands 6 years ago
freqtrade.service.watchdog Update documentation to use subcommands 6 years ago
mkdocs.yml Update install-script documentation and reorder installation steps 6 years ago
requirements-common.txt Bump ccxt from 1.22.95 to 1.23.30 6 years ago
requirements-dev.txt Bump coveralls from 1.10.0 to 1.11.1 6 years ago
requirements-hyperopt.txt Bump scikit-learn from 0.22.1 to 0.22.2 6 years ago
requirements-plot.txt Bump plotly from 4.5.1 to 4.5.2 6 years ago
requirements.txt Bump pandas from 1.0.0 to 1.0.1 6 years ago
setup.cfg Fix paths in setup and travis 7 years ago
setup.py Add Questionaire workflow 6 years ago
setup.sh Address PR Review 6 years ago

README.md

Freqtrade

Freqtrade CI Coverage Status Documentation Maintainability

Freqtrade is a free and open source crypto trading bot written in Python. It is designed to support all major exchanges and be controlled via Telegram. It contains backtesting, plotting and money management tools as well as strategy optimization by machine learning.

freqtrade

Disclaimer

This software is for educational purposes only. Do not risk money which you are afraid to lose. USE THE SOFTWARE AT YOUR OWN RISK. THE AUTHORS AND ALL AFFILIATES ASSUME NO RESPONSIBILITY FOR YOUR TRADING RESULTS.

Always start by running a trading bot in Dry-run and do not engage money before you understand how it works and what profit/loss you should expect.

We strongly recommend you to have coding and Python knowledge. Do not hesitate to read the source code and understand the mechanism of this bot.

Exchange marketplaces supported

Documentation

We invite you to read the bot documentation to ensure you understand how the bot is working.

Please find the complete documentation on our website.

Features

  • Based on Python 3.6+: For botting on any operating system - Windows, macOS and Linux.
  • Persistence: Persistence is achieved through sqlite.
  • Dry-run: Run the bot without playing money.
  • Backtesting: Run a simulation of your buy/sell strategy.
  • Strategy Optimization by machine learning: Use machine learning to optimize your buy/sell strategy parameters with real exchange data.
  • Edge position sizing Calculate your win rate, risk reward ratio, the best stoploss and adjust your position size before taking a position for each specific market. Learn more.
  • Whitelist crypto-currencies: Select which crypto-currency you want to trade or use dynamic whitelists.
  • Blacklist crypto-currencies: Select which crypto-currency you want to avoid.
  • Manageable via Telegram: Manage the bot with Telegram.
  • Display profit/loss in fiat: Display your profit/loss in 33 fiat.
  • Daily summary of profit/loss: Provide a daily summary of your profit/loss.
  • Performance status report: Provide a performance status of your current trades.

Quick start

Freqtrade provides a Linux/macOS script to install all dependencies and help you to configure the bot.

git clone git@github.com:freqtrade/freqtrade.git
cd freqtrade
git checkout develop
./setup.sh --install

For any other type of installation please refer to Installation doc.

Basic Usage

Bot commands

usage: freqtrade [-h] [-v] [--logfile FILE] [--version] [-c PATH] [-d PATH]
                 [-s NAME] [--strategy-path PATH] [--dynamic-whitelist [INT]]
                 [--db-url PATH] [--sd-notify]
                 {backtesting,edge,hyperopt} ...

Free, open source crypto trading bot

positional arguments:
  {backtesting,edge,hyperopt}
    backtesting         Backtesting module.
    edge                Edge module.
    hyperopt            Hyperopt module.

optional arguments:
  -h, --help            show this help message and exit
  -v, --verbose         Verbose mode (-vv for more, -vvv to get all messages).
  --logfile FILE        Log to the file specified
  --version             show program's version number and exit
  -c PATH, --config PATH
                        Specify configuration file (default: None). Multiple
                        --config options may be used.
  -d PATH, --datadir PATH
                        Path to backtest data.
  -s NAME, --strategy NAME
                        Specify strategy class name (default:
                        DefaultStrategy).
  --strategy-path PATH  Specify additional strategy lookup path.
  --dynamic-whitelist [INT]
                        Dynamically generate and update whitelist based on 24h
                        BaseVolume (default: 20). DEPRECATED.
  --db-url PATH         Override trades database URL, this is useful if
                        dry_run is enabled or in custom deployments (default:
                        None).
  --sd-notify           Notify systemd service manager.

Telegram RPC commands

Telegram is not mandatory. However, this is a great way to control your bot. More details and the full command list on our documentation

  • /start: Starts the trader
  • /stop: Stops the trader
  • /status [table]: Lists all open trades
  • /count: Displays number of open trades
  • /profit: Lists cumulative profit from all finished trades
  • /forcesell <trade_id>|all: Instantly sells the given trade (Ignoring minimum_roi).
  • /performance: Show performance of each finished trade grouped by pair
  • /balance: Show account balance per currency
  • /daily <n>: Shows profit or loss per day, over the last n days
  • /help: Show help message
  • /version: Show version

Development branches

The project is currently setup in two main branches:

  • develop - This branch has often new features, but might also cause breaking changes.
  • master - This branch contains the latest stable release. The bot 'should' be stable on this branch, and is generally well tested.
  • feat/* - These are feature branches, which are being worked on heavily. Please don't use these unless you want to test a specific feature.

Support

Help / Slack

For any questions not covered by the documentation or for further information about the bot, we encourage you to join our slack channel.

Bugs / Issues

If you discover a bug in the bot, please search our issue tracker first. If it hasn't been reported, please create a new issue and ensure you follow the template guide so that our team can assist you as quickly as possible.

Feature Requests

Have you a great idea to improve the bot you want to share? Please, first search if this feature was not already discussed. If it hasn't been requested, please create a new request and ensure you follow the template guide so that it does not get lost in the bug reports.

Pull Requests

Feel like our bot is missing a feature? We welcome your pull requests!

Please read our Contributing document to understand the requirements before sending your pull-requests.

Coding is not a neccessity to contribute - maybe start with improving our documentation? Issues labeled good first issue can be good first contributions, and will help get you familiar with the codebase.

Note before starting any major new feature work, please open an issue describing what you are planning to do or talk to us on Slack. This will ensure that interested parties can give valuable feedback on the feature, and let others know that you are working on it.

Important: Always create your PR against the develop branch, not master.

Requirements

Uptodate clock

The clock must be accurate, syncronized to a NTP server very frequently to avoid problems with communication to the exchanges.

Min hardware required

To run this bot we recommend you a cloud instance with a minimum of:

  • Minimal (advised) system requirements: 2GB RAM, 1GB disk space, 2vCPU

Software requirements