Randomized proof-labeling schemes

Mor Baruch, Pierre Fraigniaud, Boaz Patt-Shamir

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

22 Scopus citations

Abstract

Proof-labeling schemes, introduced by Korman, Kutten and Peleg [PODC 2005], are a mechanism to certify that a network configuration satisfies a given boolean predicate. Such mechanisms find applications in many contexts, e.g., the design of fault-tolerant distributed algorithms. In a proof-labeling scheme, predicate verification consists of neighbors exchanging labels, whose contents depends on the predicate. In this paper, we introduce the notion of randomized proof-labeling schemes where messages are randomized and correctness is probabilistic. We show that randomization reduces label size exponentially while guaranteeing probability of correctness arbitrarily close to one. In addition, we present a novel label-size lower bound technique that applies to both deterministic and randomized proof-labeling schemes. Using this technique, we establish several tight bounds on the verification complexity of MST, acyclicity, connectivity, and longest cycle size.

Original languageEnglish
Title of host publicationPODC 2015 - Proceedings of the 2015 ACM Symposium on Principles of Distributed Computing
Pages315-324
Number of pages10
ISBN (Electronic)9781450336178
DOIs
StatePublished - 21 Jul 2015
Externally publishedYes
EventACM Symposium on Principles of Distributed Computing, PODC 2015 - Donostia-San Sebastian, Spain
Duration: 21 Jul 201523 Jul 2015

Publication series

NameProceedings of the Annual ACM Symposium on Principles of Distributed Computing
Volume2015-July

Conference

ConferenceACM Symposium on Principles of Distributed Computing, PODC 2015
Country/TerritorySpain
CityDonostia-San Sebastian
Period21/07/1523/07/15

Keywords

  • Communication complexity
  • Distributed verfification

Fingerprint

Dive into the research topics of 'Randomized proof-labeling schemes'. Together they form a unique fingerprint.

Cite this