A cryptocurrency trading bot supporting multiple exchanges written in Golang.

Please note that this bot is under development and is not ready for production!

Community

Join our slack to discuss all things related to GoCryptoTrader! GoCryptoTrader Slack

Exchange Support Table

We are aiming to support the top 30 exchanges sorted by average liquidity as ranked by CoinMarketCap. However, we welcome pull requests for any exchange which does not match this criterion. If you need help with this, please join us on Slack.

** NA means not applicable as the exchange does not support the feature.

Current Features

• Support for all exchange fiat and digital currencies, with the ability to individually toggle them on/off.
• AES256 encrypted config file.
• REST API support for all exchanges.
• Websocket support for applicable exchanges.
• Ability to turn off/on certain exchanges.
• Communication packages (Slack, SMS via SMSGlobal, Telegram and SMTP).
• HTTP rate limiter package.
• Unified API for exchange usage.
• Customisation of HTTP client features including setting a proxy, user agent and adjusting transport settings.
• NTP client package.
• Database support (Postgres and SQLite3). See database.
• OTP generation tool. See gen otp.
• Connection monitor package.
• gRPC service and JSON RPC proxy. See gRPC service.
• gRPC client. See gctcli.
• Forex currency converter packages (CurrencyConverterAPI, CurrencyLayer, Exchange Rates, Fixer.io, OpenExchangeRates, Exchange Rate Host).
• Packages for handling currency pairs, tickers and orderbooks.
• Portfolio management tool; fetches balances from supported exchanges and allows for custom address tracking.
• Basic event trigger system.
• OHLCV/Candle retrieval support. See OHLCV.
• Recent and historic trade processing. See trades.
• Backtesting application. An event-driven backtesting tool to test and iterate trading strategies using historical or custom data. See backtester.
• Exchange HTTP mock testing. See mock.
• Exchange multichain deposits and withdrawals for specific exchanges. See multichain transfer support.

Development Tracking

Our Kanban board provides updates on:

• New feature development
• Bug fixes in progress
• Recently completed work
• Contribution opportunities

Follow our progress as we continuously improve GoCryptoTrader.

Contribution

Please feel free to submit any pull requests or suggest any desired features to be added.

When submitting a PR, please abide by our coding guidelines.

Compiling and Running instructions

Download and install Go from Go Downloads for your platform.

Linux/macOS

git clone https://github.com/thrasher-corp/gocryptotrader.git
cd gocryptotrader
go build
mkdir ~/.gocryptotrader
cp config_example.json ~/.gocryptotrader/config.json

Windows

git clone https://github.com/thrasher-corp/gocryptotrader.git
cd gocryptotrader
go build
mkdir %AppData%\GoCryptoTrader
copy config_example.json %APPDATA%\GoCryptoTrader\config.json

• Make any necessary changes to the config.json file.
• Run the gocryptotrader binary file.

Sonic JSON handling

GoCryptoTrader can optionally use the Sonic JSON library for improved performance, as a drop in replacement for golang.org/encoding/json. Please see sonic Requirements for supported platforms.

To enable sonic, build with the sonic_on tag:

go build -tags=sonic_on

Decimal handling

GoCryptoTrader uses shopspring/decimal by default through the shared types/decimal package. Build with udecimal_on to use udecimal instead:

go build -tags=udecimal_on

The tag changes both the implementation and some decimal behaviour. Before enabling it, note these differences:

• Precision: udecimal retains up to 19 fractional digits. Arithmetic and float conversion truncate anything beyond that without returning an error, so a non-zero result with a magnitude below 1e-19 becomes zero. Parsing does not truncate: NewFromString rejects inputs requiring more than 19 fractional digits.
• Division: The udecimal build truncates division results to 19 fractional digits. The default shopspring build rounds division results to 16 fractional digits, so the final digits can differ between builds.
• Large values: Plain decimal values round-trip through text, JSON and SQL codecs even when they exceed udecimal's native 200-character parser limit. Scientific notation is rejected when expanding it would produce more than 200 digits.
• API behaviour: Fractional Pow exponents are rejected.
• Representation: A udecimal-backed Decimal occupies 32 bytes instead of 16 bytes. Its binary encoding is not compatible with shopspring's and rejects values whose native encoding would exceed its one-byte length field.

Without the tag, Decimal remains an alias of shopspring's type.

Run the same benchmark suite against both implementations with:

make decimal_bench

The suite defaults to five 500 ms samples per operation. Override these with DECIMAL_BENCH_COUNT and DECIMAL_BENCH_TIME when collecting longer benchmark runs.

BenchmarkDecimalInexactFloat64 measures conversion to a plain float64; BenchmarkDecimalFloat64 separately measures conversion with the exactness flag required by Float64().

Donations

If this framework helped you in any way, or you would like to support the developers working on it, please donate Bitcoin to:

bc1qk0jareu4jytc0cfrhr5wgshsq8282awpavfahc

Binaries

Binaries will be published once the codebase reaches a stable condition.

Contributor List

A very special thank you to all who have contributed to this program