Gains Network bot

Setup

npm i
cp config.dev.json config.json
# or cp config.prod.json config.json
echo "my wallet priv key" > wallet.txt

Test

npm test

Run

src/app.ts
# point the browser at localhost:85/dashboard

CLI

Manually test commands

# infrastructure
src/cli.ts showKeys                            # display used private and public keys
src/cli.ts publishNotification "test message"

# gTrade specific
src/cli.ts gTradeStats
src/cli.ts issueTrade --pair btc --price 23390 --size 100 --leverage 20 --stopLoss 0 --takeProfit 23500 --slippage 0.01             # buy:  price > mark
src/cli.ts issueTrade --pair btc --price 23350 --size 100 --leverage 20 --stopLoss 23500 --takeProfit 0 --slippage 0.01 --dir sell  # sell: price < mark
src/cli.ts issueTrade --pair eth --price 1641 --size 100 --leverage 20 --stopLoss 0 --takeProfit 1650 --slippage 0.01
src/cli.ts issueMarketTrade --pair eth --size 100 --leverage 20 --stopLoss 0 --takeProfit 1650 --slippage 0.01
src/cli.ts getOpenTrades --pair eth
src/cli.ts closeTrade --pair eth --orderIndex 0
src/cli.ts closeAllTrades

EC2 deployment

Following is my setup, guided by desire not to be limited by network bandwidth (suits websockets). Note: following assumes:

• deploy on non-burstable instance with decent network bandwidth, to avoid issues with closed websockets
  • https://aws.amazon.com/ec2/pricing/on-demand/
  • https://www.densify.com/resources/ec2-instance-types/
• 3.80.119.255 is your ubuntu ec2 instance, with port 80 open
• gbot.pem aws keypair has created
• aws-deployment priv key has been setup in github
• <my-pub-key> = your wallet priv key, with appropriate funds for given chain

scp -i ~/.ssh/gbot.pem ~/.ssh/aws-deployment [email protected]:~/.ssh
ssh -i ~/.ssh/gbot.pem [email protected]
# inside the ec2 terminal...
# ensure we can clone from github
chmod 400 ~/.ssh/aws-deployment
vi ~/.ssh/config
"
Host github.com
 HostName github.com
 IdentityFile ~/.ssh/aws-deployment
"
chmod 600 ~/.ssh/config
# install deps
sudo apt update
sudo apt install nodejs npm curl -y
curl https://raw.githubusercontent.com/creationix/nvm/master/install.sh | bash
source ~/.bashrc
nvm install 16.6.0
sudo setcap cap_net_bind_service=+ep `which node`  # do if webServerPort != 80
# install repo
mkdir src && cd src
git clone [email protected]:konrads/gbot.git
cd gbot
npm i
cp config.dev.json config.json  # fix up monitoredTrader, etc!
echo "<my-pub-key>" > wallet.txt
node_modules/.bin/ts-node src/cli.ts
# try it out
node_modules/.bin/ts-node src/cli.ts showKeys
node_modules/.bin/ts-node src/cli.ts gTradeStats
# start the server
npm run pm2-install
npm run build
npm run pm2-start
pm2 logs
# open http://3.80.119.255/dashboard for dashboard

Operation details

Adhere to following guidelines:

• gbot operates on trades index 0 - expect it to be closed if opened manually. Ideally - do not open trades manually at all.
• gbot triggers on periodic schedule and certain WS events. Note, to keep the logic simple, WS events cause the same update as per schedule
• should WS connection drop off and fail to recover - gbot will keep ticking on periodic schedules only
• on restart following rules are abided by:
  • if both positions exist in same dir - noop
  • if my position exists but monitored doesn't - mine is closed (on trade 0)
  • if both positions exist, but in opposite dirs - mine is cancelled (and subsequently re-opened to rebalance)
  • if monitored position exists and mine doesn't - I don't know when monitored was opened - will wait for it to re-open