The modern cryptocurrency trading bot framework written in Go.
Go to file
2022-06-18 16:32:53 +08:00
.github fix: move gofmt to golintci, disable most of the checks 2022-06-17 19:00:36 +09:00
apps/backtest-report optimizer: use moment.js 2022-06-15 16:24:28 +08:00
assets add backtest report screenshot 2022-05-20 19:37:32 +08:00
charts/bbgo fix helm chart grpc binding string 2022-05-09 19:09:40 +08:00
cmd fix: apply gofmt on all files, add revive action 2022-06-17 16:06:59 +09:00
config fix: rename useHeikinAshi to heikinAshi in config 2022-06-17 11:38:36 +09:00
contracts add missing files on bbgo contract folder 2022-01-26 14:51:38 +09:00
desktop desktop: add more app properties 2021-02-17 17:28:54 +08:00
doc add v1.35.0 release note 2022-06-17 14:01:14 +08:00
evans grpc: register trading server 2022-04-16 23:45:10 +08:00
examples fix: apply gofmt on all files, add revive action 2022-06-17 16:06:59 +09:00
frontend add missing import 2022-06-16 22:52:32 +08:00
linode add linode stackscripts 2021-03-16 19:57:37 +08:00
migrations avoid running truncate table in the migration script 2022-06-17 13:57:15 +08:00
pkg pivotshort: call BindTradeStats 2022-06-18 16:32:53 +08:00
python bump version to 0.1.9 2022-05-16 12:29:09 +08:00
scripts add more commands to the release test 2022-06-08 15:10:43 +08:00
utils move util/embed to utils/ 2022-06-08 15:10:43 +08:00
v2 bump go version to 1.17 2022-03-15 17:45:26 +08:00
.dockerignore add .dockerignore 2022-01-22 00:51:30 +08:00
.evans.toml add .evans.toml 2022-04-13 12:35:58 +08:00
.gitignore fix: gosimple alert 2022-06-17 20:19:51 +09:00
.golangci.yml fix: increase golangci timeout 2022-06-17 20:27:03 +09:00
.markdownlint.yaml feature: add pre-commit 2022-06-17 16:07:00 +09:00
.pre-commit-config.yaml fix: move gofmt to golintci, disable most of the checks 2022-06-17 19:00:36 +09:00
.travis.yml use bbgo_dev for mysql rockhopper 2021-03-14 11:18:22 +08:00
app.json add the first app.json for heroku 2020-10-26 10:29:05 +08:00
bbgo.sql add bbgo.sql 2021-01-06 15:13:59 +08:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2021-11-26 01:02:02 +08:00
codecov.yml feature: add codecoverage and add race detection in go test, fix: fix race conditions 2022-06-10 14:01:14 +09:00
CONTRIBUTING.md Create CONTRIBUTING.md 2021-11-26 01:14:28 +08:00
deploy.sh deploy.sh: add sudo command 2021-12-06 18:17:52 +08:00
Dockerfile fix: sqlite3 compilation 2022-05-17 12:30:36 +09:00
go.mod upgrade rockhopper 2022-06-17 13:45:13 +08:00
go.sum upgrade rockhopper 2022-06-17 13:45:13 +08:00
LICENSE Replace License with AGPL 2022-04-29 02:15:35 +08:00
Makefile move util/embed to utils/ 2022-06-08 15:10:43 +08:00
Procfile add Procfile 2020-10-26 10:46:19 +08:00
README.md feature: add pre-commit 2022-06-17 16:07:00 +09:00
rockhopper_mysql.yaml add rockhopper command for test 2022-05-03 16:48:03 +08:00
rockhopper_sqlite.yaml add rockhopper config for sqlite3 2021-02-05 14:15:44 +08:00

BBGO

A trading bot framework written in Go. The name bbgo comes from the BB8 bot in the Star Wars movie.

Current Status

Go GoDoc Go Report Card DockerHub Coverage Status open collective badge open collective badge

Community

Telegram Global Telegram Taiwan Twitter

What You Can Do With BBGO

Trading Bot Users 💁‍♀️ 💁‍♂️

You can use BBGO to run the built-in strategies.

Strategy Developers 🥷

You can use BBGO's trading unit and back-test unit to implement your own strategies.

Trading Unit Developers 🧑‍💻

