Subcubic Coin Tossing in Asynchrony without Setup
Abstract
We consider an asynchronous network of $n$ parties connected to each other via secure channels, up to $t$ of which are byzantine. We study common coin tossing, a task where the parties try to agree on an unpredictable random value, with some chance of failure due to the byzantine parties' influence. Coin tossing is a well known and often studied task due to its use in byzantine agreement. In this work, we present an adaptively secure committee-based method to roughly speaking turn strong but c...
Description / Details
We consider an asynchronous network of parties connected to each other via secure channels, up to of which are byzantine. We study common coin tossing, a task where the parties try to agree on an unpredictable random value, with some chance of failure due to the byzantine parties' influence. Coin tossing is a well known and often studied task due to its use in byzantine agreement. In this work, we present an adaptively secure committee-based method to roughly speaking turn strong but costly common coins into cheaper but lower-quality ones. For all and , we show how to use a strong (very rarely failing) coin that costs bits of communication to get a cheaper coin that costs bits of communication. This latter coin tolerates fewer byzantine parties than the former, and it fails with an arbitrarily small constant probability. For any , our method allows us to get a perfectly secure binary coin that tolerates faults with messages of size , as well as a setup-free cryptographically secure binary coin that tolerates faults with bits of communication (where is a cryptographic security paramater). These coins both have latency. They are to our knowledge the first setup-free coins that cost bits of communication but still succeed with at least constant probability against adaptive byzantine faults. As such, they for the first time enable setup-free (and even perfectly secure) asynchronous byzantine agreement with communication against adaptive byzantine faults.
Source: arXiv:2603.02071v1 - http://arxiv.org/abs/2603.02071v1 PDF: https://arxiv.org/pdf/2603.02071v1 Original Link: http://arxiv.org/abs/2603.02071v1
Please sign in to join the discussion.
No comments yet. Be the first to share your thoughts!
Mar 4, 2026
Computer Science
Cybersecurity
0