“…Apart from quorum systems, another popular mechanism for consistency is the class of primary-based protocols, where each data block x has an associated primary, which is responsible for coordinating operations on x . For example, Reference [ 9 ] proposed an update model assuming a primary which serializes the update executions, and, similarly, in Reference [ 10 ], the node storing a data block enforces serialized writes, while updates are disseminated in a best effort manner to the redundant blocks, and stale reads are possible, i.e., there is no consistency guarantee.…”