You can use BBGO's underlying common exchange API, currently it supports 4+ major exchanges, so you don't have to repeat the implementation.

Features

Screenshots

bbgo dashboard

bbgo backtest report

Supported Exchanges

  • Binance Spot Exchange (and binance.us)
  • FTX Spot Exchange
  • OKEx Spot Exchange
  • Kucoin Spot Exchange
  • MAX Spot Exchange (located in Taiwan)

Documentation and General Topics

BBGO Tokenomics

To support the development of BBGO, we have created a bounty pool to support contributors by giving away $BBG tokens. Check the details in $BBG Contract Page and our official website

Requirements

Get your exchange API key and secret after you register the accounts (you can choose one or more exchanges):

This project is maintained and supported by a small group of team. If you would like to support this project, please register on the exchanges using the provided links with referral codes above.

Installation

Install from binary

The following script will help you set up a config file and a dotenv file:

# grid trading strategy for binance exchange
bash <(curl -s https://raw.githubusercontent.com/c9s/bbgo/main/scripts/setup-grid.sh) binance

# grid trading strategy for max exchange
bash <(curl -s https://raw.githubusercontent.com/c9s/bbgo/main/scripts/setup-grid.sh) max

# bollinger grid trading strategy for binance exchange
bash <(curl -s https://raw.githubusercontent.com/c9s/bbgo/main/scripts/setup-bollgrid.sh) binance

# bollinger grid trading strategy for max exchange
bash <(curl -s https://raw.githubusercontent.com/c9s/bbgo/main/scripts/setup-bollgrid.sh) max

If you already have configuration somewhere, a download-only script might be suitable for you:

bash <(curl -s https://raw.githubusercontent.com/c9s/bbgo/main/scripts/download.sh)

Or refer to the Release Page and download manually.

Since v2, we've added new float point implementation from dnum to support decimals with higher precision. To download & setup, please refer to Dnum Installation

One-click Linode StackScript

Build from source

See Build from source

Configuration

Add your dotenv file:

# for Binance Exchange, if you have one
BINANCE_API_KEY=
BINANCE_API_SECRET=

# if you want to use binance.us, change this to 1
BINANCE_US=0

# for MAX exchange, if you have one
MAX_API_KEY=
MAX_API_SECRET=

# for FTX exchange, if you have one
FTX_API_KEY=
FTX_API_SECRET=
# specify it if credentials are for subaccount
FTX_SUBACCOUNT=

# for OKEx exchange, if you have one
OKEX_API_KEY=
OKEX_API_SECRET=
OKEX_API_PASSPHRASE

# for kucoin exchange, if you have one
KUCOIN_API_KEY=
KUCOIN_API_SECRET=
KUCOIN_API_PASSPHRASE=
KUCOIN_API_KEY_VERSION=2

Prepare your dotenv file .env.local and BBGO yaml config file bbgo.yaml.

To check the available environment variables, please see Environment Variables

The minimal bbgo.yaml could be generated by:

curl -o bbgo.yaml https://raw.githubusercontent.com/c9s/bbgo/main/config/minimal.yaml

To run strategy:

bbgo run

To start bbgo with the frontend dashboard:

bbgo run --enable-webserver

If you want to switch to other dotenv file, you can add an --dotenv option or --config:

bbgo sync --dotenv .env.dev --config config/grid.yaml --session binance

To query transfer history:

bbgo transfer-history --session max --asset USDT --since "2019-01-01"

Advanced Configuration

Testnet (Paper Trading)

Currently only supports binance testnet. To run bbgo in testnet, apply new API keys from Binance Test Network, and set the following env before you start bbgo:

export PAPER_TRADE=1
export DISABLE_MARKET_CACHE=1 # the symbols supported in testnet is far less than the mainnet

Notification

Synchronizing Trading Data

By default, BBGO does not sync your trading data from the exchange sessions, so it's hard to calculate your profit and loss correctly.

By synchronizing trades and orders to the local database, you can earn some benefits like PnL calculations, backtesting and asset calculation.

You can only use one database driver MySQL or SQLite to store your trading data.

Notice: SQLite is not fully supported, we recommend you use MySQL instead of SQLite.

Configure MySQL Database

To use MySQL database for data syncing, first you need to install your mysql server:

# For Ubuntu Linux
sudo apt-get install -y mysql-server

# For newer Ubuntu Linux
sudo apt install -y mysql-server

Or run it in docker

Create your mysql database:

mysql -uroot -e "CREATE DATABASE bbgo CHARSET utf8"

Then put these environment variables in your .env.local file:

DB_DRIVER=mysql
DB_DSN="user:password@tcp(127.0.0.1:3306)/bbgo"

Configure Sqlite3 Database

To use SQLite3 instead of MySQL, simply put these environment variables in your .env.local file:

DB_DRIVER=sqlite3
DB_DSN=bbgo.sqlite3

Synchronizing your own trading data

Once you have your database configured, you can sync your own trading data from the exchange.

See Configure Sync For Private Trading Data

Using Redis to keep persistence between BBGO sessions

To use Redis, first you need to install your Redis server:

# For Ubuntu/Debian Linux
sudo apt-get install -y redis

# For newer Ubuntu/Debian Linux
sudo apt install -y redis

Set the following environment variables in your bbgo.yaml:

persistence:
  redis:
    host: 127.0.0.1  # The IP address or the hostname to your Redis server, 127.0.0.1 if same as BBGO  
    port: 6379  # Port to Redis server, default 6379
    db: 0  # DB number to use. You can set to another DB to avoid conflict if other applications are using Redis too.

Built-in Strategies

Check out the strategy directory strategy for all built-in strategies:

  • pricealert strategy demonstrates how to use the notification system pricealert. See document.
  • xpuremaker strategy demonstrates how to maintain the orderbook and submit maker orders xpuremaker
  • buyandhold strategy demonstrates how to subscribe kline events and submit market order buyandhold
  • bollgrid strategy implements a basic grid strategy with the built-in bollinger indicator bollgrid
  • grid strategy implements the fixed price band grid strategy grid. See document.
  • supertrend strategy uses Supertrend indicator as trend, and DEMA indicator as noise filter supertrend. See document.
  • support strategy uses K-lines with high volume as support support. See document.
  • flashcrash strategy implements a strategy that catches the flashcrash flashcrash

To run these built-in strategies, just modify the config file to make the configuration suitable for you, for example if you want to run buyandhold strategy:

vim config/buyandhold.yaml

# run bbgo with the config
bbgo run --config config/buyandhold.yaml

Back-testing

See Back-testing

Adding New Built-in Strategy

Fork and clone this repository, Create a directory under pkg/strategy/newstrategy, write your strategy at pkg/strategy/newstrategy/strategy.go.

Define a strategy struct:

package newstrategy

import (
	"github.com/c9s/bbgo/pkg/fixedpoint"
)

type Strategy struct {
	Symbol string           `json:"symbol"`
	Param1 int              `json:"param1"`
	Param2 int              `json:"param2"`
	Param3 fixedpoint.Value `json:"param3"`
}

Register your strategy:

package newstrategy

const ID = "newstrategy"

const stateKey = "state-v1"

var log = logrus.WithField("strategy", ID)

func init() {
	bbgo.RegisterStrategy(ID, &Strategy{})
}

Implement the strategy methods:

package newstrategy

func (s *Strategy) Subscribe(session *bbgo.ExchangeSession) {
	session.Subscribe(types.KLineChannel, s.Symbol, types.SubscribeOptions{Interval: "2m"})
}

func (s *Strategy) Run(ctx context.Context, orderExecutor bbgo.OrderExecutor, session *bbgo.ExchangeSession) error {
	// ....
	return nil
}

Edit pkg/cmd/builtin.go, and import the package, like this:

package cmd

// import built-in strategies
import (
	_ "github.com/c9s/bbgo/pkg/strategy/bollgrid"
	_ "github.com/c9s/bbgo/pkg/strategy/buyandhold"
	_ "github.com/c9s/bbgo/pkg/strategy/flashcrash"
	_ "github.com/c9s/bbgo/pkg/strategy/grid"
	_ "github.com/c9s/bbgo/pkg/strategy/pricealert"
	_ "github.com/c9s/bbgo/pkg/strategy/support"
	_ "github.com/c9s/bbgo/pkg/strategy/swing"
	_ "github.com/c9s/bbgo/pkg/strategy/trailingstop"
	_ "github.com/c9s/bbgo/pkg/strategy/xmaker"
	_ "github.com/c9s/bbgo/pkg/strategy/xpuremaker"
)

Write your own private strategy

Create your go package, and initialize the repository with go mod and add bbgo as a dependency:

go mod init
go get github.com/c9s/bbgo@main

Write your own strategy in the strategy file:

vim strategy.go

You can grab the skeleton strategy from https://github.com/c9s/bbgo/blob/main/pkg/strategy/skeleton/strategy.go

Now add your config:

mkdir config
(cd config && curl -o bbgo.yaml https://raw.githubusercontent.com/c9s/bbgo/main/config/minimal.yaml)

Add your strategy package path to the config file config/bbgo.yaml

---
build:
  dir: build
  imports:
  - github.com/your_id/your_swing
  targets:
  - name: swing-amd64-linux
    os: linux
    arch: amd64
  - name: swing-amd64-darwin
    os: darwin
    arch: amd64

Run bbgo run command, bbgo will compile a wrapper binary that imports your strategy:

dotenv -f .env.local -- bbgo run --config config/bbgo.yaml

Or you can build your own wrapper binary via:

bbgo build --config config/bbgo.yaml

See also:

Command Usages

Submitting Orders to a specific exchagne session

bbgo submit-order --session=okex --symbol=OKBUSDT --side=buy --price=10.0 --quantity=1

Listing Open Orders of a specific exchange session

bbgo list-orders open --session=okex --symbol=OKBUSDT
bbgo list-orders open --session=ftx --symbol=FTTUSDT
bbgo list-orders open --session=max --symbol=MAXUSDT
bbgo list-orders open --session=binance --symbol=BNBUSDT

Canceling an open order

# both order id and symbol is required for okex
bbgo cancel-order --session=okex --order-id=318223238325248000 --symbol=OKBUSDT

# for max, you can just give your order id
bbgo cancel-order --session=max --order-id=1234566

Debugging user data stream

bbgo userdatastream --session okex
bbgo userdatastream --session max
bbgo userdatastream --session binance

Dynamic Injection

In order to minimize the strategy code, bbgo supports dynamic dependency injection.

Before executing your strategy, bbgo injects the components into your strategy object if it found the embedded field that is using bbgo component. for example:

type Strategy struct {
*bbgo.Notifiability
}

And then, in your code, you can call the methods of Notifiability.

Supported components (single exchange strategy only for now):

  • *bbgo.Notifiability
  • bbgo.OrderExecutor

If you have Symbol string field in your strategy, your strategy will be detected as a symbol-based strategy, then the following types could be injected automatically:

  • *bbgo.ExchangeSession
  • types.Market

Strategy Execution Phases

  1. Load config from the config file.
  2. Allocate and initialize exchange sessions.
  3. Add exchange sessions to the environment (the data layer).
  4. Use the given environment to initialize the trader object (the logic layer).
  5. The trader initializes the environment and start the exchange connections.
  6. Call strategy.Run() method sequentially.

Exchange API Examples

Please check out the example directory: examples

Initialize MAX API:

key := os.Getenv("MAX_API_KEY")
secret := os.Getenv("MAX_API_SECRET")

maxRest := maxapi.NewRestClient(maxapi.ProductionAPIURL)
maxRest.Auth(key, secret)

Creating user data stream to get the orderbook (depth):

stream := max.NewStream(key, secret)
stream.Subscribe(types.BookChannel, symbol, types.SubscribeOptions{})

streambook := types.NewStreamBook(symbol)
streambook.BindStream(stream)

Deployment

Development

Setting up your local repository

  1. Click the "Fork" button from the GitHub repository.
  2. Clone your forked repository into $GOPATH/github.com/c9s/bbgo.
  3. Change directory into $GOPATH/github.com/c9s/bbgo.
  4. Create a branch and start your development.
  5. Test your changes.
  6. Push your changes to your fork.
  7. Send a pull request.

Testing Desktop App

for webview

make embed && go run -tags web ./cmd/bbgo-webview

for lorca

make embed && go run -tags web ./cmd/bbgo-lorca

FAQ

What's Position?

Looking For A New Strategy?

You can write an article about BBGO in any topic, in 750-1500 words for exchange, and I can implement the strategy for you (depends on the complexity and efforts). If you're interested in, DM me in telegram https://t.me/c123456789s or twitter https://twitter.com/c9s, we can discuss.

Contributing

See Contributing

Financial Contributors

Supporter

  • GitBook

License

AGPL License