Skip to content

Latest commit

 

History

History
135 lines (77 loc) · 4.8 KB

README.md

File metadata and controls

135 lines (77 loc) · 4.8 KB
Raw

Hummingbot

Hummingbot Gateway

Hummingbot Gateway is a REST API that exposes connections to various blockchains (wallet, node & chain interaction) and decentralized exchanges (pricing, trading & liquidity provision). It is written in Typescript and takes advantage of existing blockchain and DEX SDKs. The advantage of using gateway is it provideds a programming language agnostic approach to interacting with blockchains and DEXs.

Gateway may be used alongside the main Hummingbot client to enable trading on DEXs, or as a standalone module by external developers.

Installation via Docker

If you are installing Gateway alongside Hummingbot, check out the Deploy Examples repository that helps you deploy various types of Hummingbot and Gateway configurations. For most new users, we recommend following the Hummingbot Gateway Compose deployment.

The repo also contains Bash Scripts that help you install the Gateway Docker image on a standalone basis.

Installation from source

Dependencies:

  • NodeJS (16.0.0 or higher)
  • Yarn: run npm install -g yarn after installing NodeJS
# Install dependencies
yarn

# Complile Typescript into JS
$ yarn build

# Run Gateway setup script, which helps you set configs and CERTS_PATH
$ chmod a+x gateway-setup.sh
$ ./gateway-setup.sh

# Start the Gateway server using PASSPHRASE
$ yarn start --passphrase=<PASSPHRASE>

Build Docker image

To build the gateway docker image locally execute the below make command:

make docker

Pass the ${TAG} environmental variable to add a tag to the docker image. For example, the below command will create the hummingbot/gateway:dev image.

TAG=dev make docker

Documentation

See the official Gateway docs.

The API is documented using Swagger. When Gateway is started, it also generates Swagger API docs at: https://localhost:8080

Contributing

There are a number of ways to contribute to gateway.

Configuration

  • If you want to turn off https, set unsafeDevModeWithHTTP to true in conf/server.yml.

  • If you want Gateway to log to standard out, set logToStdOut to true in conf/server.yml.

  • The format of configuration files are dictated by src/services/config-manager-v2.ts and the corresponding schema files in src/services/schema.

  • If you want to turn off https, set unsafeDevModeWithHTTP to true in conf/server.yml.

  • For each supported chain, token lists that translate address to symbols for each chain are stored in /conf/lists. You can add tokens here to make them available to Gateway.

Architecture

Here are some files we recommend you look at in order to get familiar with the Gateway codebase:

Testing

For a pull request merged into the codebase, it has to pass unit test coverage requirements. Take a look at Workflow for more details.

Unit tests

Read this document for more details about how to write unit test in gateway: How we write unit tests for gateway.

Run all unit tests.

yarn test:unit

Run an individual test folder or file

yarn jest test/<folder>/<file>

Manual tests

We have found it is useful to test individual endpoints with curl commands. We have a collection of prepared curl calls. POST bodies are stored in JSON files. Take a look at the curl calls for gateway. Note that some environment variables are expected.

Linting

This repo uses eslint and prettier. When you run git commit it will trigger the pre-commit hook. This will run eslint on the src and test directories.

You can lint before committing with:

yarn run lint

You can run the prettifier before committing with:

yarn run prettier