Validity in Network-Agnostic Byzantine Agreement
Abstract
Byzantine Agreement (BA) considers a setting of parties, out of which up to can exhibit byzantine (malicious) behavior. Honest parties must decide on a common value (agreement), which must belong to a set determined by the honest inputs (validity). Depending on the use case, this set can grow or shrink, leading to various possible desiderata collectively known as validity conditions. Varying the validity property requirement can affect the regime under which BA is solvable.
Our work investigates how the selected validity property impacts BA solvability in the network-agnostic model, where the network can either be synchronous with up to byzantine parties or asynchronous with up to byzantine parties. We give necessary and sufficient conditions for a validity property to render BA solvable, both for the case with cryptographic setup and for the one without. This traces the precise boundary of solvability in the network-agnostic model for every validity property. Our proof of sufficiency provides a universal protocol, that achieves BA for a given validity property whenever the provided conditions are satisfied.
We note that, for any non-trivial validity property, the condition is necessary for BA to be solvable, even with cryptographic setup. Specializing this claim to gives that is required whenever one expects a purely synchronous protocol to also work in an asynchronous network when there are no corruptions. This is especially surprising given that, for some validity properties, is a sufficient condition without the last stipulation.
Keywords and phrases:
byzantine agreement, validity, network-agnostic protocolsCopyright and License:
2012 ACM Subject Classification:
Theory of computation Cryptographic protocolsEditor:
Dariusz R. KowalskiSeries and Publisher:
Leibniz International Proceedings in Informatics, Schloss Dagstuhl – Leibniz-Zentrum für Informatik
1 Introduction
Achieving agreement among the parties involved in a distributed system is crucial for maintaining consistent views. This becomes particularly challenging due to the potential for parties’ failures, which can range from benign crashes to malicious (byzantine) behavior. Byzantine Agreement (BA) is an extensively studied problem in distributed computing that tackles this challenge. It seeks to establish a common value amongst a set of parties even when up to parties exhibit byzantine behavior. A crucial aspect of BA lies in its validity condition, which requires that the value agreed upon reflects the honest parties’ proposals rather than being a default or arbitrary value. Standard BA definitions consider the so-called strong unanimity (also known as strong validity): if all honest parties propose the same value , the agreed-upon output must be . This is a powerful guarantee in applications concerning binary decisions, as it coincides with honest-input validity, which requires agreement on an honest input. However, strong unanimity fails to provide meaningful outputs for larger input spaces. For instance, consider a set of parties running a BA protocol to agree on a room’s temperature: minor measurement errors are inherent, and hence strong unanimity allows agreement on a corrupted party’s proposal. Similar issues arise in scenarios such as deciding on a location using GPS coordinates [5] or when the map is modeled as a graph [30, 11].
While achieving honest-input validity in scenarios where the input space is large (size ) is impossible [29], the literature offers a plethora of weaker alternatives that are stronger and more meaningful than strong unanimity. For instance, one may avoid corrupted outputs by enhancing strong unanimity with an additional condition called intrusion tolerance [13, 22, 23]: the honest parties either agree on an honest input or on a special symbol . In the aforementioned scenarios of deciding on a measurement or a meeting point, a highly suitable alternative is the so-called convex validity: the output agreed upon must be in the honest parties’ inputs convex hull, i.e., within the range of honest inputs if the input space is a subset of [32, 28, 30, 11, 22, 23]. Stronger variants for real values require the outputs to be close to the honest inputs’ median [31, 10], or to the -th lowest honest input [27]. However, the honest-range approach is not a universal solution: this would carry no meaning in a voting problem if we represented candidates with integers. Instead, approaches based on social choice theory (Pareto validity) lead to more appropriate validity definitions [26].
The multitude of validity definitions leads to a natural question: what are the necessary and sufficient conditions for achieving BA with a given validity property, i.e., to solve a given validity property? This question can be concerned with multiple aspects, such as resilience thresholds , round complexity, or message complexity. In addition, the conditions may depend on whether a cryptographic setup and randomization are available. The communication model assumed also plays an important role: one extreme is the synchronous model, where all parties have synchronized clocks, and all messages get delivered within a predefined amount of time . This enables elegant protocols that operate in rounds, but that may fail in a real-life network where sporadic issues are possible. The other extreme is the asynchronous model, which only assumes that messages get delivered eventually. The asynchronous model comes with highly robust protocols, but also with important drawbacks: (a) lower resilience threshold: e.g., as opposed to (assuming digital signatures) for strong unanimity, or as opposed to for convex validity in ; (b) randomization is a requirement [19]. The middle ground between the two models has also been considered. The partially synchronous model [17] bridges the gap between the two extremes by assuming that the network is initially asynchronous and eventually becomes synchronous. In the synchronous and partially synchronous models, the solvability of validity conditions using deterministic protocols is completely understood [7, 8].
In this work, we are concerned with a different paradigm for bridging the gap between synchrony and asynchrony, namely the network-agnostic model [4]: parties are initially unaware of whether the network is synchronous or not: if it is synchronous, up to of the parties involved may be corrupted, and otherwise only up to . Network-agnostic protocols are designed to provide guarantees in both cases. We ask the following question:
Under what conditions can a validity property be solved in the network-agnostic model?
1.1 Our Contribution
We provide a complete characterization for achieving network-agnostic BA with a given validity property, establishing tight necessary and sufficient conditions.
We first show that, even if cryptographic setup is available, the condition is a requirement for any non-trivial validity condition to be solvable (i.e., a condition for which simply outputting a default value does not suffice). When no cryptographic setup is available, we show the stronger requirement of . Our proof for the latter, in fact, works in the synchronous model and, therefore, strengthens the characterization provided by [7] for the synchronous model. In particular, [7] only focuses on deterministic protocols, while our proofs rely on different techniques that also apply to randomized protocols.
Afterwards, regardless of whether cryptographic setup is available or not, we add one more necessary condition, which is an adaptation of the similarity condition of [8] and the containment condition of [7] to the network-agnostic model. Roughly, this requires that similar honest inputs’ configurations have a valid output in common. The term similar captures that some of the proposed inputs may come from corrupted parties, and that, in asynchronous networks, some honest inputs may be missing due to high network delays.
Finally, we show that, together, the aforementioned conditions are also sufficient by providing a universal protocol, that achieves network-agnostic BA for a given validity property whenever these conditions are satisfied. This is a more general variant of the protocol of [11]. In particular, the requirement for solvability is precisely together with the similarity condition assuming cryptographic setup, and together with the similarity condition assuming no cryptographic setup. Our protocol is randomized, which is a requirement when the network may be asynchronous and [19].
1.2 Related Work
General validity conditions.
The foundational investigation into general validity properties was initiated by Civit et al. [8] for the partially synchronous model. Subsequently, Civit et al. [7] embarked on a follow-up study, extending their analysis to the synchronous model. Both works provide a complete characterization, identifying the necessary and sufficient conditions for solving a validity property deterministically. We also note that the contributions of [8, 7] extend beyond this characterization, an important side of these works lying in the exploration of lower bounds on message complexity. This generalizes the well-established Dolev-Reischuk bound on message complexity for BA with strong unanimity [15] to encompass the broader landscape of non-trivial validity properties. Considerations of message complexity are outside our scope. We also note that probabilistic validity properties are outside the scope of the analysis of Civit et al, and also outside our scope. A notable example is qualitative validity, introduced by Goren et al [25].
Network-Agnostic BA and particular validity conditions.
Designing protocols that achieve security guarantees in both synchronous and asynchronous networks has been the subject of an extensive line of work. The network-agnostic paradigm was introduced by Blum, Katz and Loss [4]. The work of [4] shows that, if a public key infrastructure is provided, BA with strong unanimity can be achieved if and only if . Further works on network-agnostic BA with strong unanimity have focused on improving the efficiency guarantees [12, 13].
Due to its broad applicability, convex validity within the network-agnostic communication paradigm has attracted increased attention. Ghinea, Liu-Zhang and Wattenhofer [20, 21] have investigated the feasibility of achieving convex validity for a weaker variant of BA, known as Approximate Agreement [14, 1]. In particular, [20] shows that Approximate Agreement on real numbers is solvable under the same necessary and sufficient condition assuming a public key infrastructure. Building on the previous, [21] gives sufficient conditions for the multidimensional variant of the problem that match the known requirements in the pure synchronous and asynchronous models [32, 28]. Returning to the non-approximate version, Constantinescu et al. [11] have provided the tight conditions for network-agnostic BA with convex validity for abstract convex spaces. In this case, the conditions include or, if no cryptographic setup is available, , along with a few additional conditions that depend on the Helly number of the convexity space.
Other takes on network-agnostic BA have been considered, such as scaling the validity guarantees with the network conditions: for real-valued inputs, [10] proposes a protocol for BA with median validity guaranteeing that the output is closer to the honest inputs’ median when the network is synchronous than when it is asynchronous. This protocol simultaneously matches the optimal closeness guarantees for purely synchronous [31, 27] and purely asynchronous [10] networks. Such validity properties that scale with the network conditions are outside our scope.
Comparison to previous works.
As outlined above, the conditions and, if no cryptographic setup is available, , have been proven to be necessary for strong unanimity properties, i.e., stronger than strong unanimity [4]. Our work shows that this is a requirement for weaker validity properties as well, i.e., for any non-trivial property. We find this result surprising especially for weak validity: if all parties are honest and hold input , then the output agreed upon must be . Assuming a public key infrastructure, this property is solvable in the synchronous model for , as a straightforward application of the Dolev-Strong broadcast protocol [16]. On the other hand, our result implies that if we expect a BA protocol with weak validity to remain secure in the asynchronous model even for no corruptions (i.e., ), then the synchronous resilience threshold steps down from to .
In contrast to the work of [11] regarding network-agnostic BA with convex validity, our results move the difficulty of proving such feasibility results as a whole to only verifying whether a validity condition satisfies our similarity condition. That is, one can show that convex validity satisfies this similarity condition if and only if the necessary Helly number-based conditions of [11] hold. Our impossibility arguments diverge: we investigate these under any validity property, while the work of [11] considers a fixed validity property but also shows impossibility under weaker agreement requirements. On the other hand, our protocol matching our lower bounds is a more general variant of the protocol of [11].
Our paper provides a characterization similar to those of [8, 7] for the synchronous and partially synchronous settings, respectively. The key difference is that these two models allow for deterministic protocols, while the network-agnostic model inherently requires randomization for achieving BA when [19]. Consequently, the focus shifts towards randomized protocols, requiring our proofs to employ different techniques. While the arguments behind the containment condition of [7] can be easily adapted for randomized protocols, this is not immediate for their proof that is necessary when no cryptographic setup is available. Our proof for this lower bound, in fact, assumes the synchronous setting and, therefore, strengthens the characterization of [7]. Summing up, their necessary conditions now hold even for randomized protocols, and, as shown in their paper, they can be matched by deterministic protocols.
2 Preliminaries
We consider a setting with parties running a protocol in a fully-connected network, where links model authenticated channels. We will be working in the network-agnostic model: the network may be synchronous, or asynchronous, and the parties are not aware a priori of the type of network. If the network is synchronous, the parties hold perfectly synchronized clocks and each message is delivered within a publicly known amount of time . Otherwise, if the network is asynchronous, messages can get delayed for an arbitrary amount of time, and clocks may not be synchronized.
Adversary.
We assume a central adversary that may corrupt up to of the parties if the network is synchronous, and up to parties if the network is asynchronous. Corrupted parties permanently become byzantine, and hence may deviate arbitrarily (maliciously) from the protocol. The adversary additionally controls the message delivery schedule, subject to the conditions of the network type. Our impossibility results assume a static adversary (i.e., chooses which parties to corrupt at the beginning of the protocol’s execution). Our protocol, on the other hand, provides security even against an adaptive adversary (i.e., chooses which parties to corrupt at any point in the protocol’s execution).
Cryptographic setup.
We will consider both settings with and without cryptographic setup. Protocols assuming a cryptographic setup will make use of a public key infrastructure (PKI) and a secure signature scheme, and only hold against a computationally bounded adversary. For simplicity of presentation, we assume that the signatures are perfectly unforgeable.
Byzantine Agreement and Validity.
A Byzantine Agreement (BA) protocol assumes that each (honest) party holds a value as input, and enables the parties to agree on a common output satisfying a given validity condition. We assume that is at most countably infinite. In the full version of our paper [9, Section 7], we explain why such an assumption is actually necessary to get any relevant result. In the following, we present each property that a BA protocol needs to satisfy. The first property is termination, which may be deterministic (for synchronous protocols) or probabilistic while the second is agreement. We define them below:
-
(Termination) Every honest party decides on an output .
-
(Probabilistic Termination) As time goes to infinity, the probability that an honest party has not yet decided on an output value tends to .
-
(Agreement) If two honest parties output and , then .
Before describing the validity property, we need to define input configurations. Regardless of the nature of the adversary, these are defined by looking at the honest parties’ inputs after the adversary has decided which parties to corrupt. Hence, in impossibility results, where we consider a static adversary, input configurations are defined before the protocol’s execution. An input configuration is a set consisting of pairs of honest parties with their inputs: if , then is an honest party with input . Naturally, no party occurs twice in (i.e., honest parties cannot simultaneously have two inputs). We use the notation to refer to the set of (honest) parties in the input configuration . Note that, if , then is corrupted in the input configuration . Let denote the set of all possible input configurations. We also note the inclusion relation for input configurations: for , if and only if and the parties in have the same input value in both and . We say that an input configuration is maximal if . Moreover, as is at most countably infinite, the size of is at most countably infinite. A validity property is then defined by a mapping from honest parties’ inputs to valid outputs:
-
(Validity) If is the input configuration defined by the honest parties and their inputs, then no honest party outputs .
This validity definition matches the one used in [6, 7]. We say that a validity property val is trivial if Note that, if this condition holds, we can achieve validity, agreement, and termination with no communication: parties output a value in .
A validity property val is solvable if there is a BA protocol solving val, as defined below.
Definition 1.
A protocol is a -secure BA protocol solving a validity property val if it achieves probabilistic termination, agreement, and validity for the given property val even when up to parties are corrupted if it runs in a synchronous network, and even when up to parties are corrupted if it runs in an asynchronous network.
Definition 2.
A protocol is a -secure BA protocol solving a validity property val if, when running in a synchronous network, it achieves (probabilistic) termination, agreement, and validity for the given property val even when up to parties are corrupted.
One might be tempted to believe that a -secure protocol is simply a -secure protocol, but the difference is rather subtle. Namely, a -secure network-agnostic BA protocol also provides guarantees in an asynchronous network if all parties are honest. On the other hand, a -secure (synchronous) BA protocol is not required to provide any guarantees if the synchrony assumptions fail, even if there are no corruptions. We add that this subtle difference would not apply to a purely asynchronous variant of the definition, which is equivalent to -secure network-agnostic BA protocol.
Randomness.
Our work covers BA protocols which can run in the asynchronous setting. As a result of FLP [19], the protocol considered must be randomized. We consider the randomness as a black box where, at each instant, a party can ask for one or multiple random bits, each set to or uniformly and independently. So the randomness from a party’s point of view can be seen as an infinite bitstring being progressively read. There may also be shared randomness, which gives the same result to each party. Therefore, when running a protocol, we can consider its behavior over a probabilistic space where for some is the set of all possible random bits parties will read. is the -algebra generated by taking all possible prefixes from each bitstring, and is the resulting probability measure from having each bit following independently a Bernoulli random variable . From this point on, when mentioning probabilities, like almost surely properties, we refer to the probabilistic space given above.
Executions.
For a protocol , we define an execution to be a particular feasible run of . In particular, contains the input configuration from which the protocol started, the behavior of the byzantine parties, and the scheduler’s behavior (including whether the network was synchronous or asynchronous). Because an execution depends on the randomness, it is actually a random variable . We then say that an execution decides if all honest parties in the execution eventually decide an output. We note that, given a protocol satisfying probabilistic termination, including the scheduler and strategy of the adversary, an execution for this protocol decides almost surely. We will also be using the term canonical to refer to executions occurring in a synchronous network where all messages are delivered exactly units of time after being sent and where all corrupted parties crash right at the beginning of the protocol (i.e., they do not send any messages). We add that, for any given input configuration, there is a unique canonical execution (which, recall, is a random variable).
For a given protocol and randomness , we say that two executions and cannot be distinguished by a party that is honest in both executions if it has the same initial state in and (i.e., input and randomness), and receives in both and the same messages at the same times. As a consequence, if cannot distinguish between and then is in exactly the same state at any time in and . Hence, if decides a value at time in one of the two executions, then it also decides at time in the other. We also say that an execution is deciding if all honest parties eventually decide when running with randomness . If a protocol satisfies probabilistic termination, then an execution is almost surely deciding.
Validity in indistinguishable executions.
Goren et al. [25] offer a framework to formalize indistinguishability for randomized protocols. We instead decided to take a different approach by looking at deterministic indistinguishability after fixing the randomness . This can allow for easier results as we do not have to consider the whole probabilistic space at a time. For example, some of our proofs require us to define multiple executions depending on and cannot be achieved with the framework above. The drawback is that all the assumptions made must hold almost surely for the proofs to be correct. Indistinguishability is a powerful tool, especially when considering scenarios where byzantine parties follow the protocol correctly, but with inputs of their own choice. This leads us to the following lemma. The proof is included in Appendix A.
Lemma 3.
Let val be a validity property and be a -resilient BA protocol solving val. Consider two input configurations such that . Then, the value agreed upon in any execution of which decides and where the input configuration is must be in .
Intuitively, Lemma 3 ensures that honest parties cannot distinguish between a scenario where all parties in are honest, and one where the parties in are, in fact, byzantine. With the lemma in mind, for any validity property val, we can define a new validity property such that for all . Property is simultaneously a stronger version of val, in that for all we have , but it also has the property of being monotonically decreasing, in that for we have . Armed as such, the previous lemma has the following immediate corollaries:
Corollary 4.
A solvable validity property val is trivial if and only if it permits deciding the same value for all maximal input configurations, i.e., .
We end by stating a technical lemma that will be of use in the proofs presented in the subsequent sections. The proof of Lemma 5 is included in Appendix A.
Lemma 5.
Let val be a solvable validity property and a protocol solving val. Let be a maximal input configuration. If, for every maximal input configuration , the canonical executions of for and decide the same value almost surely, then val is trivial.
3 Lower Bound on
In this section, we prove that, for any non-trivial validity property, the condition is necessary for it to be solvable in the network-agnostic model even if cryptographic setup is available. Our proof will be organized as follows: we start with a preliminary lemma in Section 3.1, which focuses on a simplified setting where . In this setting, at most one party can crash if the network is synchronous, and both parties are honest if the network is asynchronous. Our preliminary lemma will show a somewhat counter-intuitive result: roughly, the value decided upon in canonical executions is independent of the honest parties’ inputs. In Section 3.2, we move from the simplified setting with two parties to a warm-up variant of our main proof. We will be working with parties, but we will only consider the particular case . By reducing this case to our preliminary lemma, we show that the condition is necessary in this setting. Finally, Section 3.3 focuses on the general case, showing that is necessary by reducing to our preliminary lemma. The main proof will be a more general version of the warm-up proof.
We note that the proofs by Civit et al. [7] rely on reducing any non-trivial validity property to weak validity, enabling lower bounds to focus solely on weak validity. However, their reduction is invalid for randomized protocols and hence cannot be used in our setting.
3.1 Preliminary Lemma
As previously mentioned, our preliminary lemma focuses on a simplified setting with parties in the network-agnostic model. When the network is synchronous, we allow the adversary to corrupt up to one party (). We restrict the adversary’s capabilities by only allowing the corrupted party to crash. When the network is asynchronous, both parties are honest (). Then, we assume a protocol achieving (probabilistic) termination and agreement in this setting. We show that, almost surely, once randomness is fixed, all canonical executions decide the same value. Note that there may be a set of randomnesses such that some canonical executions do not even decide, but the probability of picking a randomness in this set is zero.
Lemma 6.
Assume , , and that corrupted parties are only allowed to crash. Consider a protocol that achieves probabilistic termination and agreement in this setting. Then, almost surely, there exists a value such that all canonical executions of decide when running.
Proof.
Denote the two parties by and . Let . For every input configuration, we will define a finite number of executions using randomness , including the required canonical executions. Under the assumption that all executions defined for decide, we show that all canonical executions using randomness decide the same value . From here, our proof proceeds as follows: individually, each defined execution decides almost surely (by construction). The number of executions defined for each input configuration is finite, and the set of input configurations is countable (since is countable). A countable intersection of events holding almost surely holds almost surely. Then, almost surely, all defined executions for decide, i.e., our additional assumption holds almost surely, completing the proof.
Hence, from now on, we fix and only consider executions running with this randomness . We assume that all executions we consider decide, and we want to show that all canonical executions decide the same value .
We first consider canonical executions where one of the parties crashes. Let be two arbitrary values. First, we consider the canonical execution of (in a synchronous network) where is honest and has input . is corrupted and crashes at the beginning of the execution. We have assumed that is deciding, hence outputs some value within a finite amount of time (note: without receiving any messages from ). Second, consider the canonical execution of (again, in a synchronous network) where is honest and has input . is corrupted and crashes at the beginning of the execution. We have assumed that is deciding, hence outputs some value within a finite amount of time . We prove that by defining a third execution , but, this time, in the asynchronous model. Here, both and are honest with inputs and respectively. The scheduler delays any message between them until time . This way, cannot distinguish execution from execution , and therefore it outputs in as well. Similarly, outputs in . Recall that achieves agreement, hence . Note that the argument holds for arbitrary , so we get that all canonical executions where one of the parties crashes decide the same value, which we denote by .
We now consider canonical executions where none of the parties crashes and show that all such executions also decide . Consider any and the canonical execution of where both parties are honest and have inputs and . We also define as before. From the previous part, it follows that decides . We will now show that decides as well. Based on our assumption, we already know that decides, so it does so after a finite number of messages . For the next part of the proof, we first give an intuitive outline. Roughly, we will build a chain of scenarios between execution and execution : in each scenario , the network is asynchronous, and the scheduler ensures that the first messages are received synchronously, while all subsequent messages are delayed sufficiently long. Scenarios and correspond to executions and respectively, and any two consecutive scenarios will be indistinguishable to the party that sent the last message: this will imply that also decides . In the following, we write this idea formally.
For , we consider an execution of in the asynchronous model: both and are honest, and they have inputs and respectively. In execution , the scheduler uses the same strategy as that of execution : the scheduler delays any message in execution until time . Hence, and cannot distinguish between executions and , implying that decides by some time . In execution , the scheduler allows the first message to be delivered after exactly time. Assume without loss of generality that this message is sent by . All further messages are delayed until time (we define the exact time later): hence, cannot distinguish from this execution and execution , therefore it outputs by time , as in execution . , on the other hand, can distinguish between and : however, it cannot distinguish between and an execution where the network is, in fact, synchronous, and has crashed. If has crashed, has to output eventually, hence by time . Hence, the scheduler makes sure to delay all messages until time . Consequently, has to output in by time . The next executions are defined similarly: in execution with , the scheduler allows the first messages to be delivered after exactly units of time. The remaining messages are delivered sufficiently late to ensure that the last message’s sender is unable to distinguish between and execution . Thus, the last message’s sender outputs in execution , which forces the other honest party to also output .
We remark that executions and are indistinguishable, so will decide . Since this holds for arbitrary values , we have obtained that all canonical executions where no party crashes also output , hence completing the proof. ∎
3.2 Warm-up:
As a warm-up towards the main result, we focus on the particular case , and show that the condition is necessary. Intuitively, when , one cannot distinguish between a scenario where half of the parties crash in a synchronous network, and a scenario where half of the parties are honest but delayed in an asynchronous one. This way, the presence of the asynchronous case, even with no corruptions, allows two disjoint sets of honest parties to only run the protocol within their own set. Since the two sets run the protocol independently, the honest parties agree on a valid value only if the given validity property is trivial. Note that this is the case even for weak validity, which can be solved in the synchronous model for up to corruptions. Our result implies that expecting a synchronous protocol to provide guarantees when it runs in a corruption-free asynchronous network impacts the overall resilience.
Theorem 7.
Assume and consider a validity property val. If and there is a -secure BA protocol solving val, then val is trivial.
Proof.
Consider a (possibly randomized) -secure BA protocol that solves val when . Let and be two arbitrary maximal input configurations. We show that the canonical executions of and almost surely decide on the same output when run using the same randomness. Then, Lemma 5 ensures that val is trivial.
We use to build a -party protocol that matches the setting described in Lemma 6. For protocol , we consider the input set and output set , and we denote the two parties running by and . Since , we may partition the set of parties into two sets and of parties each.
Then, as shown in Figure 2, will simulate the parties in , while will simulate the parties in . Concretely, in protocol , proceeds as follows:
-
simulates all parties of running .
-
If has input , then the simulated parties in use their inputs from . Otherwise, they use their inputs from .
-
Messages between the simulated parties in are received after exactly units of time, and forwards to every message sent by a simulated party in to a party in . Once receives this message, it immediately forwards it to the simulated receiver in .
-
As soon as a party in decides a value, decides this value. continues forwarding messages as described above.
proceeds identically to , switching and .
Note that running in an asynchronous network where both and are honest corresponds to running in an asynchronous network where all parties are honest. In addition, running in a synchronous network where at most one party may crash corresponds to running in a synchronous network where at most parties may crash. Then, since is a -secure BA protocol, achieves probabilistic termination and agreement in the setting described in Lemma 6. Then, applying Lemma 6, we obtain that: almost surely, there is a value such that all canonical executions of decide on the same value . Moreover, the canonical execution of with input values matches the canonical execution of for . Similarly, the canonical execution of with input matches the canonical execution of . As a consequence, canonical executions of and decide the same value almost surely. Using Lemma 5, we can therefore conclude that val is trivial.
3.3 General Result
We are now ready to prove the final statement of this section, presented below.
Theorem 8.
Consider a validity property val, and such that and . If there is a -secure BA protocol solving val when , then val is trivial.
Proof.
Assume and that there is a -secure BA protocol solving val. We consider two input configurations and such that (i.e., all parties are honest). We show that, almost surely, the canonical executions of and decide on the same output. Then, Lemma 5 ensures that val is trivial. Similarly to the proof of Theorem 7, we use to build a two-party protocol that matches the setting of Lemma 6. For , we consider the input space and the output space .
This time, we partition into three sets , and such that and . A crucial difference from the proof of Theorem 7 is that, as shown in Figure 3, each party in simulates its own copy of the parties in . Our construction will ensure that, when runs in the synchronous setting, the two simulated copies of each party in will be in the exact same state at any point, maintaining the guarantees of when at most of the parties are corrupted. Meanwhile, in the asynchronous setting, the copies of the parties in may be in different states, but is able to tolerate byzantine parties in this case. Concretely, in protocol , party proceeds as follows:
b) This is how the network looks like from the point of view of a party in or : they are unaware of the second set being simulated in parallel.
-
simulates all parties of running .
-
If has input , then parties in take their input from . Otherwise, they take their input from .
-
As depicted in Figure 4, the messages sent between the parties simulated by are exchanged as if all parties are running independently: each such message is delivered after exactly units of time. Additionally, once a simulated party in sends a message to a simulated party in , immediately forwards this message to as well. Once receives this message, it immediately forwards it to its own simulated receiver in . The message delay here depends on the type of network that is running in.
-
Messages from a party in to are sent from to . then forwards each such message to its simulated receiver in .
-
discards any messages sent by the simulated parties in to parties in .
-
As soon as a party in (but not ) decides a value, decides this value. continues forwarding messages as described above until all its simulated parties terminate.
The behavior of is the same as the behavior of , switching and .
a) If a simulated party in wants to send a message to a party in , then two identical messages are actually sent: the first one to the copy of the receiver simulated by , and the second to the copy simulated by in .
b) If a party in wants to send a message to a party in , if the two parties are simulated by the same entity (here ), then the message gets received as expected. Otherwise, the message is discarded and the party in never receives it.
We now need to analyze in the setting described by Lemma 6. Running in an asynchronous network where both parties are honest corresponds to running in a network where the communication between parties in and is asynchronous. While the simulated copies in are not necessarily consistent, is resilient against byzantine corruptions, and therefore maintains its guarantees. Hence, achieves agreement and probabilistic termination in this setting. It remains to show that also achieves these guarantees in a synchronous network where one of the two parties may crash. Settings where both and are honest correspond to running in a synchronous network where all parties are honest. We note that, in this case, for each party in , the copy simulated by and the copy simulated by maintain the same state at all times. Settings where at most one of and may crash correspond to running in a synchronous setting where the parties meant to be simulated only by the party crashing in are corrupted. As tolerates corruptions, it maintains its guarantees. Hence, achieves agreement and probabilistic termination in this setting as well.
We conclude the proof in an identical manner to the proof of Theorem 7. Applying Lemma 6, we obtain that, almost surely, all canonical executions of decide on the same value. Moreover, the canonical execution of with input values matches the canonical execution of for . Similarly, the canonical execution of with input matches the canonical execution of . As a consequence, canonical executions of and decide the same value almost surely. Using Lemma 5, we can therefore conclude that val is trivial.
4 Lower Bound on Without Cryptographic Setup
The previous section has proven that the condition is necessary regardless of whether a cryptographic setup is available or not. We now focus on settings without cryptographic setup and prove an even stronger condition. We show that, in such settings, the condition is necessary even in the synchronous model. Since a protocol achieving -secure BA in the network-agnostic model also achieves -secure BA in the synchronous model, this bound immediately applies to the network-agnostic model. We add that our result extends the requirement of provided by Civit et al. [7] for synchronous deterministic protocols to cover randomized protocols as well.
4.1 Preliminary Lemma
Similarly to the outline of Section 3, we first consider a setting with three parties, out of which at most one is byzantine. Afterwards, we focus on the general case. Lemma 9 is an improvement over the result of Fischer, Lynch, and Merritt for weak validity [18]: the result of [18] only applies for weak validity and protocols must always decide in a finite amount of time, which is a lot stronger than probabilistic termination. Our proof uses the main core idea but improves it to lift these restrictions. Roughly, we will be running in a larger ring containing multiple copies of each party, as depicted in Figure 5.
The ring is constructed from two canonical executions with different input configurations. Parties adjacent in this ring cannot distinguish between the ring and the original setting of three parties, as the third party may be byzantine and simulate the rest of the ring. This forces parties adjacent in the ring to output the same value, which implies that the two original executions lead to the same output. We defer the formal proof to Appendix B.1.
Lemma 9.
Consider parties in a synchronous network, and assume a protocol that achieves (probabilistic) termination and agreement in this setting even when up to one party is byzantine. Then, almost surely, all canonical executions of decide the same value.
4.2 General Result
To prove our main result in this setting, we use a strategy similar to the proof of Theorem 7. Concretely, we assume an -party protocol that achieves val whenever and use it to construct a three-party protocol that contradicts Lemma 9. We defer the formal proof to Appendix B.2.
Theorem 10.
Assume and consider a validity property val. If there is a -secure BA protocol solving val in the synchronous model when no cryptographic setup is available and , then val is trivial.
Then, as any lower bound in the synchronous model also holds in the network-agnostic model, Theorem 10 immediately implies the following corollary.
Corollary 11.
Consider a validity property val, and let such that and . If there is a -secure BA protocol solving val when no cryptographic setup is available and , then val is trivial.
5 Similarity Condition
The lower bounds on presented in the previous sections are indeed necessary, but not yet sufficient. We may instantiate, for instance, the input space as the (finite) set of vertices of a (publicly known) labeled graph with maximum clique size . We consider convex validity, under the so-called monophonic convexity. For this example, network-agnostic BA requires the stronger lower bound [11]. Roughly, if any of the conditions and fails to hold, one can find scenarios where the simple presence of byzantine parties (following the protocol correctly, with inputs of their choice) prevents the honest parties from obtaining a valid output. In this section, we prove the need of one more condition that captures these validity-dependent requirements, and enables the honest parties to find a valid output even if their view over the honest inputs is not accurate. This additional condition matches the similarity condition of [8] for the partially synchronous model, and the containment condition of [7] in the synchronous model.
We need to establish a few notions. The first is the notion of neighbors of an input configuration. The neighbors of , denoted by , are the input configurations such that the parties in hold the same input values in and . Formally, . The definition of neighbors is symmetric (if then ).
The second notion is that of similar configurations of an input configuration , denoted by . These are input configurations that may be indistinguishable from . In the synchronous model, these are configurations such that . Roughly, this models scenarios where some of the parties are corrupted, but follow the protocol correctly with inputs of their own choice. In the asynchronous model, these are configurations containing parties: this additionally takes into account that at most honest parties may be isolated due to network delays. Hence, we define as
We may now define the similarity condition, which Lemma 13 proves to be necessary for the network-agnostic model. Lemma 13 adapts Theorem 2 of [8] and Lemma 8 of [7] to the network-agnostic model, and it relies on standard indistinguishability arguments. We defer the proof to Appendix C.
Definition 12 (Similarity condition).
We say that a validity property val satisfies the similarity condition if there is a Turing-computable function such that, for any input configuration , .
Note that the existence of such a function also implies .
Lemma 13.
If a validity property val is solvable in the network-agnostic model, then val satisfies the similarity condition.
It is worth noting that, in the proof of this lemma, the deterministic Turing function is defined based on a randomized protocol that solves val. This is justified because, as discussed in the proof, when time complexity is not taken into account, probabilistic Turing machines are as expressive as deterministic ones.
6 Sufficiency and Main Result
We now show that the conditions presented in the previous sections are not only necessary, but also sufficient, hence proving our main result, stated below.
Theorem 14.
Assume a non-trivial validity condition val. Then, there is a -secure protocol solving val if and only if the following conditions hold:
-
val satisfies the similarity condition.
-
or, if PKI is available, .
The remainder of the section describes a protocol that matches our necessary conditions, as stated in the lemma below. Theorem 14 then follows from combining Lemma 15 with the requirements discussed previously: the lower bounds on , described in Theorem 8 and Corollary 11, plus the similarity condition, proven to be necessary in Lemma 13.
Lemma 15.
Assume a validity condition val that satisfies the similarity condition. Then, if , or, assuming that PKI is available, if , there is a -secure BA protocol solving val.
Our construction behind Lemma 15 generalizes the network-agnostic BA protocol of [11] that solves convex validity. The parties distribute their input values using a protocol achieving Agreement on a Core-Set (ACS), which provides them with an identical view over the inputs, i.e., with a potential input configuration. This is a (randomized) communication primitive enabling identical views in the pure asynchronous model [2, 3]. We make use of the ACS definition of [11], included below, which differs from the standard definition by providing stronger properties in the synchronous model: it additionally ensures that all honest inputs are included in the common view if the network is synchronous. This property is essential for matching the higher resilience threshold in a synchronous network. This way, the parties can apply a deterministic decision over the view agreed upon in ACS and obtain an output.
Definition 16.
Let be a protocol where every party holds an input and outputs a set consisting of at least value-sender pairs. We consider the following properties in addition to those presented in Section 2:
-
Integrity: If and are both honest and , then .
-
Honest Core: If an honest party outputs , then contains all honest parties.
Then, we say that is a -secure ACS protocol if it achieves the following:
-
Probabilistic termination, agreement, integrity, and honest core when running in a synchronous network where up to parties are corrupted;
-
Probabilistic termination, agreement, and integrity when running in an asynchronous network where up to parties are corrupted.
We make use of the ACS construction of [11], described by the result below.
Theorem 17 ([11]).
Consider such that . If , or, if PKI is available and , there is a -secure ACS protocol .
We may now present the proof of Lemma 15, describing our protocol.
Proof of Lemma 15.
Our BA protocol solving val proceeds as follows: the parties distribute their input values using the protocol described in Theorem 17. provides the parties with the same output set of at least value-sender pairs, representing a potential input configuration. Once the parties obtain this set, they output , where is the Turing-computable function provided by val satisfying the similarity condition.
-secure BA solving val
Code for party with input
Regardless of whether the network is synchronous or asynchronous, since achieves probabilistic termination, our BA protocol achieves probabilistic termination as well. In addition, since achieves agreement, the parties compute their output identically, and therefore our BA protocol achieves agreement.
It remains to prove that the honest parties’ output is in , where denotes the (actual) input configuration (containing only the honest parties and their inputs). Since , it will be sufficient to show that . Regardless of the type of network, the integrity property of ensures that . If the network is asynchronous, and therefore . Otherwise, if the network is synchronous, the honest core property of ensures that honest parties and their inputs are included in . Then, and therefore in this case as well. Thus, as , we get that the value agreed upon is in , which proves the validity of the protocol and concludes the proof.
7 Conclusions and Future Work
We investigated the conditions that a validity property needs to satisfy in order to be solvable in the network-agnostic model and established the necessary and sufficient conditions. Our results demonstrate that solving a non-trivial validity property val requires (i) that val satisfies the similarity condition, and (ii) that assuming a public key infrastructure, or otherwise. Further, we provided a universal protocol that solves a given validity property whenever these established conditions are met. Our characterization follows the line of works of [8, 7] focusing on the partially synchronous model and on the synchronous model. At the same time, it generalizes prior results on when network-agnostic BA can be achieved [4, 11] from fixed validity properties to arbitrary validity properties.
While our work provides a complete answer for solvability, we leave a number of exciting problems open. Our results and approach do not hold if we allow the protocol to fail with some probability . Focusing on this weaker setting would likely allow more efficient protocols. Future works could also extend our characterization to cover settings where both and are uncountable sets and consider proving message complexity lower bounds. Other promising directions would aim to improve the efficiency of our universal protocol, or to generalize our results further to network-dependent validity properties (that allow weaker guarantees if the network is asynchronous) [10], or to weaker agreement definitions [11].
References
- [1] Ittai Abraham, Yonatan Amit, and Danny Dolev. Optimal resilience asynchronous approximate agreement. In Principles of Distributed Systems, pages 229–239, Berlin, Heidelberg, 2005. doi:10.1007/11516798_17.
- [2] Michael Ben-Or, Ran Canetti, and Oded Goldreich. Asynchronous secure computation. In Proceedings of the Twenty-Fifth Annual ACM Symposium on Theory of Computing, STOC ’93, pages 52–61, New York, NY, USA, 1993. Association for Computing Machinery. doi:10.1145/167088.167109.
- [3] Michael Ben-Or, Boaz Kelmer, and Tal Rabin. Asynchronous secure computations with optimal resilience (extended abstract). In Proceedings of the Thirteenth Annual ACM Symposium on Principles of Distributed Computing, PODC ’94, pages 183–192, New York, NY, USA, 1994. Association for Computing Machinery. doi:10.1145/197917.198088.
- [4] Erica Blum, Jonathan Katz, and Julian Loss. Synchronous consensus with optimal asynchronous fallback guarantees. In Theory of Cryptography Conference, pages 131–150. Springer, 2019. doi:10.1007/978-3-030-36030-6_6.
- [5] Zohir Bouzid, Maria Gradinariu Potop-Butucaru, and Sébastien Tixeuil. Optimal byzantine-resilient convergence in uni-dimensional robot networks. Theoretical Computer Science, 411(34):3154–3168, 2010. doi:10.1016/j.tcs.2010.05.006.
- [6] Pierre Civit, Seth Gilbert, Rachid Guerraoui, Jovan Komatovic, Matteo Monti, and Manuel Vidigueira. Every Bit Counts in Consensus. In 37th International Symposium on Distributed Computing (DISC 2023), volume 281, pages 13:1–13:26, Dagstuhl, Germany, 2023. doi:10.4230/LIPIcs.DISC.2023.13.
- [7] Pierre Civit, Seth Gilbert, Rachid Guerraoui, Jovan Komatovic, Anton Paramonov, and Manuel Vidigueira. All byzantine agreement problems are expensive. In Proceedings of the 43rd ACM Symposium on Principles of Distributed Computing, PODC ’24, pages 157–169, New York, NY, USA, 2024. Association for Computing Machinery. doi:10.1145/3662158.3662780.
- [8] Pierre Civit, Seth Gilbert, Rachid Guerraoui, Jovan Komatovic, and Manuel Vidigueira. On the validity of consensus. In Proceedings of the 2023 ACM Symposium on Principles of Distributed Computing, pages 332–343, 2023. doi:10.1145/3583668.3594567.
- [9] Andrei Constantinescu, Marc Dufay, Diana Ghinea, and Roger Wattenhofer. Validity in network-agnostic byzantine agreement. Full version of this paper. doi:10.48550/arXiv.2410.19721.
- [10] Andrei Constantinescu, Diana Ghinea, Lioba Heimbach, Zilin Wang, and Roger Wattenhofer. A Fair and Resilient Decentralized Clock Network for Transaction Ordering. In 27th International Conference on Principles of Distributed Systems (OPODIS 2023), volume 286, pages 8:1–8:20, Dagstuhl, Germany, 2024. doi:10.4230/LIPIcs.OPODIS.2023.8.
- [11] Andrei Constantinescu, Diana Ghinea, Roger Wattenhofer, and Floris Westermann. Convex Consensus with Asynchronous Fallback. In Dan Alistarh, editor, 38th International Symposium on Distributed Computing (DISC 2024), volume 319, pages 15:1–15:23, Dagstuhl, Germany, 2024. doi:10.4230/LIPIcs.DISC.2024.15.
- [12] Giovanni Deligios, Martin Hirt, and Chen-Da Liu-Zhang. Round-efficient byzantine agreement and multi-party computation with asynchronous fallback. In Theory of Cryptography Conference, pages 623–653. Springer, 2021. doi:10.1007/978-3-030-90459-3_21.
- [13] Giovanni Deligios and Mose Mizrahi Erbes. Closing the efficiency gap between synchronous and network-agnostic consensus. In Advances in Cryptology – EUROCRYPT 2024, pages 432–461, 2024. doi:10.1007/978-3-031-58740-5_15.
- [14] Danny Dolev, Nancy A. Lynch, Shlomit S. Pinter, Eugene W. Stark, and William E. Weihl. Reaching approximate agreement in the presence of faults. J. ACM, 33(3):499–516, May 1986. doi:10.1145/5925.5931.
- [15] Danny Dolev and Rüdiger Reischuk. Bounds on information exchange for byzantine agreement. J. ACM, 32(1):191–204, January 1985. doi:10.1145/2455.214112.
- [16] Danny Dolev and H. Raymond Strong. Authenticated algorithms for byzantine agreement. SIAM Journal on Computing, 12(4):656–666, 1983. doi:10.1137/0212045.
- [17] Cynthia Dwork, Nancy Lynch, and Larry Stockmeyer. Consensus in the presence of partial synchrony. J. ACM, 35(2):288–323, April 1988. doi:10.1145/42282.42283.
- [18] Michael J. Fischer, Nancy A. Lynch, and Michael Merritt. Easy impossibility proofs for distributed consensus problems. In Michael A. Malcolm and H. Raymond Strong, editors, 4th ACM PODC, pages 59–70. ACM, August 1985. doi:10.1145/323596.323602.
- [19] Michael J Fischer, Nancy A Lynch, and Michael S Paterson. Impossibility of distributed consensus with one faulty process. Journal of the ACM (JACM), 32(2):374–382, 1985. doi:10.1145/3149.214121.
- [20] Diana Ghinea, Chen-Da Liu-Zhang, and Roger Wattenhofer. Optimal synchronous approximate agreement with asynchronous fallback. In Proceedings of the 2022 ACM Symposium on Principles of Distributed Computing, PODC’22, pages 70–80, New York, NY, USA, 2022. Association for Computing Machinery. doi:10.1145/3519270.3538442.
- [21] Diana Ghinea, Chen-Da Liu-Zhang, and Roger Wattenhofer. Multidimensional approximate agreement with asynchronous fallback. In Proceedings of the 35th ACM Symposium on Parallelism in Algorithms and Architectures, SPAA ’23, pages 141–151, New York, NY, USA, 2023. Association for Computing Machinery. doi:10.1145/3558481.3591105.
- [22] Diana Ghinea, Chen-Da Liu-Zhang, and Roger Wattenhofer. Brief Announcement: Communication-Optimal Convex Agreement. In The 43rd ACM Symposium on Principles of Distributed Computing (PODC), Nantes, France, June 2024.
- [23] Diana Ghinea, Chen-Da Liu-Zhang, and Roger Wattenhofer. Communication-optimal convex agreement. In Proceedings of the ACM Symposium on Principles of Distributed Computing, PODC ’25, pages 39–49, New York, NY, USA, 2025. Association for Computing Machinery. doi:10.1145/3732772.3733551.
- [24] John T. Gill. Computational complexity of probabilistic turing machines. In Proceedings of the Sixth Annual ACM Symposium on Theory of Computing, STOC ’74, pages 91–95, 1974. doi:10.1145/800119.803889.
- [25] Guy Goren, Yoram Moses, and Alexander Spiegelman. Probabilistic indistinguishability and the quality of validity in byzantine agreement. In Proceedings of the 4th ACM Conference on Advances in Financial Technologies, AFT ’22, pages 111–125, New York, NY, USA, 2023. Association for Computing Machinery. doi:10.1145/3558535.3559789.
- [26] Darya Melnyk, Yuyi Wang, and Roger Wattenhofer. Byzantine Preferential Voting. In 14th Conference on Web and Internet Economics (WINE), Oxford, United Kingdom, December 2018. doi:10.1007/978-3-030-04612-5_22.
- [27] Darya Melnyk and Roger Wattenhofer. Byzantine agreement with interval validity. In 2018 IEEE 37th Symposium on Reliable Distributed Systems (SRDS), pages 251–260, 2018. doi:10.1109/SRDS.2018.00036.
- [28] Hammurabi Mendes, Maurice Herlihy, Nitin Vaidya, and Vijay K Garg. Multidimensional agreement in byzantine systems. Distributed Computing, 28(6):423–441, 2015. doi:10.1007/s00446-014-0240-5.
- [29] Gil Neiger. Distributed consensus revisited. Information Processing Letters, 49(4):195–201, 1994. doi:10.1016/0020-0190(94)90011-6.
- [30] Thomas Nowak and Joel Rybicki. Byzantine Approximate Agreement on Graphs. In 33rd International Symposium on Distributed Computing (DISC 2019), volume 146, pages 29:1–29:17, Dagstuhl, Germany, 2019. doi:10.4230/LIPIcs.DISC.2019.29.
- [31] David Stolz and Roger Wattenhofer. Byzantine Agreement with Median Validity. In 19th International Conference on Principles of Distributed Systems (OPODIS 2015), volume 46, pages 1–14, Dagstuhl, Germany, 2016. doi:10.4230/LIPIcs.OPODIS.2015.22.
- [32] Nitin H. Vaidya and Vijay K. Garg. Byzantine vector consensus in complete graphs. In Panagiota Fatourou and Gadi Taubenfeld, editors, 32nd ACM PODC, pages 65–73. ACM, July 2013. doi:10.1145/2484239.2484256.
Appendix
Appendix A Preliminaries: Missing Proofs
Lemma 3. [Restated, see original statement.]
Let val be a validity property and be a -resilient BA protocol solving val. Consider two input configurations such that . Then, the value agreed upon in any execution of which decides and where the input configuration is must be in .
Proof.
Consider a deciding execution of for . Construct the execution , which is identical to except that its input configuration is instead of . Observe that is an execution of for . Indeed, parties in (which are byzantine) can act as if they are honest and behave exactly as they do in . The honest parties in cannot distinguish between and , so the agreed-upon value in both executions must be the same. Since is a valid execution of for , this value must be in .
Lemma 5. [Restated, see original statement.]
Let val be a solvable validity property and a protocol solving val. Let be a maximal input configuration. If, for every maximal input configuration , the canonical executions of for and decide the same value almost surely, then val is trivial.
Proof.
Note that a countable intersection of events that happen almost surely happens almost surely. We assume the lemma’s condition and want to prove that val is trivial. Because is at most countably infinite, the number of maximal input configurations is at most countably infinite. By taking an intersection of events, one for each maximal , that happen almost surely by the lemma condition, we get that, almost surely, for all the canonical executions of for and decide the same value. Hence, because it happens with probability , it means we can find such that this event happens. That is, for all maximal , the canonical executions of for and with randomness decide the same value. This implies that, for all maximal , the canonical execution of on with randomness decides the same value . Therefore, by Corollary 4, val is trivial.
Appendix B No Cryptographic Setup: Missing Proofs
B.1 Proof of Lemma 9
To prove our statement, we will be running in a larger ring containing multiple copies of each party, as depicted in Figure 6. The ring is constructed from two canonical executions with different input configurations. We will show that parties adjacent in this ring cannot distinguish between the ring and the original setting of three parties, as the third party may be byzantine and simulate the rest of the ring. This will force parties adjacent in the ring to output the same value, which, in turn, guarantees that the two original executions lead to the same output.
Restricting the probabilistic space.
In the following proof, we will consider a countable amount of different executions. Since satisfies probabilistic termination, it means that each of these executions are deciding almost surely. Because the countable union of almost surely events happens almost surely, this means that the event happens almost surely. So it is enough to prove that all canonical execution of in decide the same value to get the proof.
Constructing the ring.
In order to formally describe the construction of the ring, we have to fix two executions with the same randomness. We denote the three parties by , and we consider two arbitrary maximal input configurations . Let , and we consider a canonical execution with input configuration , and a canonical execution with input configuration . By definition of , these two executions are deciding.
As is a deciding execution, there is a number of rounds such that, in , all honest parties have decided the same value within rounds. Similarly, there is an such that, in the canonical execution , all honest parties have decided the same value within rounds. Let , implicitly depends on .
To construct the ring depicted in Figure 6, we make copies of each party . Out of the copies of party , will be the copies of having its input value from and will be the copies of with input from . The copies of are then denoted by , where , , and . The copies indexed by are the ones on the top row of Figure 6, while the copies indexed by are the ones on the bottom row. We now connect these copies via bidirectional communication channels:
-
For and , we add a channel between and , and one between and .
-
Then, to complete the path on the row indicated by index , for every index , we add a channel between and .
-
Similarly, to complete the path on the row indicated by , for each , we add a channel between and .
-
We now connect the two rows and hence complete the ring: we add a channel between and , and one between and .
Outputs of adjacent copies.
We consider a synchronous execution on the ring, where each copy runs as party , using the input value assigned to it in input configuration . We assume that messages are received exactly units of time after being sent. In the lemma below, we show that adjacent copies in the ring, denoted by and , obtain the same output.
Lemma 18.
Consider two parties and that are adjacent in the ring. Then, in execution , and obtain outputs, and they output the same value.
Proof.
Without loss of generality, assume that and are copies of and . We consider an execution of with three parties. In execution , and have the same input values as and . is byzantine and simulates the additional parties in the ring, so they have the same behavior as in execution . All messages are delivered in exactly time, similarly to execution .
We remark that execution and execution are identical. Hence, our execution over the ring is equivalent to running in a synchronous setting with three parties out of which one is corrupted. Therefore, maintains its properties, namely probabilistic termination and agreement, on the ring as well. It follows that and both obtain outputs, and they output the same value.
Outputs on the entire ring.
Lemma 18 establishes that adjacent copies in the ring output the same value in execution . Using induction, we prove that all parties output the same value in . As a consequence, the copies and of each party output . This will imply that, in the two executions and we defined when constructing the ring, all honest parties output the same value.
Lemma 19.
In execution , all parties output, and they output the same value.
Proof.
We prove by induction that, in execution , after rounds, for , parties with are in the same state as party in the canonical execution . The base case considers the very beginning of the executions and , where the parties have not yet received any messages. Their state then is only defined by their input value and . Each party takes its input from , which the case for in execution as well. We thus obtain that parties in the ring have the same input state as party .
For the induction step, assume that our claim holds for , and we prove that it also holds for . Let denote the set of parties for which we proved they were in the same state as in after rounds, and let be the set of parties for which we want to prove that the claim holds after rounds. The set of direct neighbors of (including themselves) in the ring is . Moreover, within one round, parties are only able to receive messages from their direct neighbors. Using the induction hypothesis, we get that parties in receive exactly the same messages at the -th round in execution and , therefore they stay in the same state after round .
As a consequence, and are in the same state after the -th round in executions and respectively. However, we have assumed that all parties in output by round in execution . Therefore, in execution , outputs the same value as in . With a symmetric argument, one can show that parties obtain the same output as in . This enables us to conclude that and decide the same value using Lemma 18.
Assumption on deciding execution.
Before concluding the proof of Lemma 9 using Lemma 19, we need to discuss the assumptions over deciding executions and make sure that event happens almost surely. For every possible input configuration of size three, we consider a finite amount of fixed executions. Moreover, we take into account that there is only at most a countably infinite amount of input configurations (because we assumed was countable). Therefore, we consider in total a countable union of a finite amount of executions, which is countable. Therefore, the event that all these executions are deciding happens almost surely, which concludes the proof of Lemma 9.
B.2 Proof of Theorem 10
Proof.
Assume , and that there is a -secure BA protocol solving val in the synchronous model.
We consider two arbitrary maximal input configurations and . We show that all canonical executions of and almost surely decide on the same output value. Then, Lemma 5 ensures that val is trivial. Similarly to the proof of Theorem 7 and Theorem 8, we use to build a protocol for three parties, denoted by , that matches the setting of Lemma 9. For protocol , we consider the input space and the output space .
To do so, we partition into three sets of size at most each. As shown in Figure 7, in protocol , simulates all the parties in set . ensures that all messages between the simulated parties in get delivered within time. In addition, forwards any message sent from a party it simulates to a party in set () to . When receives this message, it immediately forwards it to the simulated receiver. If has input , the simulated parties in take their input from . Otherwise, they take their input from . When a party in outputs a value , outputs .
Since is a -resilient BA protocol when , we obtain that achieves probabilistic termination and agreement even when one of the three parties is byzantine. Then, Lemma 9 ensures that, almost surely, all deciding canonical executions of lead to the same output value.
Moreover, we remark that, by construction, the canonical execution of with input values matches the canonical execution of for . Similarly, the canonical execution of with input matches the canonical execution of . As a consequence, canonical executions of and decide the same value almost surely. Applying Lemma 5, we conclude that val is trivial.
Appendix C Similarity Condition: Missing Proof
Lemma 13. [Restated, see original statement.]
If a validity property val is solvable in the network-agnostic model, then val satisfies the similarity condition.
Proof.
Assume that is a network-agnostic BA protocol solving val. Consider an input configuration .
In the following proof, we will consider a finite amount of different executions. Since satisfies probabilistic termination, it means that each of these executions are deciding almost surely. Because the finite union of almost surely events happens almost surely, all of these executions will decide almost surely. So, there exists some which we fix such that all the executions below are deciding when ran with randomness .
We first consider the canonical execution of on . As achieves network-agnostic BA, all honest parties output the same value in execution . We want to prove that , hence we show that for every . Using the definition of , we split the analysis as follows:
-
(i)
such that . Consider an execution where the input configuration is and the network is synchronous. Parties in are byzantine, but follow the protocol correctly using the values assigned to them in as inputs. Parties in crash at the start of the execution. Parties in cannot distinguish between and , so the output value must also satisfy .
-
(ii)
such that . First, note that : since and , we obtain that . As val is solvable, Theorem 8 ensures that , and allows us to conclude that .
Let . We consider an execution where the input configuration is and the network is asynchronous. Similarly to execution , parties in are byzantine, but follow the protocol correctly using the values assigned to them in as inputs, and parties in crash at the very beginning of the execution. All messages are delivered in a synchronous way, except for the messages sent from parties in . These are delayed until after party outputs: this is possible as cannot distinguish between and and therefore it has to obtain an output without receiving these messages. In addition, the fact that cannot distinguish between and ensures that the output agreed upon in satisfies .
Therefore, the output in execution satisfies . So when running , if this execution terminates (which happens almost surely), then this value can be used for .
We now explain how to get a Turing computable function out of protocol and this property. We first remark that is a randomized protocol, which can be simulated by a probabilistic Turing machine. However, when time complexity is not taken into account, a probabilistic Turing machine is as expressive as a regular deterministic Turing machine (see Theorem 2 from [24]: for a given number of random bits used, we can try all of them in exponential time). Therefore, we can simulate a deciding execution of using a deterministic Turing machine. Because there are no byzantine parties, we can also remove the public-key infrastructure assumption which was used as a black box (for example, one can replace the signing function with one that returns the message concatenated with the id of the party). This gives us a Turing function to compute .
