System Architecture

Today, public blockchains simply have a flat layer of ledger server mesh network under the API server.

The Fireal Mobile Blockchain has more network layer(s) below the ledger server mesh network. Mining devices may be linked to any one of the ledger servers of Fireal directly, or via another layer of trusted node mesh network. Mesh networks between mining devices and trusted nodes may also exist. Hence, the network architecture may vary from one to multiple layers of mesh networks.

It should also be noted that due to the simplicity of mining devices, MMI for transaction processing and direct association with wallet are generally not being built within mining devices. Instead, they are normally linked to user devices such as cell phones, tablets, or computers for communicating with the Fireal ecosystem.

Similar to public blockchains today, there is an API server on top of the ledger server mesh network to link different categories of users together, as well as to wallets and exchanges. A big data bank can be built into the SPI servers to collect data, and carry out analysis to generate useful information such as consumer behavior, best-selling products, product reliability and life, service response time, etc. Such information has the potential to become an income-generating source for the Fireal Mobile Blockchain.

The following diagram illustrates possible system architecture. It should be noted that the mining assignment block shown is within the API server. It is also possible that the mining assignment is within the ledger server mesh network controller.

Blockchain ecosystems are normally more vulnerable to 51% takeover attacks when the number of ledger server nodes is small. As number of ledger servers grows, Fireal becomes more and more robust against such attacks. Therefore, special care should be taken during the initial launch of new blockchains. For Fireal, the whole system is controlled collaboration with strategic partners serving also as owners of trusted nodes or even trusted ledger servers. This makes the Fireal Mobile Chain ecosystem not an open system at the beginning to trade for better system security.

Transaction Execution

Transaction requests can be raised by any device on the Fireal Mobile Chain ecosystem having a valid wallet for paying or receiving Fireal coin. A transaction request comprises the transaction information in terms of the nature of the transaction such as purchase or selling of goods and services, involved parties, delivery schedule, warranty terms, transaction amount involved, etc., together with a transaction HASH, and other optional data such as signature, day and time stamp, etc.

Upon receiving of a new transaction request, the Fireal Mobile Chain ecosystem assigns the job of computing the new transaction HASH to one or more mining devices. Trusted node(s) or ledger server(s) then validates new transaction HASH generated by mining device(s).

Transaction request once verified and validated, the newly generated transaction HASH will be appended to the transaction request to form a new transaction block. The new transaction is then appended to the last transaction block. The transaction amount involved will then be transferred between corresponding wallets.

Last updated