Source Code Exchange Software
The inherent flexibility of our software allows us to build various applications on top of the existing code and modify everything to your liking.
Source Code Structure
Our source code is structured into five different modules: cxClient, cxServer, cxWallet, cxEngine and cxAdmin. Each module operates on its own, but all modules interact with each other.
The five modules are distributed across three servers:
Server 1: cxClient + cxServer: Responsible for everything on the enduser (trader) side
Server 2: cxWallet: Responsible for storing all cryptocurrency funds
Server 3: cxEngine + cxAdmin: Responsible for matching trades and administrative functions
Except for the cxClient, all modules save their data on a decentralized database cluster. The database cluster is spread across all three servers. If one or two servers go down, the complete database can always be recovered as long as one server remains live. In other words, all three servers share the same database information. However, depending on the module, each server possesses different write permissions.
Modules
cxClient
The cxClient is the frontend user interface of our exchange software. It is responsible for rendering everything that investors (endusers) see in their browser. It allows users to sign up, log in, place buy / sell orders, view their trade history / purchased tokens, view balances, deposit/withdraw digital assets, upload KYC documents and view charts. Changes to the design and layout all take place in the cxClient. The cxClient also features Google Authenticator and email-based two-factor authentication as security measures on the frontend side.
cxServer
The cxServer processes everything that comes from the cxClient side. It retrieves the user input from the cxClient and then writes it into the database cluster. Put differently, the cxServer is the API between the cxClient and database cluster. If an investor signs up, for example, the cxClient forwards the input information to the cxServer which subsequently writes the information into the database cluster.
cxWallet
The cxWallet is the multicurrency wallet module which stores all cryptocurrency funds. If an exchange offers three tradeable cryptocurrencies (e.g. Bitcoin, Ethereum and Litecoin), the cxWallet will contain three separate wallets. Each wallet will be synced up with each cryptocurrency’s respective blockchain.
cxEngine
The cxEngine module matches trades on the exchange. Moreover, the cxEngine is also responsible for providing the data in the order book, reviewing and executing transactions, and calculating account balances.
cxAdmin
The cxAdmin module provides the administrative interface for the exchange operator. It is the equivalent of a business intelligence and management software. Within the interface, admins can approve deposit/withdrawal requests, manage KYC requirements, create and answer support tickets, modify trading fees, and manage cold storage functionalities. Administrators can only access the cxAdmin module through a VPN connection to prevent any unauthorized logins.
Exchange Software Modules Use cases
The source code in our software modules is modified appropriately to either work in an exchange or ICO/STO environment. To better understand how the modules interact with each other in our exchange software, let’s explore three exchange-specific use cases:
1) What happens behind a trade?
2) What happens behind a deposit?
3) What happens behind a withdrawal?
ICO/STO Platform Modules Use Cases
Essentially, an ICO/STO is not that different from an exchange. For instance, if an investor buys tokens, an exchange takes place. The investor (usually) exchanges bitcoin or ethereum for ICO/STO tokens. Hence the fundamental source code in an exchange software and ICO/STO platform is quite similar. We will explore 3 ICO/STO use cases and how our software modules handle them:
1) How is an ICO/STO token created?
2) What happens behind an ICO/STO token purchase?
3) What happens behind a smart contract?
