BX-bot (Bex) is a simple Java automated trading bot for trading Bitcoin on cryptocurrency exchanges.

The project contains the basic infrastructure to trade on a cryptocurrency exchange... except for the trading strategies - you'll need to write those yourself. A simple example scalping strategy is included to get you started with the Trading API - take a look here for more ideas.

Exchange Adapters for using BTC-e, Bitstamp, Bitfinex, OKCoin, Huobi, GDAX, itBit, Kraken, and Gemini are included. Feel free to improve these or contribute new adapters to the project, that would be shiny.

The Trading API provides support for limit orders traded at the spot price; it does not support futures or margin trading... yet.

Warning: Trading Bitcoin carries significant financial risk; you could lose money. This software is provided 'as is' and released under the MIT license.

• Trading Engine - the execution unit. It provides a framework for integrating and executing Exchange Adapters and Trading Strategies.
• Exchange Adapters - the data stream unit. They provide access to a given exchange.
• Trading Strategies - the decision or strategy unit. This is where the trading decisions happen.
• Trading API - Trading Strategies use this API to make trades. Exchange Adapters implement this to provide access to a given exchange.
• Strategy API - Trading Strategies implement this for the Trading Engine to execute them.

Trading Strategies and Exchange Adapters are injected by the Trading Engine on startup. The bot uses a crude XML based dependency injection framework to achieve this; the long term goal is to run it as a Spring Boot app in a microservice system.

The bot was designed to fail hard and fast if any unexpected errors occur in the Exchange Adapters or Trading Strategies: it will log the error, send an email alert (if configured), and then shutdown.

BX-bot requires Oracle JDK 1.8 for the development and runtime environment.

You can use Maven 3 or Gradle 3 to build the bot and pull in the dependencies; BX-bot depends on log4j, JavaMail, Google Gson, Google Guava, and Spring Boot. See the Maven pom.xml for details.

1. Clone the repo locally (master branch).

1. From the project root, run ./mvnw clean install. If you want to run the exchange integration tests, use ./mvnw clean install -Pint. To execute both unit and integration tests, use ./mvnw clean install -Pall.
2. Take a look at the Javadoc in the ./target/apidocs folders of the bxbot-trading-api, bxbot-strategy-api, and bxbot-exchange-api modules after the build completes.

1. From the project root, run ./gradlew build. If you want to run the exchange integration tests, use ./gradlew integrationTests. To execute both unit and integration tests, use ./gradlew build integrationTests.
2. To generate the Javadoc, run ./gradlew javadoc and look in the ./build/docs/javadoc folders of the bxbot-trading-api, bxbot-strategy-api, and bxbot-exchange-api modules.

The bot has undergone basic unit testing on a best-effort basis; there is a continuous integration build running on Travis CI.

The latest stable build can always be found on the Releases page. The SNAPSHOT builds on master are active development builds, but the tests should always pass and the bot should always be deployable.

Issues and new features will be managed using the project Issue Tracker - submit bugs here.

You are welcome to take on new features or fix bugs! See here for how to get involved.

The bot provides a simple plugin framework for:

• Exchanges to integrate with.
• Markets to trade on.
• Trading Strategies to execute.

It uses XML configuration files. These live in the config folder.

Config changes are only applied at startup; they are not hot.

All configuration elements are mandatory unless specified otherwise.

Sample configurations for running on different exchanges can be found in the config/samplesfolder.

You specify the Exchange Adapter you want BX-bot to use in the exchange.xml file.

<exchange>
    <name>BTC-e</name>
    <adapter>com.gazbert.bxbot.exchanges.BtceExchangeAdapter</adapter>
    <authentication-config>
        <config-item>
            <name>key</name>
            <value>your-api-key</value>
        </config-item>
        <config-item>
            <name>secret</name>
            <value>your-secret-key</value>
        </config-item>
    </authentication-config>
    <network-config>
        <connection-timeout>30</connection-timeout>
        <non-fatal-error-codes>
            <code>502</code>
            <code>503</code>
        </non-fatal-error-codes>
        <non-fatal-error-messages>
            <message>Connection reset</message>
            <message>Connection refused</message>
        </non-fatal-error-messages>
    </network-config>
    <other-config>
        <config-item>
            <name>buy-fee</name>
            <value>0.5</value>
        </config-item>
        <config-item>
            <name>sell-fee</name>
            <value>0.5</value>
        </config-item>
    </other-config>
</exchange>

All elements are mandatory unless stated otherwise.

The <name> value is for descriptive use only. It is used in the log statements.

For the <adapter> value, you must specify the fully qualified name of the Exchange Adapter class for the Trading Engine to inject on startup. The class must be on the runtime classpath. See the How do I write my own Exchange Adapter? section for more details.

