Consensus not reached during tx validation

[ghost]

Describe the problem you discovered

Describe the solution you'd like

No response

---

Epic: #306

[ghost]

Hey team! Please add your planning poker estimate with ZenHub @apoorv-2204 @imnik11 @Neylix @prix-uniris

[Neylix]

I think we can reproduce this error by running the benchmark with mix dev.lbench

[Neylix]

This error is caused by a problem of latency between nodes when there is several transactions including the same transaction chain in the same time :

In my opinion this error is "normal" and cannot be resolved as it is the result of decentralized system and atomic commitment

[Neylix]

For network transaction we can see in log that there is a timestamp inconsistencie causing the consensus not reached :

This insconsistencie should be fixed by dd0d0bc