How 3s3s/opentrade works
Project Type and Purpose
• OpenTrade is a full-stack, microservices-style cryptocurrency exchange platform written in Node.js.
• It consists of three cooperating Node.js services:
• databaseServer – a custom data-access API for all persistent data (users, orders, trades, balances)
• accountsserver – the authentication/account-management service
• server – the main HTTP/HTTPS web server delivering UI pages, JSON API, WebSockets, admin console, and RPC logic for trading
• It also integrates with external cryptocurrency daemon processes (e.g. bitcoind/litecoind clones) via JSON-RPC, an SMTP mailer, and Google reCAPTCHA.
File‐Structure Analysis
• Top-level directories:
• databaseServer/: data-service microservice
• accountsserver/: authentication microservice
• server/: main web microservice (modules/, views/, static pages)
• static_pages/: pure front-end HTML/CSS/JS (used for offline test, chart page, etc.)
• ssl_certificates/: TLS keys for HTTPS
• Configuration files: private_constants.js (API keys, SSL paths), constants.js (exchange parameters), chart.html (front-end config), package.json, databaseServer/utils, server/database.js
README Insights
• Deploys three Node services via forever
• Uses NVM/Node 12.x
• Requires external coin-daemon processes on RPC ports
• First user becomes admin, coins added via admin UI
• Captures both static and server-rendered front-end (EJS templates + client JS)