SmithBot

A user interface that enables the customer care staff to quickly manage and track client subscriptions was required. We had to get acquainted with a variety of crypto currency trading principles. Coped with a variety of exchanges that were not API implementations. We had to make orders for users at the same time. We worked creatively with crypto exchange APIs to avoid blocking our server by IP address or even banning user keys. Logs kept in AWS cloudwatch made it impossible for clients to examine the system; they needed to be streamed someplace and made more understandable to customers.

We applied multiple tenancy structure to database, server and client code AWS-based automated deployment -Integrated with other services to automate the setup procedure -Each user's trade signal is processed in parallel. Caching essential exchange data so that we did not have to contact the exchange too often Configured a nginx gateway to handle the customer's server's fallback. Streamed required logs to elastic-search for customer review

Key Features: 1. Bot Server (existing): - Runs a variety of AI trading bot instances: - Each bot tracks the market of a trade pair and decides the optimal action - Each bot generates trade signals (‘buy’ or ‘sell’) - REST API to client web application - Various visualization functions to get information on trades, bots and their performance - Sends signals to client application when trades occur