It’s not really that complicated

Those of you who care about EOS must have seen the blueprint below. Yes, it is only a blueprint at present, and given BM’s urination, it must have been changed beyond recognition in mind (for example, eOSD in the picture has been renamed long ago). Therefore, this chart can only be used as a reference for the future development of EOS, which is far from being so complex and complete.

Before looking at the architecture of the system let’s take a look at the main components of the current EOS system:

  • Nodeos: The core processes of the EOS system, known as “nodes”. Plugins can be configured at runtime:

    • producer_pluginWitness plugin: Witnesses must use this plugin, not normal nodes.
    • wallet_plugin(Wallet plug-in) : Use this plug-in to dispense with the Keosd wallet tool.
    • wallet_api_plugin(Wallet interface plug-in) : Provides an interface for the wallet plug-in.
    • chain_api_plugin(Block link interface plug-in) : provides block chain data interface.
    • http_plugin(HTTP plug-in) : provides HTTP interfaces.
    • account_history_api_plugin(Account history interface) : provides an interface for querying account history.

  • Cleos: A local command-line tool that interacts with human users on the command line and communicates with the REST interface of the node (NodeOS). It is a bridge between the user or developer and the node process.

  • Keosd: local wallet tool. A process that stores wallets for non-node users and can manage and encrypt multiple wallets with private keys.

Local single-node test system

In the case of a single node, only NodeOS and CLEos are required. Keosd is not required because the wallet plug-in of the node is used to manage the private key. This single node is the entirety of the blockchain, where all data is stored in a single node. So “BlockChian” in the image below is just a concept, and all the block generation is done in NodeOS.

Local multi-node test system

The local multi-node test system is more like a real blockchain network, but runs on the same computer. Keosd manages the private key, CLEOS connects users and nodes, and NodeOS generates blocks as nodes.

Public test network

The architecture of the PUBLIC Beta network is essentially the same as the soon-to-launch EOS mainnet, minus 100 backup nodes, with 21 primary nodes. Users connect to NodeOS via CLEOS, which in turn connects to the blockchain network (other NodeOs).

EOS primary network

If there are no major changes in the near future, the upcoming EOS primary network will be a 21 primary + 100 standby architecture.

(Image from or modified from EOS official)

Related articles and videos recommended

[Xu Xiaodi] EOS block data structure

Yuan Yuan Institute brings together a large number of blockchain masters to create high-quality blockchain technology courses. There are high quality free public courses on all major platforms for a long time, welcome to sign up and watch. Open course address: ke.qq.com/course/3451…