The <authentication-config> section is optional. If present, at least 1 <config-item> must be set - these are repeating key/value String pairs. This section is used by the inbuilt Exchange Adapters to configure their exchange trading API credentials - see the sample exchange.xml config files for details.

The <network-config> section is optional. If present, the <connection-timeout>, <non-fatal-error-codes>, and <non-fatal-error-messages> sections must be set. This section is used by the inbuilt Exchange Adapters to set their network configuration as detailed below:

• The <connection-timeout> is the timeout value that the exchange adapter will wait on socket connect/socket read when communicating with the exchange. Once this threshold has been breached, the exchange adapter will give up and throw an ExchangeNetworkException. The sample Exchange Adapters are single threaded: if a request gets blocked, it will block all subsequent requests from getting to the exchange. This timeout value prevents an indefinite block.

• The <non-fatal-error-codes> section contains a list of HTTP status codes that will trigger the adapter to throw a non-fatal 'ExchangeNetworkException'. This allows the bot to recover from temporary network issues. See the sample exchange.xml config files for status codes to use.

• The <non-fatal-error-messages> section contains a list of java.io exception messages that will trigger the adapter to throw a non-fatal ExchangeNetworkException. This allows the bot to recover from temporary network issues. See the sample exchange.xml config files for messages to use.

The <other-config> section is optional. If present, at least 1 <config-item> must be set - these are repeating key/value String pairs. This section is used by the inbuilt Exchange Adapters to configure any additional config, e.g. buy/sell fees.

BX-bot only supports 1 Exchange Adapter for each instance of the bot; you will need to create multiple (runtime) instances of the bot to run against different exchanges.

You specify which markets you want to trade on in the markets.xml file.

<markets>      
    <market>
        <label>BTC/USD</label>
        <id>btc_usd</id>
        <base-currency>BTC</base-currency>
        <counter-currency>USD</counter-currency>
        <enabled>true</enabled>
        <trading-strategy>scalping-strategy</trading-strategy>
    </market>
    <market>
        <label>LTC/BTC</label>
        <id>ltc_usd</id>
        <base-currency>LTC</base-currency>
        <counter-currency>BTC</counter-currency>
        <enabled>false</enabled>
        <trading-strategy>scalping-strategy</trading-strategy>
    </market>        
</markets>

All elements are mandatory unless stated otherwise.

The <label> value is for descriptive use only. It is used in the log statements.

The <id> value is the market id as defined on the exchange. E.g the BTC-e BTC/USD market id is btc_usd - see https://btc-e.com/api/3/docs

The <base-currency> value is the currency short code for the base currency in the currency pair. When you buy or sell a currency pair, you are performing that action on the base currency. The base currency is the commodity you are buying or selling. E.g. in a BTC/USD market, the first currency (BTC) is the base currency and the second currency (USD) is the counter currency.

The <counter-currency> value is the currency short code for the counter currency in the currency pair. This is also known as the quote currency.

The <enabled> value allows you to toggle trading on the market. Remember, config changes are only applied on startup.

The <trading-strategy> value must match a strategy <id> defined in your strategies.xml config. Currently, BX-bot only supports 1 <trading-strategy> per <market>.

You specify the Trading Strategies you wish to use in the strategies.xml file.

<trading-strategies>
    <strategy>
        <id>scalping-strategy</id>
        <label>Basic Scalping Strat</label>
        <description>A simple trend following scalper that buys at current BID price and sells at current
         ASK price, taking profit from the spread. The exchange fees are factored in.</description>
        <class-name>com.gazbert.bxbot.strategies.ExampleScalpingStrategy</class-name>
        <configuration>
            <config-item>
                <name>btc-buy-order-amount</name>
                <value>0.5</value>
            </config-item>
            <config-item>
                <name>minimumPercentageGain</name>
                <value>1</value>
            </config-item>
        </configuration>
    </strategy>
    <strategy>
        <id>macd-strategy</id>
        <label>MACD Based Strat</label>
        <description>Strat uses MACD data to take long position in USD.</description>
        <class-name>com.gazbert.bxbot.strategies.YourMacdStrategy</class-name>
        <configuration>
            <config-item>
                <name>btc-buy-order-amount</name>
                <value>0.5</value>
            </config-item>
            <config-item>
                <name>shortEmaInterval</name>
                <value>12</value>
            </config-item>
            <config-item>
                <name>longEmaInterval</name>
                <value>26</value>
            </config-item>
        </configuration>
    </strategy>
</trading-strategies>

All elements are mandatory unless stated otherwise.

The <id> value must be unique. The markets.xml <market><trading-strategy> entries cross-reference this.

The <label> value is for descriptive use only. It is used in the log statements.

The <description> value is optional and not used anywhere yet; a new Web UI will in the future.

