Merge pull request hummingbot#2192 from CoinAlpha/development

release / v.0.30.0 sync dev => master (PR 2 of 3)
Learn-2-trade · Aug 11, 2020 · 7659cfe · 7659cfe
2 parents 6e825b1 + ab1975e
commit 7659cfe
Show file tree

Hide file tree

Showing 206 changed files with 3,777 additions and 6,733 deletions.
diff --git a/conf/__init__.py b/conf/__init__.py
@@ -68,10 +68,6 @@
 kucoin_secret_key = os.getenv("KUCOIN_SECRET_KEY")
 kucoin_passphrase = os.getenv("KUCOIN_PASSPHRASE")
 
-# Bitcoin_com Tests
-bitcoin_com_api_key = os.getenv("BITCOIN_COM_API_KEY")
-bitcoin_com_secret_key = os.getenv("BITCOIN_COM_SECRET_KEY")
-
 test_web3_provider_list = [os.getenv("WEB3_PROVIDER")]
 
 # Liquid Tests

diff --git a/documentation/docs/advanced/exchange-rates.md b/documentation/docs/advanced/exchange-rates.md
diff --git a/documentation/docs/advanced/logging.md b/documentation/docs/advanced/logging.md
@@ -1,14 +1,14 @@
-# Logs and Logging
+# Logs and Logging
 
 As Hummingbot is an in-progress, open-access software, logs are available locally for each time an instance is run. Logs contain records of what happens when a bot is run, including the results of specified checks and behaviors as well as error tracing.
 
 ## Viewing Log Configurations
 
 The way that log files are structured is contained within `conf/hummingbot_logs.yml`. For now, we request that users leave the log settings at the defaults. This makes it easier for the Hummingbot team to trace bugs and other problems that users face when logs are submitted.
 
-## Error log collection
+## Error Log Collection
 
-The only data Hummingbot requests from users is error logs. We collect error logs for the sole purpose of debugging and continuously improving hummingbot. We'll never share the data with a third party.
+The only data Hummingbot requests from users is error logs. We collect error logs for the sole purpose of debugging and continuously improving Hummingbot. We'll never share the data with a third party.
 
 You can choose to disable error logging.
 

diff --git a/documentation/docs/advanced/telegram.md b/documentation/docs/advanced/telegram.md
@@ -45,16 +45,30 @@ Below, we show how to create a Telegram bot that integrates with your Hummingbot
 
 ### 3. Configure the Telegram Settings in Hummingbot
 
-* In the directory where you have installed Hummingbot, go to your global configuration file: `conf/conf_global.yml`.
-
-* Enter the following parameters at the end of the file:
+* In the directory where you have installed Hummingbot, go to your global configuration file `conf/conf_global.yml` and edit the following parameters inside the file:
 
 ```
 telegram_enabled: true
 telegram_token: <TELEGRAM TOKEN FROM STEP 1>
 telegram_chat_id: <TELEGRAM ID FROM STEP 2>
 ```
 
+* Locating your global configuration:<br />
+    * Installed from source: `hummingbot/conf`<br />
+    * Installed via Docker: `hummingbot_files/hummingbot_conf`<br />
+        `hummingbot_files` is the default name of the parent directory. This can be different depending on the setup
+        when the instance was created.<br />
+    * Installed via Binary (Windows): `%localappdata%\hummingbot.io\Hummingbot\conf`<br />
+    * Installed via Binary (MacOS): `~/Library/Application\ Support/Hummingbot/Conf`<br />
+
+* Alternatively, you can also configure your Telegram bot inside the Hummingbot client by using the following commands:
+
+```
+config telegram_enabled
+config telegram_token
+config telegram_chat_id
+```
+
 ### 4. Startup Hummingbot
 
 You can now startup Hummingbot and confirm that the integration is properly configured.
@@ -72,3 +86,5 @@ your hummingbot CLI window.
 
 ![](/assets/img/telegram-buttons.png)
 
