Consensus Protocol

LACChain Networks orchestrated by LACNet use IBFT2.0 consensus protocol for the validation of transactions and the generation of new blocks. This is a Proof of Authority protocol that eliminates high carbon emissions and energy consumptions involved in other popular consensus protocols such as proof of work. In addition to IBFT2.0, all validator nodes in LACChain Mainnets are contractually committed with LACNet to follow certain rules that guarantee the resilience of the network without crypto incentives -(for more info check the Adscription Agreement for Validator nodes)[https://github.com/LACNetNetworks/besu-networks/blob/master/mainnet/adcription_contracts/Adscription_contract_validator_%26_boot_ENG.pdf]All of these together guarantees that: 

  • Blocks need to be signed by 2/3+1 validator nodes to be valid.
  • Finality is instantaneous.
  • History cannot be rewritten without noticing.
  • Only nodes permissioned as validators can propose and vote new blocks.
  • Validator nodes have a time slot to propose a new block. When time expires, the validator is replaced by another available validator.
  • Validator nodes must accept any valid transaction and report any invalid transaction.
  • Validator nodes must be resilient.

In LACChain Networks, validators do not compete to produce blocks, but rather take turns. As such, finality is instantaneous and new blocks are always appended at the end, never rewriting the history. If there were an attack by a majority of validator nodes trying to rewrite the history, any honest node in the network (including validators and not validators) could simply refuse to accept it as soon as the honest node finds that the hash of the block previous to the last proposed block does not match with the hash in the latest version of the chain the honest nodes have. Regarding governance matters, every node operator (including writers, boots, and validators) participates in the governance working groups that propose and vote for updates in the network.

LACNet has also established a fixed number of validator nodes active at the same time and a pool of inactive nodes that are interchanged or rotated according to performance and decentralization. To know more, check [Validator Rotation Protocol].

Copyright 2022 ┬ę All rights Reserved. Designed by LACNet