For the <class-name> value, you must specify the fully qualified name of your Trading Strategy class for the Trading Engine to inject on startup. The class must be on the runtime classpath.

The <configuration> section is optional. It allows you to set custom key/value pair String config - this is passed to your Trading Strategy when the bot starts up; see the How do I write my own Trading Strategy? section.

The engine.xml file is used to configure the Trading Engine.

<engine>
    <emergency-stop-currency>BTC</emergency-stop-currency>
    <emergency-stop-balance>1.0</emergency-stop-balance>
    <trade-cycle-interval>60</trade-cycle-interval>
</engine>

All elements are mandatory.

The <emergency-stop-currency> value must be set to prevent catastrophic loss on the exchange. This is normally the currency you intend to hold a long position in. It should be set to the currency short code for the wallet, e.g. BTC, LTC, USD. This value can be case sensitive for some exchanges - check the Exchange Adapter documentation.

The <emergency-stop-balance> value must be set to prevent catastrophic loss on the exchange. The Trading Engine checks this value at the start of every trade cycle: if your <emergency-stop-currency> wallet balance on the exchange drops below this value, the Trading Engine will log it, send an Email Alert (if configured) and then shutdown.

The <trade-cycle-interval> value is the interval in seconds that the Trading Engine will wait/sleep before executing each trade cycle. The minimum value is 1 second. Some exchanges allow you to hit them harder than others. However, while their API documentation might say one thing, the reality is you might get socket timeouts and 5xx responses if you hit it too hard - you cannot perform low latency trading over the public internet ;-) I might have EMA/MACD strats running every 5 mins and 'scalping' strats running every 60s on BTC-e. You'll need to experiment with the trade cycle interval for different exchanges.

You specify the Email Alerts config in the email-alerts.xml file.

<email-alerts>
    <enabled>false</enabled>
    <smtp-config>
        <smtp-host>smtp.gmail.com</smtp-host>
        <smtp-tls-port>587</smtp-tls-port>
        <account-username>[email protected]</account-username>
        <account-password>your.account.password</account-password>
        <from-addr>[email protected]</from-addr>
        <to-addr>[email protected]</to-addr>
    </smtp-config>
</email-alerts>

This config is used to send email alerts when the bot is forced to shutdown due to an unexpected error occurring in the Trading Strategies or Exchange Adapters.

All elements are mandatory unless stated otherwise.

If <enabled> is set to 'true', the bot will load the optional <smtp-config> config. If <enabled> is set to 'false', you can omit the <smtp-config> config.

If enabled, the bot will send email alerts to the <to-addr> if it needs to shutdown due to a critical error.

Sample SMTP config for using a Gmail account is shown above.

The email is sent using TLS.

Logging for the bot is provided by log4j. The log file is written to logs/bxbot.log uses a rolling policy. It will create up to 7 archives on the same day (1-7) that are stored in a directory based on the current year and month, and will compress each archive using gzip. Once a file reaches 100 MB or a new day is started, it is archived and a new log file is created. Only the last 90 archives are kept. The logging level is set at info. You can change this default logging configuration in the config/log4j2.xml file.

I recommend running at info level, as debug level logging will produce a lot of output from the Exchange Adapters; it's very handy for debugging, but not so good for your disk space!

"Battle not with monsters, lest ye become a monster, and if you gaze into the abyss, the abyss gazes also into you." - Friedrich Nietzsche

The best place to start is with the sample Trading Strategy provided - see the latest BasicScalpingExampleStrategy. More information can be found here.

Your strategy must implement the TradingStrategy interface. This allows the Trading Engine to:

• inject your strategy on startup of the bot.
• pass any configuration (you set up in the strategies.xml) to your strategy.
• invoke your strategy during each trade cycle.

The Trading Engine will only send 1 thread through your Trading Strategy; you do not have to code for concurrency.

You use the TradingApi to make trades etc. The API is passed to your Trading Strategy implementation init method when the bot starts up. See the Javadoc for full details of the API.

Your Trading Strategy implementation should throw a StrategyException whenever it 'breaks'. BX-bot's error handling policy is designed to fail hard and fast; it will log the error, send an Email Alert (if configured), and shutdown.

Note that the inbuilt Exchange Adapters will (some more often than others!) throw an ExchangeNetworkException if they encounter network issues connecting with the exchange. Your strategy should always catch this exception and choose what to do next, e.g. retry the previous Trading API call, or 'swallow' the exception and wait until the Trading Engine invokes the strategy again at the next trade cycle.

You specify the Trading Strategies you wish to use in the strategies.xml file - see the main Configuration section for full details.

The optional <configuration> section in the strategies.xml allows you to set key/value pair String config to pass to your Trading Strategy implementation.

On startup, the Trading Engine will pass the config to your Trading Strategy's init method in the StrategyConfig arg.

