Free, open source crypto trading bot
Go to file
2019-11-02 13:01:42 +01:00
.dependabot Add dependabot config yaml 2019-08-17 17:19:02 +02:00
.github add Operating system to issue template 2019-08-03 20:04:49 +02:00
bin Remove wrong import in legacy startup sript 2019-07-15 06:27:43 +02:00
build_helpers Pass test-data to dockerized backtest 2019-09-08 19:27:42 +02:00
docs Improve documentation regarding loading methods from hyperopt 2019-11-02 13:01:42 +01:00
freqtrade Allow populate-indicators to come from strategy 2019-11-02 11:10:33 +01:00
scripts Remove obsolete scripts 2019-10-24 23:11:07 +03:00
tests Merge pull request #2451 from freqtrade/bt_analysis_maxopen 2019-11-01 00:13:31 +03:00
user_data Improve documentation regarding loading methods from hyperopt 2019-11-02 13:01:42 +01:00
.coveragerc Fix paths in setup and travis 2019-09-08 19:05:51 +02:00
.dockerignore Add unnecessary files to .dockerignore 2018-05-06 20:23:20 +02:00
.gitignore Don't gitignore sample_strategy 2019-09-08 19:45:50 +02:00
.pylintrc ignore talib.abstract in pylint 2018-01-11 07:08:56 +02:00
.readthedocs.yml adding readdoc config 2018-12-28 14:11:22 +01:00
.travis.yml Make travis test-hyperopt the sample strategy 2019-11-02 11:12:08 +01:00
config_binance.json.example Move experimental settings to ask_strategy 2019-10-05 13:29:59 +03:00
config_full.json.example Replace coins in whitelist with existing ones 2019-10-30 09:26:08 +01:00
config_kraken.json.example Add --dl-trades cli flag 2019-10-13 13:15:22 +02:00
config.json.example Replace coins in whitelist with existing ones 2019-10-30 09:26:08 +01:00
CONTRIBUTING.md Fix beeing again ... 2019-10-08 21:16:35 +02:00
docker-compose.develop.yml use .develop dockerfile, move docs to develop.md, add freqtrade_bash 2019-09-26 09:22:49 -06:00
docker-compose.yml pr feedback regarding docker-compose naming 2019-09-23 13:17:20 -06:00
Dockerfile Update python base to 3.7.5 and install hyperopt dependencies 2019-10-20 10:47:04 +02:00
Dockerfile.develop Base dev Docker image on freqtradeorg/freqtrade:develop. 2018-12-17 13:53:22 -08:00
Dockerfile.pi Update PI install documentation and dockerfile 2019-09-25 11:40:34 +02:00
Dockerfile.technical Replace technical link 2019-05-25 15:54:35 +02:00
environment.yml Reorg dependencies to have hyperopt seperated 2019-09-25 11:40:34 +02:00
freqtrade.service Remove deprecated --dynamic-whitelist from freqtrade.service 2019-03-06 20:55:40 +03:00
freqtrade.service.watchdog Support for systemd watchdog via sd_notify 2019-03-10 21:04:38 +03:00
LICENSE Initial commit 2017-05-18 02:13:02 +02:00
MANIFEST.in Fix paths in setup and travis 2019-09-08 19:05:51 +02:00
mkdocs.yml docs: Create Advanced Post-installation Tasks section; move systemd stuff there 2019-10-26 13:26:22 +03:00
README.md Update slack link 2019-09-26 19:36:09 +02:00
requirements-common.txt Bump ccxt from 1.18.1306 to 1.18.1346 2019-10-28 07:42:58 +00:00
requirements-dev.txt Bump pytest from 5.2.1 to 5.2.2 2019-10-28 11:41:44 +00:00
requirements-hyperopt.txt Update python base to 3.7.5 and install hyperopt dependencies 2019-10-20 10:47:04 +02:00
requirements-plot.txt Bump plotly from 4.1.1 to 4.2.1 2019-10-21 07:50:16 +00:00
requirements.txt Bump pandas from 0.25.1 to 0.25.2 2019-10-21 08:33:48 +00:00
setup.cfg Fix paths in setup and travis 2019-09-08 19:05:51 +02:00
setup.py Merge pull request #2282 from freqtrade/jupyter_nbconvert 2019-10-01 19:58:20 +02:00
setup.sh Ensure git reset --hard is realy desired 2019-08-07 21:45:58 +02:00

Freqtrade

Build Status 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 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.

A note on Binance

For Binance, please add "BNB/<STAKE>" to your blacklist to avoid issues. Accounts having BNB accounts use this to pay for fees - if your first trade happens to be on BNB, further trades will consume this position and make the initial BNB order unsellable as the expected amount is not there anymore.

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