Network Topology

We present the following proposal for LACChain network configuration using EOSIO nodes.

Design principles#

  • Trustless, the correct and optimal functioning of the network, should not be based on trust between the entities that make up the network.

  • Horizontal scalability, to be able to scale the network infrastructure to satisfy the growth of its demand in a simple way.

  • Read and write permissions Use a permission system to grant permissions to write (push tx) or read (consumption of APIs or blocks by P2P).

  • MVP This topology can be the base of an MVP without modifications to the native EOSIO network protocol.

Proposed Topology#

Topologia de Red LatamLink
  • Layer 1 (Core) Validator and interconnecting p2p node network.

    • Layer 2 (Bridge) p2p distribution network among p2p validators and boot nodes.

      • Layer 3 (Satellite) Writer and observer nodes consumption layer.

LatamLink Topology

Layer 1 - Core Network#

The core network is composed of the blocks producers who have been added to the consensus protocol group. The final computational power source is derived from the network core.

Validator Nodes#

In an EOSIO network these nodes are called block producers, they are in charge of generating blocks every 500ms. These nodes should only be connected to other nodes managed by the same entity.

Validator p2p for other Validators#

P2P node configured as part of the internal network of the validators.

Layer 2 - Bridge#

Validator p2p out#

Node configured to only broadcast blocks over p2p connections, allowed p2p out observers connect to this node.

Validator p2p bidir#

Node configured to accept p2p transactions from allowed nodes and send it to the validator.

Boot Nodes#

Boot p2p out#

Node configured to accept blocks from p2p validators and only forward them to p2p and api observers, does not accept transactions.

Boot p2p bidir#

P2p node configured to update writer nodes with new blocks and in turn accept txs to send to validators

Layer 3 - Satellite#

Writer Nodes#

Writer p2p#

Accepts transactions through p2p and sends them to layer 1 through a boot-p2p-bidir.

for example: A wallet manages its own API and connects to the network through a p2p writer.

Writer API#

Accept http transaction push requests and send them to layer 1 through a boot-p2p-bidir

Observer Nodes#

Observer nodes p2p#

An observer node p2p is a node that is consuming layer 1 information through a boot-p2p-out, it can only read the state of the blockchain.

Observer nodes API#

Node that allows requesting information from the blockchain through an http request, the use of dfuse is recommended.


Node Discovery#

Node Discovery Cycle

  1. The entity configures a new node.
  2. The entity registers a new node with the committee including information such as node type (observer-api, writer-p2p, boot-p2p-bidir, etc.) along with its public key for peering.
  3. The committee updates the node table in the smart contract with the node information to add the above data.
  4. Nodes already in the network must update their list of allowed pairs with the new added node.
  5. The new node confirms that it is connected to the network.

Nodes Groups and Sub-Groups#

Writer NodesBoot NodesObserver NodesValidator Nodes
Group 1....nGroup 1....nGroup 1...nActive and Stand-By
groups of up to 40 nodesgroups of up to 40 nodesgroups of up to 10 nodesactive defined in schedule

Boot and validator nodes that do not meet the required configuration can be removed by the permissioning committee.

Node Communication#

For more information on how communication works between nodes in EOSIO networks, check out the Developers Portal


The cycle of a transaction is as follows:

  1. A client sends a signed transaction by https or by p2p to a writer node, either API or p2p.

  2. The writer verifies the transaction.

  3. The writer broadcastes the transaction to the boot-p2p-bidir nodes.

  4. The boot-p2p-bidir, broadcastes the transaction to the layer 1 (core).

  5. The validator that is in schedule verifies the transaction and executes it.

  6. The validator broadcastes the new block to the layer 1 and the layer 2.

  7. Layer 2 Boot verifis the new block and broadcastes it to the layer 3.

Routes optimizations / Connections#

The goal is to manage the network topology in a dynamic way using Smart Contracts.

In the current BESU LACChain topology, the "boot" nodes can be connected to all nodes in the network (boot, validator and writer). At present, all "boot" nodes are connected to all nodes. This is not scalable and efficient. Alongside, the nodes are not restricted by the network to connect only to correspondent nodes (in other words, a writer with the boot, or validator with validator and boot), nor do they have the information about what kind of node each of them is. We need proportionalities to that information out of the chain.

Cloud Infrastructure#

LACChain is interested in using autonomous deployments on several clouds using tools like terraform. The goals related to the cloud are the following:

  • Take advantage of the tools in the cloud to improve the Layerbilities in the network.
  • Explore the use of the key vaults in the cloud.
  • Work with partners to open up cloud services in LACChain on a SAAS basis.
Last updated on