cryptobob 1.1.0

CryptoBob package

CryptoBob

CryptoBob is a radically simple crypto currency bot, which interacts with Kraken and…

• … automatically buys crypto currencies on a recurring basis
• … automatically withdraws crypto currencies when a threshold is reached

CryptoBob is your perfect little sidekick, when you want to automate the purchase and storage of crypto currencies on your hardware wallet / ledger. Of course there are services out there doing this, but usually Kraken has much better fees than those services, and a much better selection of crypto ;)

Installation

Install the package via PyPi:

pip3 install cryptobob

Install the package from source:

pip3 install cryptobob@git+https://git.confirm.ch/confirm/cryptobob.git

Usage

The usage of cryptobob is quite simple:

usage: cryptobob [-h] [-c CONFIG] [-v] {run,assets,otp}

CryptoBob - The bot which buys & withdraws crypto automatically.

positional arguments:
  {run,assets,otp}            action to execute

options:
  -h, --help                  show this help message and exit
  -c CONFIG, --config CONFIG  the path to the CryptoBob config
  -v, --verbose               enable verbose logging mode (repeat to increase verbosity, up to -vvv)

To display all assets listed on Kraken, you can run:

cryptobob assets

To run CryptoBob, you can simply execute:

cryptobob run -vv

In case you configured OTP for your API key and want to get a one-time code, you can run:

cryptobob otp

Please note you've to configure CryptoBob accordingly.
Check out the next section for the configuration.

Configuration

By default, CryptoBob is searching its configuration file under ~/.cryptobob.yml.
Feel free to change the configuration file path by specifying the -c or --config CLI flag.

You can find an example configuration in the CryptoBob repository called cryptobob.yml.

IMPORTANT: The configuration file contains sensitive informations. Make sure you set the permissions right!

Runtime data

Please note CryptoBob doesn't store any runtime data or alike on your system, since it will always check in with Kraken directly.

For example, when you configure an interval of buying a certain asset, CryptoBob will always check the order history, to find the last executed order. Given the retreived order timestamp, CryptoBob decides to open new orders based on your configuration.

Of course, only orders initiated by CryptoBob will be queried for the timestamps (achieved via userref on ClosedOrders).