engine.xml

<?xml version="1.0"?>
<!--

Trading Engine config.

All elements are mandatory unless stated otherwise.
Only 1 engine element can be specified.

-->
<engine>

    <!--
    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.
    -->
    <emergency-stop-currency>BTC</emergency-stop-currency>

    <!--
    The <emergency-stop-balance> value must be set to prevent a catastrophic loss on the trading.
    The Trading Engine checks this value at the start of every trade cycle: if your <emergency-stop-currency> balance on
    the trading drops below this value, the Trading Engine will stop trading on all markets and shutdown.
    Manual intervention is then required to restart the bot. You can set this value to 0 to override this check.
    -->
    <emergency-stop-balance>1.0</emergency-stop-balance>

    <!--
    The <trade-cycle-interval> value is the interval in seconds that the Trading Engine will wait/sleep before executing
    the next 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.
    -->
    <trade-cycle-interval>60</trade-cycle-interval>
</engine>