Reliability

LX operates Via its own Zero Knowledge Subnet on the Lux Network. As shown in Figure 1, at any given time a system node is designated as Leader to generate a Proof of History sequence, providing the network global read consistency and a verifiable passage of time. The Leader sequences user messages and orders them such that they can be efficiently processed by other nodes in the system, maximizing throughput.

It executes the transactions on the current state that is stored in RAM and publishes the transactions and a signature of the final state to the replication nodes called Verifiers. Verifiers execute the same transactions on their copies of the state, and publish their computed signatures of the state as confirmations.

The published confirmations serve as votes for the consensus algorithm. Figure 1: Transaction flow throughout the network. In a non-partitioned state, at any given time, there is one Leader in the network. Each Verifier node has the same hardware capabilities as a Leader and can be elected as a Leader, this is done through PoS based elections. In terms of CAP theorem, Consistency is almost always picked over Availability in an event of a Partition.