General Convex Agreement with Near-Optimal Communication

Abstract

Byzantine Agreement (BA) considers a setting of n parties out of which up to t can be byzantine (malicious), and requires the honest parties to agree on an input subject to a condition called validity: if all honest parties have input v, the output agreed upon must be v. Convex Agreement (CA) strengthens BA by requiring the output agreed upon to lie in the convex hull of the honest parties' inputs. This validity condition captures aggregation tasks, such as robust learning and sensor fusion, where honest inputs may differ but should still constrain the final decision. Existing protocols for CA over general convexity spaces require at least O(L · n2) bits of communication for L-bit inputs, leaving a gap with BA's Ω(L · n) lower bound. We investigate this gap, and we present deterministic synchronous CA protocols with near-optimal communication complexity in the long-message regime. When L=Ω(n·κ), where κ is a security parameter, our protocols use O(L· n n) bits of communication for finite convexity spaces and O(L· n1+o(1)) communication for Euclidean spaces Rd. Our protocols also have asymptotically optimal round complexity O(n). If an upper bound L on the honest inputs' length in bits is known in advance, we achieve near-optimal resilience t<n/(ω+) for any constant >0, where ω is the Helly number of the convexity space. When no such bound is known, we achieve resilience t<n/(ω++1). As a sample application, we show how our protocols can be used to obtain efficient solutions for parallel instances of BA. Our main technical contribution is the use of extractor graphs to obtain a deterministic assignment of parties to committees, which is robust against adaptive adversaries.

0

Turn this paper into a lesson

ArcXiv compiles a structured reading guide from this paper's metadata: plain-English importance, contributions, prerequisite concepts, which sections to read first, flashcards, and a quiz. Grounded in the abstract, never invented.

Discussion (0)

Sign in to join the discussion.

Loading comments…