论文标题
口腔拜占庭可靠广播[扩展版本]
Oracular Byzantine Reliable Broadcast [Extended Version]
论文作者
论文摘要
拜占庭可靠广播(BRB)是一种基本分布式计算原始的,其应用程序从通知到异步支付系统不等。出于实际考虑,我们研究了客户服务器拜占庭可靠广播(CSB),这是BRB的多拍变体,其界面是在广播客户端和交付服务器之间分配的。我们提出草案,这是CSB的最佳弹性实施。像大多数BRB的实施一样,草案在异步环境中保证了耐受性和安全性。但是,在良好的条件下,草稿实现了无与伦比的效率。在同步的时刻,不受拜占庭不当行为,并且在许多广播客户的限制下,草稿服务器以$ 0 $ $ 0 $的签名验证的成本和$ \ log_2(c) + b $ bits交换了$ b $ c $ c $ c $ c $ cults of System normes norme normes normes norme normes normes number systems of System normes number norme norme norme norme norme norme norme norme norme normes cunters。这是传达有效载荷所需的最小数量的信息理论(假设它是压缩的$ b $位)以及其发件人的标识符($ \ log_2(c)$ bits,是枚举任何$ c $ elements的必要条件,并且如果广泛的频率是均匀或不知名的,则是必要的。这两个成就具有深远的实践意义。现实世界中的BRB实现通常是通过昂贵的签名验证或通过交流开销来瓶颈的。相反,对于草稿,网络是限制:服务器可以像从可靠的甲骨文中接收到它们一样快地传递有效载荷。
Byzantine Reliable Broadcast (BRB) is a fundamental distributed computing primitive, with applications ranging from notifications to asynchronous payment systems. Motivated by practical consideration, we study Client-Server Byzantine Reliable Broadcast (CSB), a multi-shot variant of BRB whose interface is split between broadcasting clients and delivering servers. We present Draft, an optimally resilient implementation of CSB. Like most implementations of BRB, Draft guarantees both liveness and safety in an asynchronous environment. Under good conditions, however, Draft achieves unparalleled efficiency. In a moment of synchrony, free from Byzantine misbehaviour, and at the limit of infinitely many broadcasting clients, a Draft server delivers a $b$-bits payload at an asymptotic amortized cost of $0$ signature verifications, and $\log_2(c) + b$ bits exchanged, where $c$ is the number of clients in the system. This is the information-theoretical minimum number of bits required to convey the payload ($b$ bits, assuming it is compressed), along with an identifier for its sender ($\log_2(c)$ bits, necessary to enumerate any set of $c$ elements, and optimal if broadcasting frequencies are uniform or unknown). These two achievements have profound practical implications. Real-world BRB implementations are often bottlenecked either by expensive signature verifications, or by communication overhead. For Draft, instead, the network is the limit: a server can deliver payloads as quickly as it would receive them from an infallible oracle.