+!!! tip
+    If you are running multiple bots with telegram enabled, you can use same [telegram chat id](https://telegram.me/userinfobot) with different telegram tokens from each bot you created to control all of them.  You can also enable [telegram chat folders](tg://settings/folders) to organize your bots.  Visit [telegram blog page](https://telegram.org/blog/folders) for more info. 
diff --git a/documentation/docs/assets/img/allow_mouse_reporting.png b/documentation/docs/assets/img/allow_mouse_reporting.png
diff --git a/documentation/docs/assets/img/git-bash.png b/documentation/docs/assets/img/git-bash.png
diff --git a/documentation/docs/assets/img/highlight_macos.png b/documentation/docs/assets/img/highlight_macos.png
diff --git a/documentation/docs/assets/img/jump_orders5.PNG b/documentation/docs/assets/img/jump_orders5.PNG
diff --git a/documentation/docs/assets/img/jump_orders6.PNG b/documentation/docs/assets/img/jump_orders6.PNG
diff --git a/documentation/docs/assets/img/lmb.svg b/documentation/docs/assets/img/lmb.svg
diff --git a/documentation/docs/assets/img/properties_windows.png b/documentation/docs/assets/img/properties_windows.png
diff --git a/documentation/docs/assets/img/quickstart_exit.png b/documentation/docs/assets/img/quickstart_exit.png
diff --git a/documentation/docs/assets/img/quickstart_import.png b/documentation/docs/assets/img/quickstart_import.png
diff --git a/documentation/docs/assets/img/quickstart_paper_on.png b/documentation/docs/assets/img/quickstart_paper_on.png
diff --git a/documentation/docs/assets/img/quickstart_pingpong.png b/documentation/docs/assets/img/quickstart_pingpong.png
diff --git a/documentation/docs/assets/img/quickstart_start.png b/documentation/docs/assets/img/quickstart_start.png
diff --git a/documentation/docs/assets/img/quickstart_starting.png b/documentation/docs/assets/img/quickstart_starting.png
diff --git a/documentation/docs/assets/img/quickstart_stop.png b/documentation/docs/assets/img/quickstart_stop.png
diff --git a/documentation/docs/assets/img/rasp-no-monitor.png b/documentation/docs/assets/img/rasp-no-monitor.png
diff --git a/documentation/docs/assets/img/rmb.png b/documentation/docs/assets/img/rmb.png
diff --git a/documentation/docs/assets/img/rpi-config.jpg b/documentation/docs/assets/img/rpi-config.jpg
diff --git a/documentation/docs/assets/img/rpi-hummingbot.jpg b/documentation/docs/assets/img/rpi-hummingbot.jpg
diff --git a/documentation/docs/assets/img/rpi-private-address.jpg b/documentation/docs/assets/img/rpi-private-address.jpg
diff --git a/documentation/docs/assets/img/rpi-ssh.jpg b/documentation/docs/assets/img/rpi-ssh.jpg
diff --git a/documentation/docs/connectors/eterbase.md b/documentation/docs/connectors/eterbase.md
@@ -9,9 +9,9 @@ ETERBASE is the first regulation-compliant European cryptocurrency exchange, off
 Eterbase is a centralized exchange, you will need to generate and provide your API key in order to trade using Hummingbot.
 
 ```
-Enter your Eterbase Account >>>
 Enter your Eterbase API key >>>
 Enter your Eterbase secret key >>>
+Enter your Eterbase Account >>>
 ```
 
 Private keys and API keys are stored locally for the operation of the Hummingbot client only. At no point will private or API keys be shared to CoinAlpha or be used in any way other than to authorize transactions required for the operation of Hummingbot.

diff --git a/documentation/docs/connectors/index.md b/documentation/docs/connectors/index.md
@@ -13,12 +13,13 @@ Connectors are packages of code that link Hummingbot's internal trading algorith
 ## Hummingbot-Supported Connectors
 
 * [Binance](/connectors/binance)
+* [Bittrex Global](/connectors/bittrex)
 * [Coinbase Pro](/connectors/coinbase)
+* [Eterbase](/connectors/eterbase)
 * [Huobi Global](/connectors/huobi)
-* [Bittrex Global](/connectors/bittrex)
-* [Liquid](/connectors/liquid)
-* [KuCoin](/connectors/kucoin)
 * [Kraken](/connectors/kraken)
+* [KuCoin](/connectors/kucoin)
+* [Liquid](/connectors/liquid)
 * [Radar Relay](/connectors/radar-relay)
 
 ## Community-Contributed Exchange Connectors
@@ -45,4 +46,4 @@ Please contact the support contact listed in the above table for support questio
 ## Coming Soon to Hummingbot
 
 * Bitfinex
-* HitBTC
+* HitBTC
diff --git a/documentation/docs/connectors/kraken.md b/documentation/docs/connectors/kraken.md
@@ -36,9 +36,19 @@ Take note that for your API keys to work with Hummingbot, **set the Nonce Window
 !!! warning "API key permissions"
     We recommend using only **"trade"** enabled API keys; enabling **"withdraw", "transfer", or the equivalent** is unnecessary for current Hummingbot strategies.
 
-Shows nonce reminder when adding API keys to Kraken
+Shows nonce reminder when adding API keys to Kraken.
+
 ![](/assets/img/kraken_nonce.png)
 
+Also note that your account must have funds to avoid getting this error when trying to connect your Kraken API on Hummingbot.
+
+```
+Failed connections:                                                                                      |
+    kraken: {'error': {'error': []}}
+
+10:12:24 - kraken_market - Error received from https://api.kraken.com/0/private/Balance. Response is {'error': []}.
+```
+
 ### Asset Codes
 
 Kraken uses asset codes in front of some pairs as a classification system. Asset codes starting with **'X'** represent cryptocurrencies, though this is no longer followed for the newest coins. Asset codes starting with **'Z'** represent fiat currencies.