An efficient validated asynchronous byzantine agreement protocol using committee
Nasit S Sony
TL;DR
This work addresses asynchronous Byzantine agreement under adversarial faults by introducing a validated asynchronous BA (VABA) that uses a stochastic committee to reduce broadcasting and computation. The main method combines a committee-selection protocol, prioritized four-step provable-broadcast (P-PB) invocations, leader-election, and a mapping of the elected leader to a committee member, yielding Efficient-VABA with strong safety and liveness guarantees. The key contributions are the committee-based reduction in message complexity, the Propose-Suggest and mapping mechanisms to ensure progress from a small broadcast set, and formal security and efficiency analyses that show termination and optimal message/communication costs. The approach offers practical benefits for scalable fault-tolerant consensus in asynchronous networks, with potential extensions to further reduce remaining $n\!-to!-n$ communications and enhance performance.
Abstract
We present a Byzantine agreement protocol to address the inefficiencies inherent in multi-valued Byzantine agreement protocols, i.e., a version of the Byzantine agreement protocol where every party broadcasts its request, and at the end of the protocol, every party agrees on one of the party's requests. The protocol we present is a validated asynchronous Byzantine agreement protocol, i.e., a party's request must be validated by some external validity property before it is proposed for agreement. Differently from most of the MVBA protocols, we allow only a subset of total parties to broadcast their requests instead of all, and we make the subset selection stochastic each time the parties choose to broadcast a new set of requests. Then, at the time of the agreement, we choose a party from the selected subset, and the parties reach an agreement on the selected party's broadcast. Extensive theoretical analysis shows that this approach can produce efficient output regarding messages and computation overhead, but the protocol is time-consuming.
