Lower Bounds for Leader Election and Collective Coin Flipping, Revisited

We study the tasks of collective coin flipping and leader election in the full-information model.We prove new lower bounds for coin flipping protocols, implying lower bounds for leader election protocols. We show that any -round coin flipping protocol, where each of players sends 1 bit per round, can be biased by bad players. For all this strengthens previous lower bounds [RSZ, SICOMP 2002], which ruled out protocols resilient to adversaries controlling players. Consequently, we establish that any protocol tolerating a linear fraction of corrupt players, with only 1 bit per round, must run for at least rounds, improving on the prior best lower bound of . This lower bound matches the number of rounds, , taken by the current best coin flipping protocols from [RZ, JCSS 2001], [F, FOCS 1999] that can handle a linear sized coalition of bad players, but with players sending unlimited bits per round. We also derive lower bounds for protocols allowing multi-bit messages per round. Our results show that the protocols from [RZ, JCSS 2001], [F, FOCS 1999] that handle a linear number of corrupt players are almost optimal in terms of round complexity and communication per player in a round.A key technical ingredient in proving our lower bounds is a new result regarding biasing most functions from a family of functions using a common set of bad players and a small specialized set of bad players specific to each function that is biased.We give improved constant-round coin flipping protocols in the setting that each player can send 1 bit per round. For two rounds, our protocol can handle sized coalition of bad players; better than the best one-round protocol by [AL, Combinatorica 1993] in this setting.
View on arXiv@article{chattopadhyay2025_2504.01856, title={ Lower Bounds for Leader Election and Collective Coin Flipping, Revisited }, author={ Eshan Chattopadhyay and Mohit Gurumukhani and Noam Ringach and Rocco Servedio }, journal={arXiv preprint arXiv:2504.01856}, year={ 2025 } }