ICO/STO Platform Source Code – Module Use Cases

The source code of our ICO/STO platform is based on five different modules. Below we share three use case examples of how these modules interact with each other within the ICO/STO platform.

ICO/STO Token Creation

An ICO/STO holder wants to launch an ICO or STO and therefore create a new (Ethereum) token. This is the sequence behind the scenes:

  1. New tokens are created through smart contracts which are located on the Ethereum blockchain. Each respective smart contract possesses its own address.
  2. The smart contract address is both entered into the wallet config file within the cxWallet and into the cxAdmin module.
  3. The cxAdmin writes the smart contract address into the database cluster. This is necessary to enable the ICO/STO token ultimately to be purchasable. The cxEngine will also later use that information during the token purchase phase to exchange tokens against incoming payments.
  4. Assuming the landing page (cxClient + cxServer) have already been implemented, the ICO/STO token is now ready to be purchased within our software platform. 


The ICO/STO token sale has gone live. An interested investor wants to purchase ICO/STO tokens and signs up. The sign up process is handled as follows:

  1. The investor signs up and creates an account through his browser (cxClient).
  2. The cxClient forwards the account information to the cxServer which subsequently writes the information into the database cluster.
  3. The cxWallet receives the information from the database cluster that a new account has been created and generates a new Ethereum public address.
  4. The cxServer retrieves the public address from the database cluster and subsequently forwards it to the cxClient.
    5. The cxClient displays the public address within the browser and the investor can now send funds.

Purchase ICO/STO Tokens

An investor has already signed up and wants to send funds in order to purchase ICO/STO tokens.

  1. The trader sends BTC or ETH or FIAT money to the addresses or bank information displayed by the cxClient. If the trader pays through cryptocurrency, the funds will directly arrive in the cxWallet which is synced up with the respective blockchain. If the trader pays through FIAT currency, the funds will be credited in the cxAdmin module.
  2. Predefined token exchange rate for each payment method are set up in the cxAdmin in advance. The cxAdmin writes the exchange rate information into the database cluster. When the funds arrive, the cxEngine will retrieve the token exchange rates from the database cluster and execute the exchange. The cxEngine also writes the transaction into the database cluster.
  3. The cxServer retrieves the token information from the database cluster and forwards it to the cxClient.
  4. The cxClient displays the amount of purchased tokens within the trader’s user account.