desynchronization due to Orion

Problem

It has been observed that when the limit gas is set to execute a private transaction, the desynchronization failure also occurs (Tested in version 1.4.0 and besu 1.3.6).

The problem was detected in nodes that had orion and besu running

It was identified that the bootnodes that had orion and besu running in the same environment caused other nodes on the network that also had orion and besu running to get out of sync.
Nodes that only ran besu were not affected.

workaround:

In case Orion is not necessary

Disable the orion service in the bootnodes configuration and restart the "pantheon" service a) Go to the file /root/lacchain/config.toml and comment the following lines:

privacy-enabled = true
privacy-url = "http://127.0.0.1:4444"
privacy-public-key-file = "/root/lacchain/orion/keystore/nodeKey.pub"

b) Then restart the pantheon service: systemctl restart pantheon

In case Orion is necessary

a) Go to the file /root/lacchain/config.toml and comment the following lines:

#privacy-enabled = true
#privacy-url = "http://127.0.0.1:4444"
#privacy-public-key-file = "/root/lacchain/orion/keystore/nodeKey.pub"`

b) Then restart the pantheon service: systemctl restart pantheon c) Wait for the besu node to finish synchronizing d) Once the node is synchronized, return to the /root/lacchain/config.toml file and uncomment the lines that were commented in step "a" e) Step followed restart the pantheon service systemctl restart pantheon Verify that the node is already properly synchronized.

lacchain / besu-pro-testnet