The module local-dev provides the ICOnatorLocalDevApplication class with a main() that is able to run all the ICOnator backend applications at once, without SMTP Server or SMTP Relay: for example, Postfix, or services like Amazon SES and Google Gmail.Ethereum Full Node: for example, Parity or Geth - or providers such as Infura or QuikNode.Message Broker Server, AMQP 0.9.1 protocol: for example, RabbitMQ.SQL Server: for example, PostgreSQL or MariaDB.
![blank iconator blank iconator](https://sites.google.com/site/branchestoheaven/_/rsrc/1472783802681/rainbow-text---photoshop-elements/yuh.png)
The ICOnator applications require these services: Monitor: Responsible to monitor payment transactions to pay-in addresses, convert amounts, and listen to blockchain-related events.Įach of them has specific functionalities that are documented in the respective sub-modules.Rates: Responsible to constantly fetch rates, which would be consumed by other applications.Email: Responsible to listen to events and send emails to investors.
![blank iconator blank iconator](https://sites.google.com/site/branchestoheaven/rainbow-text---photoshop-elements/lyr.png)
Such APIs provide functionalities as, e.g., registering new investors and distributing pay-in addresses
![blank iconator blank iconator](https://sites.google.com/site/branchestoheaven/_/rsrc/1472783801447/rainbow-text---photoshop-elements/lyr.png)
ICOnator provides its backend applications as:
Blank iconator how to#
The repository ICOnator-docker-compose provides the easiest andįastest way to experiment, see how it works, and check how to run ICOnator backend applications. The ICOnator is an easy, secure, configurable, and scalable open source ICO engine - driven by the community.īasically, the concept of an ICO engine is to provide a generic core and, on top of that, ICO platforms can build specific features and tailor requirements which certainly differ depending on ICO's business requirements. ICOnator has the goal to support the worldwide tokenization of assets.