consensus-safety-unverified-across-optimization-variants

Status: IN

Both consensus mechanisms represent inverse optimizations of Multi-Paxos (Raft centralizes proposal authority in a leader, TOB decentralizes it to allow any node to propose), but neither variant's safety has been validated under the asynchronous conditions it is designed for — all protocol tests use deterministic synchronous delivery with no real network I/O, message loss, or reordering.

Justifications

Two inverse Paxos optimizations share the same verification gap — both are designed for asynchronous networks but tested exclusively under synchronous simulation

Depends on (SL): consensus-architectures-are-inverse-optimizations, protocol-safety-validated-only-under-synchronous-model

Depended on by

JSON