Your Trading Strategy implementation has a compile-time dependency on the Strategy API and the Trading API.

The inbuilt BasicScalpingExampleStrategy also has a compile-time dependency on log4j and Google Guava.

To get going fast, you can code your Trading Strategy and place it in the bxbot-strategies module alongside the example strategy. When you build the project, your Trading Strategy will be included in the BX-bot jar. You can also create your own jar for your strats, e.g. my-strats.jar, and include it on BX-bot's runtime classpath - see the Installation Guide for how to do this.

The best place to start is with one of the sample Exchange Adapters provided - see the latest BitstampExchangeAdapter for example.

Your adapter must implement the TradingApi and the ExchangeAdapter interfaces. This allows for:

• the main Trading Engine to inject your adapter on startup and initialise it with config from the exchange.xml file.
• the Trading Strategies to invoke your adapter's implementation of the TradingApi during each trade cycle.

AbstractExchangeAdapter is a handy base class that all the inbuilt Exchange Adapters extend - it could be useful.

The Trading Engine will only send 1 thread through your Exchange Adapter; you do not have to code for concurrency.

Your Exchange Adapter implementation should throw a TradingApiException whenever it breaks; the Trading Strategies should catch this and decide how they want to proceed.

The Trading API provides an ExchangeNetworkException for adapters to throw when they cannot connect to the exchange to make Trading API calls. This allows for Trading Strategies to recover from temporary network failures. The exchange.xml config file has an optional <network-config> section, which contains <non-fatal-error-codes> and <non-fatal-error-messages> elements - these can be used to tell the adapter when to throw the exception.

The first release of the bot is single-threaded for simplicity. The downside to this is that if an API call to the exchange gets blocked on IO, BX-bot will get stuck until your Exchange Adapter frees the block. The Trading API provides an ExchangeNetworkException for your adapter to throw if it times-out connecting to the exchange. It is your responsibility to free up any blocked connections - see the AbstractExchangeAdapter for an example how to do this.

The Trading Engine will also call your adapter directly when performing the Emergency Stop check to see if your <emergency-stop-currency> wallet balance on the exchange drops below the configured <emergency-stop-value> value. If this call to the TradingApi getBalanceInfo() fails and is not due to a TradingApiException, the Trading Engine will log the error, send an Email Alert (if configured), and shutdown. If the API call failed due to an ExchangeNetworkException, the Trading Engine will log the error and sleep until the next trade cycle.

You provide your Exchange Adapter details in the exchange.xml file - see the main Configuration section for full details.

Your Exchange Adapter implementation has a compile-time dependency on the Trading API.

The inbuilt Exchange Adapters also have compile-time dependencies on log4j, Google Gson, and Google Guava.

To get going fast, you can code your Exchange Adapter and place it in the bxbot-exchanges module alongside the other inbuilt adapters. When you build the project, your Exchange Adapter will be included in the BX-bot jar. You can also create your own jar for your adapters, e.g. my-adapters.jar, and include it on BX-bot's runtime classpath - see the Installation Guide for how to do this.

The Releases page has the stable releases. Or you can grab the latest code from the head of the master branch.

1. Prerequisite: Oracle JDK 1.8 needs to be installed on the machine you want to run the bot.
2. Edit the config XML files as required.

1. If you plan on using Trading Strategies or Exchange Adapters that are packaged in separate jar files, you'll need to add the dependency in the bxbot-app/pom.xml - see the commented out dependency examples inside it.
2. From the project root, run ./mvnw clean assembly:assembly to produce the distribution artifacts bxbot-app-<version>-dist.tar.gz and bxbot-app-<version>-dist.zip in the ./target folder.
3. Copy either the bxbot-app-<version>-dist.tar.gz or the bxbot-app-<version>-dist.zip onto the machine you want to run the bot and unzip it someplace.
4. Usage: ./bxbot.sh [start|stop|status]

1. If you plan on using Trading Strategies or Exchange Adapters that are packaged in separate jar files, you'll need to add the dependency in the bxbot-app/build.gradle - see the commented out dependency examples inside it.
2. From the project root, run ./gradlew buildTarGzipDist or ./gradlew buildZipDist to build the distribution artifact: either bxbot-app-<version>.tar.gz or bxbot-app-<version>.zip respectively. It will be placed in the ./build/distributions folder.
3. Copy the artifact onto the machine you want to run the bot and unzip it someplace.
4. Usage: ./bxbot.sh [start|stop|status]

The following features are in the pipeline:

• REST API for administering the bot.
• Web UI for administering the bot written in Angular.
• An experimental project to register BX-bot trades using an Ethereum blockchain.
• Trade Analysis app - a microservice that will feed off trading events sent by the bots.
• Android app for administering the bot.

See the main project Issue Tracker for timescales and progress.