Abstract 1 Introduction 2 Related Work 3 Preliminaries 4 Guild Assumptions are not Asymmetric 5 Depth 6 Reliable Broadcast 7 Consensus 8 Conclusion and Future Work References

Weaker Assumptions for Asymmetric Trust

Ignacio Amores-Sesar ORCID Aarhus University, Denmark Christian Cachin ORCID University of Bern, Switzerland Simon Holmgaard Kamp ORCID Ruhr University Bochum, Germany Juan Villacis ORCID University of Bern, Switzerland
Abstract

In distributed systems with asymmetric trust, each participant is free to make its own trust assumptions about others, captured by an asymmetric quorum system. This contrasts with ordinary, symmetric quorum systems and threshold models, where trust assumptions are uniformly shared among participants. Fundamental problems like reliable broadcast and consensus are unsolvable in the asymmetric model if quorum systems satisfy only the classical properties of consistency and availability. Existing approaches overcome this by introducing stronger assumptions. We show that some of these assumptions are overly restrictive, so much so that they effectively eliminate the benefits of asymmetric trust. To address this, we propose a new approach to characterize asymmetric problems and, building upon it, present algorithms for reliable broadcast and consensus that require weaker assumptions than previous solutions. Our methods are general and can be extended to other core problems in systems with asymmetric trust.

Keywords and phrases:
Asymmetric Trust, Quorum Systems, Reliable Broadcast, Consensus
Copyright and License:
[Uncaptioned image] © Ignacio Amores-Sesar, Christian Cachin, Simon Holmgaard Kamp, and Juan Villacis; licensed under Creative Commons License CC-BY 4.0
2012 ACM Subject Classification:
Theory of computation Distributed algorithms
Related Version:
Full Version: https://arxiv.org/abs/2509.09493 [3]
Funding:
This work was supported by the Swiss National Science Foundation (SNSF) under grant agreement Nr. 219403 (Emerging Consensus), by the Initiative for Cryptocurrencies and Contracts (IC3), by the Cryptographic Foundations for Digital Society, CryptoDigi, DFF Research Project 2, Grant ID 10.46540/3103-00077B, and by the European Union, ERC2023-StG-101116713. Views and opinions expressed are those of the author(s) only and do not necessarily reflect those of the European Union. Neither the European Union nor the granting authority can be held responsible for them.
Editors:
Andrei Arusoaie, Emanuel Onica, Michael Spear, and Sara Tucci-Piergiovanni

1 Introduction

Asymmetric trust models, such as those proposed by Damgård et al. [13], Alpos et al. [2], and Losa et al. [22] allow the development of distributed protocols in which each participant can operate under its own trust settings. These algorithms are built on top of asymmetric quorum systems, where each process independently defines its own quorums. The traditional consistency and availability properties must be satisfied by these systems, but as was shown by Li et al. [20], they are not enough to solve fundamental problems like reliable broadcast and consensus. Therefore, the models introduce additional assumptions on the quorums. The protocols for reliable broadcast and consensus of Alpos et al. [2] require the existence of a guild, a set of processes that contains a quorum for each of its members. Li et al. [20] and Losa et al. [22] identify similar conditions. These assumptions can be very strong and restrictive, and while they are sufficient to provide solutions to the aforementioned problems, we will show that they are not necessary. This leads to asymmetric algorithms that work under weaker assumptions, making such systems more flexible and usable.

We start by showing that current assumptions for algorithms such as reliable broadcast or consensus are so restrictive that it becomes unnecessary to use asymmetric trust models altogether. That is, given an asymmetric trust assumption that satisfies such requirements, we can derive an equivalent symmetric trust assumption such that no process will be worse off by adopting it. This result is surprising, considering that Damgård et al. [13] show that asymmetric trust is more expressive than symmetric trust.

To solve this, we introduce the notion of depth of a process and propose a new approach to characterize asymmetric problems based on it. We use this concept to provide more general definitions of unauthenticated, asymmetric, asynchronous, Byzantine reliable broadcast and binary consensus. We also propose new algorithms for these problems that forego the guild requirement in favor of weaker assumptions on depth.

The remainder of this document is organized as follows. Section 2 discusses related work in the asymmetric trust setting. Section 3 introduces the model and reviews key concepts that serve as the foundation for our work. We show in Section 4 that the current assumptions are so strong that they invalidate the benefits of asymmetric trust. Section 5 introduces the concept of depth. Sections 6 and 7 present algorithms for reliable broadcast and consensus that forego the guild assumption in favor of weaker depth assumptions. The proofs of all results are deferred to the full version of this article [3].

2 Related Work

Threshold and symmetric quorum systems are fundamental tools in distributed computing, commonly used to establish the safety and liveness guarantees of various protocols [25, 23, 6, 11]. They constitute a crucial component of many systems in cloud computing [19, 17] and cryptocurrencies [15, 9, 10]. One drawback is that all participants must use the same quorum system, which restricts their freedom to choose who to trust. The asymmetric model, introduced by Damgård et al. [13] and further developed by Alpos et al. [2], represents a novel approach that generalizes the symmetric paradigm. It allows participants to make trust choices of their own, reflecting social connections or other information available to them outside the protocol. Each participant can specify its own quorum system, giving it the freedom to have its own trust assumptions. Amores-Sesar et al. [5] show that algorithms relying on symmetric quorums cannot be applied directly to the asymmetric model, as certain properties do not hold if the underlying quorums are asymmetric. This drives the need to adapt existing symmetric protocols and redefine protocol properties to fit the new model.

Existing work [2] introduces asymmetric versions of relevant primitives like reliable broadcast, binary consensus, and common coin. Amores-Sesar et al. [5] extend this work by developing a DAG-based consensus protocol that relies on such primitives. Losa et al. [22] present another approach to model asymmetric trust. They forego the notion of fail-prone sets and strengthen the definition of quorums, by requiring each quorum to contain a quorum for each member. Li et al. [20] expand on this model and address the topic of which quorum properties are necessary or sufficient to solve core asymmetric problems such as consensus. Sheff et al. [28] propose a variant of the Paxos protocol that incorporates heterogeneous trust assumptions.

Senn and Cachin [27] explore asymmetric trust in the crash-fault scenario and show that, in this setting, asymmetric trust reduces to symmetric trust.

Asymmetric trust introduces novel challenges to the design of distributed protocols. One significant hurdle is that of processes that have wrong friends, that is, the existence of processes that are correct and behave according to the underlying algorithm, but whose trust assumptions do not capture the actual faulty processes. Damgård et al. [13] and Alpos et al. [2] use the term naive to refer to such participants and point out that their presence can lead to safety and liveness issues in asymmetric protocols. To address this, they introduce the concept of a guild, a set of processes that contains a quorum for each member, and provide algorithms for reliable broadcast and consensus that work correctly only in executions that have this structure. They point out that having a quorum system that only satisfies the consistency and availability properties can lead to liveness issues for some processes. In a slightly different model, Li et al. [20] prove that the traditional properties of quorum consistency and availability are not sufficient to solve reliable broadcast and consensus. They introduce a new property, called strong availability, very similar to the notion of a guild, and prove that this property is sufficient to solve the aforementioned problems. They do not comment on the necessity of such a property.

Asymmetric consensus protocols have also transcended into the blockchain space with XRP Ledger [12] (https://xrpl.org) and Stellar [24, 21] (https://stellar.org) as main representatives. In the XRP Ledger, each participant declares its own assumptions by listing other participating nodes from which it considers votes [12, 4]. Stellar uses a similar approach, in which each participant keeps a list of participants it considers important and waits for a suitable majority of them to agree on a transaction before considering it settled [24, 22, 21].

3 Preliminaries

3.1 Model

All algorithms we propose are for the asynchronous unauthenticated setting. We will consider a system of n processes 𝒫={p1,,pn} that interact with each other by exchanging messages. A protocol for 𝒫 consists of a collection of programs with instructions for all processes. They are presented using the event-based notation of Cachin et al. [11]. An execution starts with all processes in a special initial state; subsequently the processes repeatedly trigger events, react to events, and change their state through computation steps. A process that follows its protocol during an execution is called correct. A faulty process, also called Byzantine, may crash or deviate arbitrarily from its specification. We will assume that there is a low-level functionality for sending messages over point-to-point links between each pair of processes. This functionality is accessed through the events of sending and receiving a message. Point-to-point messages are authenticated and delivered reliably among correct processes. Here and from now on, the notation 𝒜 for a system 𝒜2𝒫 , denotes the collection of all subsets of the sets in 𝒜, that is, 𝒜={A|AA,A𝒜}.

3.2 Asymmetric Trust Overview

We consider and expand the asymmetric trust model proposed by Alpos et al. [2]. We summarize here the necessary context for understanding this work; we refer the reader to their paper for a full presentation. In protocols with asymmetric trust, each participant is free to make its own individual trust assumptions about others, captured by an asymmetric quorum system. This contrasts with ordinary, symmetric and threshold quorum systems, where all participants share the same trust assumptions. Given a set of processes 𝒫, an asymmetric fail-prone system 𝔽=[1,,n], where i represents the failure assumptions of process pi, captures the heterogeneous model. Each i is a collection of subsets of 𝒫 such that some Fi with F𝒫 is called a fail-prone set for pi and contains all processes that, according to pi, may at most fail together in some execution [13]. We can, in turn, proceed to define asymmetric Byzantine quorum systems, denoted by .

Definition 1.

An asymmetric Byzantine quorum system for 𝔽 is an array of collections of sets =[𝒬1,,𝒬n] where 𝒬i2𝒫 for i[1,n]. The set 𝒬i2𝒫 is a symmetric quorum system of pi and any set Qi𝒬i is called a quorum for pi. The system must satisfy the following two properties.

Consistency:

The intersection of two quorums for any two processes contains at least one process for which either process assumes that it is not faulty, i.e.,

i,j[1,n],Qi𝒬i,Qj𝒬j,Fijij:QiQjFij.
Availability:

For any process pi and any set of processes that may fail together according to pi, there exists a disjoint quorum for pi in 𝒬i, i.e.,

i[1,n],Fii:Qi𝒬i:FiQi=.

Given an asymmetric quorum system for 𝔽, an asymmetric kernel system for is defined analogously as the array 𝕂=[𝒦1,,𝒦n] that consists of the kernel systems for all processes in 𝒫. A set Ki𝒦i is called a kernel for pi and for each Ki it holds that Qi𝒬i,KiQi, that is, a kernel intersects all quorums of a process.

Given an asymmetric fail-prone system 𝔽, there will exist a valid asymmetric quorum system for 𝔽 if and only if 𝔽 satisfies the B3 condition [13, 2]. This property is defined as follows.

Definition 2 (B3-condition).

An asymmetric fail-prone system 𝔽 satisfies the B3-condition, abbreviated as B3(𝔽), whenever it holds that

i,j[1,n],Fii,Fjj,Fijij:𝒫FiFjFij.

If B3(𝔽) holds, then the canonical quorum system, defined as the complement of the asymmetric fail-prone system, is a valid asymmetric quorum system. This is similar to what happens in the symmetric case, where if the fail-prone system satisfies the Q3 property, the existence of a valid symmetric quorum system 𝒬 is guaranteed [16].

During an execution, the set of processes that fail is denoted by F. The members of F are unknown to the processes and can only be identified by an outside observer and the adversary. A process pi correctly foresees F if Fi, that is, F is contained in one of its fail-prone sets. Based on this information, it is possible to classify processes in three categories.

Faulty:

a faulty process, i.e., piF;

Naive:

a correct process pi, i.e. piF, where Fi; or

Wise:

a correct process pi, i.e. piF, where Fi

Alpos et al. [2] show that naive processes may disrupt the safety and liveness guarantees of some protocols. In order to formalize this notion, they introduced the concept of a guild which is central for many of the algorithms they propose (e.g., reliable broadcast, binary consensus).

Definition 3.

A guild is a set of wise processes that contains one quorum for each of its members. Formally, a guild 𝒢 for 𝔽 and , for an execution with faulty processes F, is a set of processes that satisfies the following two properties.

Wisdom:

𝒢 is a set of wise processes, that is,

pi𝒢:Fi.
Closure:

𝒢 contains a quorum for each of its members, that is,

pi𝒢:Qi𝒬i:Qi𝒢.

Alpos et al. [2] provide reliable broadcast and binary consensus implementations which function only in executions that contain a guild. In relation to this, Definition 4 presents the notion of a tolerated system, originally introduced by Alpos et al. [2]. It is built on top of tolerated sets, which are sets that contain all elements outside of a guild. This portrays the resilience of the trust assumptions, as even when all processes in one of the tolerated sets fail, there is still a guild in the system. This structure is used by Alpos et al. [2] and Zanolini [29] in their construction of several asymmetric protocols.

Definition 4 (Tolerated system [2]).

Given an asymmetric Byzantine quorum system and an execution with faulty processes F, a set of processes T is called tolerated (by ) if a non-empty guild 𝒢 for F and exists such that T=𝒫𝒢.

The tolerated system 𝒯 of an asymmetric Byzantine quorum system is the maximal collection of tolerated sets, where F ranges over all possible executions.

Lemma 5, which is crucial for the construction presented in Section 4, shows that if there is an asymmetric fail-prone system 𝔽 such that B3(𝔽) holds, then Q3(𝒯) also holds. This means that 𝒯 is a valid symmetric fail-prone system [16].

Lemma 5 ([2]).

Let be an asymmetric Byzantine quorum system among processes 𝒫 with asymmetric fail-prone system 𝔽=¯, i.e., such that is a canonical asymmetric Byzantine quorum system, and let 𝒯 be the tolerated system of . If B3(𝔽) holds, then 𝒯 is a valid symmetric fail-prone system, i.e., Q3(𝒯) holds.

3.3 Quorum-based Algorithms

In the following sections, we will give results regarding the existence of algorithms to solve problems such as reliable broadcast and consensus. To do this, we must first define what we mean by an algorithm. We will consider all algorithms to be quorum-based algorithms. Definition 6 formalizes this notion. It is derived from the definitions used by Losa et al. [22] and Li et al. [20] , but it is adapted to fit the asymmetric model of Alpos et al. [2]. We use the term initiator of the execution to refer to the sole process that triggers the execution of an algorithm. In our work, this only applies within the context of reliable broadcast, where the initiator is the process that broadcasts a value. In consensus, there is no single initiator because all processes propose a value.

Definition 6 (Quorum-based algorithm).

Given a distributed algorithm A, processes 𝒫, and asymmetric quorum system , we will say that A is quorum-based if the following properties hold

  • In any execution where a correct process pi issues a response, there is a quorum Qi𝒬i such that pi received a message from each member of Qi.

  • If the state of a correct process pi changes upon receiving a message from some process pj, then there is a Qi𝒬i such that pjQi or pj is the initiator of the execution of A.

  • For every execution where a correct process pi produces an output, there exists an execution where pi only receives messages from the members of one of its quorums Qi𝒬i and the initiator and pi outputs the same value.

4 Guild Assumptions are not Asymmetric

In the asymmetric trust setting, Li et al. [20] show that a quorum system satisfying the classical properties of consistency and availability alone does not suffice to solve fundamental problems such as reliable broadcast or consensus. The heterogeneous views of the system make it necessary to assume more structure. Different approaches have reached similar conclusions about the assumptions needed to address these problems under asymmetric trust. Alpos et al. [2] require the existence of a guild, while Li et al. [20] propose that the system must satisfy the strong availability property. This is closely related to the idea of a guild, as it also requires the existence of a well-behaved group of processes that includes a quorum for every participant. In this section, we examine the implications of these assumptions, focusing on the model proposed by Alpos et al. [2].

Guilds are a strong assumption, essentially requiring all members to have common beliefs, which goes against the idea of asymmetric trust. We show that for any asymmetric Byzantine fail-prone system 𝔽, if a guild exists in an execution, then we can build an equally valid symmetric trust assumption from 𝔽. This means that, in such cases, asymmetric trust reduces to symmetric trust.

In the crash-fault model, Senn and Cachin [27] already show that given an asymmetric fail-prone system 𝔽, it is possible to construct a symmetric fail-prone system from 𝔽 such that if all processes adopt as their trust assumption, no process will be worse off. This result implies that there is no need for asymmetric trust in that setting. We extend this by showing that a similar scenario occurs in the Byzantine fault model for all executions with a guild. This effectively invalidates the advantages of asymmetric trust for the algorithms proposed by Alpos et al. [2] which rely on the existence of a guild.

We now show how to construct a symmetric fail-prone system from an asymmetric fail-prone system 𝔽, such that in all executions with a guild, is as expressive as 𝔽. We will build it based on the notion of the tolerated system, presented in Section 2 and used by Alpos et al. [2] and Zanolini [29] in their consensus protocols.

Definition 7 (Tolerated Symmetric Fail-Prone System).

Let 𝔽 be an asymmetric fail-prone system that satisfies B3(𝔽), be its associated canonical quorum system and 𝒯 be the tolerated system derived from according to Definition 4. We interpret 𝒯 as a symmetric fail-prone set and denote it by ^, that is, ^=𝒯, with a one-to-one correspondence between the tolerated sets and fail-prone sets.

From Lemma 5 we know that the tolerated symmetric fail-prone system satisfies the Q3 property and therefore there will be at least one valid symmetric Byzantine quorum system associated to it.

Lemma 8.

Let 𝔽 be an asymmetric fail-prone system that satisfies B3(𝔽), 𝒯 be the tolerated system derived from 𝔽 and ^ be the tolerated symmetric fail-prone system derived according to Definition 7. Given an execution with a guild 𝒢 and faulty processes F, then F^.

Proof.

By Definition 4, there exists a tolerated set T=𝒫𝒢 such that T𝒯. Since F𝒢= we know that FT and consequently there exists a fail-prone set F^ such that T=F. Therefore, the set of faulty processes will be considered by the fail-prone system ^.

Theorem 9.

Let 𝔽 be an asymmetric fail-prone system that satisfies B3(𝔽). Given an execution with faulty processes F and at least one guild 𝒢, it is possible to derive a symmetric fail-prone system from 𝔽 such that F.

Proof.

We first identify the tolerated symmetric fail-prone system ^ according to Definition 7. Since B3(𝔽) we know that Q3(^) and therefore it is a valid symmetric Byzantine fail-prone system. Applying Lemma 8, we know that if we are in an execution with a guild 𝒢 and faulty processes F, then F^. Therefore, by taking =^ it is possible to construct a symmetric fail-prone system derived from 𝔽 such that F.

Theorem 9 shows that for executions with a guild, every process is at least as well off using the symmetric quorum system instead of 𝔽. For a wise process pi the situation will remain the same regardless of the quorum system chosen. With the asymmetric system Fi will hold, while with the symmetric alternative F. For naive processes the situation improves, as now the faulty processes will be considered in their trust assumption. Thus, there is no reason for a process not to adopt the derived symmetric fail-prone system . Building can be computationally expensive because it requires computing 𝒯. However, existing asymmetric consensus protocols [2, 29] also require computing 𝒯, so our approach is no more costly than current solutions.

Hence, if a guild is needed to solve a problem in the asymmetric setting, there exists a way to circumvent this and use any existing symmetric algorithm while obtaining the same guarantees that an asymmetric algorithm would provide. Therefore, if a problem can only be solved if a guild exists, the interest in using asymmetric trust to solve it decreases. This motivates the search for better algorithms for problems such as reliable broadcast and consensus, where the only known asymmetric algorithms require a guild.

One limitation of this result is that it assumes knowledge of the trust assumptions for all processes (𝔽). Although this assumption holds in the Damgård et al. [13] and Alpos et al. [2] models, it is not required in other asymmetric trust models [22]. We also note that knowledge of the faulty processes F is not required to derive the symmetric fail-prone system presented in Theorem 9.

5 Depth

In the symmetric world, processes are classified as correct or faulty. This suffices to express the properties of algorithms and capture all potential states of a process. In the asymmetric world this is not enough, a process might be correct but have incorrect trust assumptions. Damgård et al. [13] and Alpos et al. [2] address this problem by introducing the notions of naive, wise, and guilds.

Existing protocols for reliable broadcast and consensus in the Alpos et al. [2] model require a guild to ensure safety and liveness. The results of Section 4, coupled with the inherent rigidity of having this kind of assumptions, motivate the search for new asymmetric algorithms that forego such assumptions. In order to do this, we introduce a new way to describe the quality of processes, based on how much they can rely on other processes during an execution. We denote this concept as the depth of a process. We then show how it can be used to characterize asymmetric problems in a more fine-grained manner. Definition 10 introduces this notion. This approach allows to generalize the concept of wise process or guild member and introduces more expressivity to the system.

Definition 10 (Depth of a process).

For an execution, we recursively define the notion of a correct process having depth d as follows

  • Any correct process pi has depth 0.

  • Additionally, a correct process pi has depth d1 if it has a quorum such that all processes contained in it have depth at least d1, i.e.,

    Q𝒬i,pjQ: pj is correct, has depth s, and sd1.

Note that a process with maximal depth d also has depth d for all 0dd. We will focus on the maximal depth of a process. In the following sections, any reference to the depth of a process should be understood as its maximal depth. Following the terminology of Damgård et al. [13], naive processes have depth 0, wise processes have depth at least 1, and processes in a guild have infinite depth.

In Sections 6 and 7 we show how the properties of protocols can be adapted to take into account the depth of processes. We modify them to show that some property must hold for all processes with depth at least d. For example, the totality property of reliable broadcast is updated to state that all processes with depth d eventually deliver a message.

6 Reliable Broadcast

Section 4 shows that if an execution includes a guild, we can convert asymmetric trust assumptions into symmetric ones. This means that if a problem can only be solved in executions with a guild, the interest in using asymmetric trust to solve it decreases. So far, the only known protocols for reliable broadcast and consensus in the Alpos et al. [2] model require the existence of a guild. This motivates the search for new algorithms that work without relying on guild assumptions for these problems. We start this search with the Byzantine reliable broadcast problem. Our approach weakens the trust assumptions needed and eliminates the need for a guild. Definition 11 presents a way to characterize reliable broadcast based on the depth of processes. Its properties are specific to processes that have at least a certain maximal depth.

Definition 11 (Depth-characterized asymmetric Byzantine reliable broadcast).

A protocol for asymmetric Byzantine reliable broadcast with sender ps and depth d, shortened as RB[d], defined through the events dar-broadcast(m) and dar-deliver(m) satisfies the following properties:

  • Validity: If a correct process ps dar-broadcasts a message m, then all processes with depth d eventually dar-deliver m.

  • Consistency: If some process with depth d dar-delivers m and another process with depth d dar-delivers m, then m=m.

  • Integrity: Every process with depth d dar-delivers m at most once. Moreover, if the sender ps is correct and the receiver has depth d, then m was previously dar-broadcast by ps.

  • Totality: If a process with depth d dar-delivers some message, then all processes with depth d eventually dar-deliver a message.

The reliable broadcast proposed by Alpos et al. [2] is closely related to RB[], although not as general. RB[] guarantees a solution for all processes with depth , whereas the protocol by Alpos et al. [2] only guarantees a solution for those processes with depth that also belong to the maximal guild. That is, processes with depth that are members of a guild, but not of the maximal guild, are not guaranteed to receive a solution.

A natural question arises, which is the minimum depth needed to implement the different primitives. A low depth not only corresponds to weaker asymmetric assumptions, but also reflects, to a certain level, the communication complexity of an algorithm. Lemma 12 shows that it is not possible to solve reliable broadcast for depths 0 or 1.

Lemma 12.

There is no quorum-based algorithm that solves RB[1].

Proof.

Consider a system with processes p1,p2,p3,p4,p5 and p6 and the following fail-prone system.

𝔽D:1={{1,2,5,6},{1,2,3}}2={{1,2,5,6},{1,2,3}}3={{1,2,4}}4={{1,2,3}}5={{1,2,4}}6={{1,2,4}}

It satisfies the B3 property and therefore the following canonical quorum system is valid.

D:𝒬1={{3,4},{4,5,6}}𝒬2={{3,4},{4,5,6}}𝒬3={{3,5,6}}𝒬4={{4,5,6}}𝒬5={{3,5,6}}𝒬6={{3,5,6}}

Let the processes p1, p2, p3, p4 be correct and p5, p6 be Byzantine. Since p1 and p2 have a quorum composed only of correct processes ({3,4}) they have depth 1. We now show an execution in which p1 dar-delivers while p2 does not, which breaks the totality property of RB[1].

Firstly consider an execution E0 in which p5 dar-broadcasts value 0, all processes behave according to the algorithm. Processes p1 and p2 will deliver value 0. From Definition 6 we know that there is an equivalent execution E where p1 and p2 deliver the same value and only receive messages from the processes in their quorum {4,5,6} and p5.

Now consider an execution E in which processes p5 and p6 behave towards p4 like in E. Note that p4 will behave like in E since at every step it will receive the same messages from the same processes as it did in E. Let p5 and p6 also behave towards p2 like in E and send no messages towards all other processes. Process p3 does not begin the execution since it never receives any message from the initiator (Byzantine) nor any member of one of its quorums (processes 3, 5 or 6). Process p2 will deliver value 0 as it receives the same messages from the same processes as in E. On the contrary, process p1 will not deliver any value since it will never receive messages from all processes in one of its quorums, which would contradict Definition 6. This comes from the fact that p3 will never send any message and that p5 and p6 are Byzantine and will not send it any message. Therefore, p2 delivers a value but p1 does not, which breaks the totality property of RB[1].

Lemma 13 shows that if an algorithm solves RB[s] then it also solves RB[s] for all ss. This simplifies the search for a solution by reducing it to finding an algorithm that works for the minimal value of s. Since there are no algorithms that can solve RB[1], we must search for a protocol that solves the problem for processes with a depth of at least 2.

Lemma 13.

If a quorum-based algorithm A solves RB[d] then it solves RB[d] for all d’>d.

Proof.

Suppose that an algorithm A solves RB[d]. Denote by S the set of all processes that have depth d and by S the set of all processes that have depth d’. Since SS then all properties of RB[d] will be satisfied for the processes in S after executing A. Therefore A also solves RB[d].

Algorithm 1 presents a solution for RB[3]. Every process waits to receive a quorum of Readyafterecho messages associated to the same message m and round r before delivering m. A process with depth 3 will only receive such a quorum if there exists a set of processes Q (which form a quorum for a wise process) that can attest that the sender indeed sent the value m. Since there will be an attesting quorum for every process that delivers, and since quorums for wise processes intersect in at least one correct process, we can deduce that all processes with depth 3 that deliver a value m will deliver the same value. In addition, we use a technique similar to Bracha’s kernel amplification [8] to ensure that if a valid process delivers then all valid processes will deliver. The arrays in lines 4, 5, 6, and 7 are hashmaps, so even though they are depicted as having infinite size they are actually sparsely populated. The algorithm has a latency of 3 asynchronous rounds in the good case and 5 in the bad case. Its correctness is proved in Theorem 14. The complete proofs of the result and the supporting lemmas are presented in the full version [3]. The existence of an algorithm to solve RB[2] remains an open question.

Algorithm 1 Depth 3 asymmetric reliable broadcast with sender ps (RB[3]) (process pi).
Theorem 14.

Algorithm 1 solves RB[3].

Corollary 15.

Algorithm 1 solves RB[d] for any d3.

In Algorithm 1 and Definition 11, we assume that all correct processes start the execution. This allows us to focus solely on characterizing the depth of the processes that complete the execution. However, in more complex scenarios, such as when protocols are composed sequentially, it is important to also characterize the depth of the processes that start the execution.

For example, consider two protocols executed one after the other. If only processes with depth d complete the first protocol, we cannot assume that all correct processes will initiate the second; we can only rely on those with depth d to do so. This highlights the need to explicitly define both the starting and ending depths of participating processes, especially in composed protocols.

In the case of reliable broadcast, we treat it as a standalone algorithm and thus omit this distinction. In later sections, we will define protocols using two depth parameters: one for the processes that begin the execution, and one for those that finish.

7 Consensus

We adapt the consensus problem to the depth paradigm and propose an algorithm that solves it for all processes with a minimum depth of at least 10. We follow an approach similar to the one proposed by Abraham et al. [1], who use a round-based algorithm composed of a binding crusader agreement and a common coin. However, for reasons that will be discussed in Section 7.3, we replace binding crusader agreement with a binding graded agreement protocol which allows parties to provide multiple input. For this purpose, we introduce depth-characterized versions of these primitives in Sections 7.1 and 7.2, which we use as subprotocols inside the main consensus algorithm.

It is at this point that the need to characterize the depth of starting and finishing processes arises. The consensus protocol first calls the binding graded agreement, and then the common coin. Only processes that finish the former will be able to make the call to the latter. Because of this, we need to take into account that not all correct processes can start executing a protocol. We introduce two parameters to characterize the depth of protocols: d to refer to the depth of processes that start the execution, and d to refer to the depth of processes that finish the execution. We will say that an algorithm works if, in case all processes with depth d start the execution, all processes with depth d satisfy the required properties. In case we assume that all correct processes start (i.e., d=0), as is the case for standalone protocols (like consensus and reliable broadcast), we will ignore the d parameter.

7.1 Common Coin

The existing asymmetric common coin protocol proposed by Alpos et al. [2] has issues that motivate the development of a new protocol. It is not a purely asymmetric protocol, as each process first constructs the tolerated system, which is a symmetric fail-prone system, and executes the protocol based upon it. This means that the protocol is actually symmetric and is not suitable for asymmetric applications. We address this by first redefining the problem to fit the depth paradigm, shown in Definition 16, and propose a modified version of the scheme introduced by Alpos et al. [2], which solves the problem for all processes with depth at least d+1, as long as all processes with depth d start the execution. The parameter for all processes starting the protocol is needed since it will be used as part of a pipeline of protocols, which means that only the processes that finish the preceding protocol are guaranteed to start executing the common coin.

Definition 16 (Depth-characterized asymmetric common coin).

A protocol for common coin, for processes with depth d and d, defined by the events release-coin(round) and output-coin(c), shortened as CC[d,d], satisfies the following properties:

Termination:

If all processes with depth d call release-coin, then every process with depth d eventually executes output-coin.

Unpredictability:

No process has information about the value of the coin before at least one process with depth d has called release-coin.

Matching:

If a process with depth d executes output-coin(c) and another process with depth d executes output-coin(c), then c=c.

No bias:

The distribution of the coin is uniform over .

Algorithm 2 provides a solution to the common coin taking any value d and d=d+1. In our consensus construction, we require CC[8, 9] in particular. The common coin we design is strong and it follows the approach of Rabin [26] and assumes that coins are predistributed by a trusted dealer. The scheme uses Benaloh-Leichter [7] secret sharing, such that the coin is additively shared within every quorum. The dealer shares one coin for every possible round of the protocol and when a process receives a share it can verify that it was indeed created by the dealer. This can be done using standard digital signatures but is outside the scope of this paper. Alpos et al. [2] follow the same approach in their scheme. Theorem 17 proves the correctness of the algorithm. The proof of this result is presented in the full version of the article [3].

Algorithm 2 Asymmetric common coin (code for pi).
Theorem 17.

Algorithm 2 implements CC[d, d+1].

7.2 Binding Graded Agreement

Following the paradigm of Abraham et al. [1], we will build the consensus protocol relying on an intermediate agreement protocol. They use a binding crusader agreement protocol, but given our asymmetric scenario, we require a more complex intermediate agreement protocol. We will use a binding graded agreement protocol based on the justified proxcensus protocol of Kamp [18]. Definition 18 presents the properties that such a primitive must satisfy to reflect that only a fraction of correct processes might start the execution. This is of use in the round-based context where this primitive will be used, as we can only guarantee that processes with a certain depth will be alive in consensus rounds other than the first.

Our depth-characterized asymmetric binding graded agreement takes as input one or multiple values and produces as output a value with a corresponding grade. A correct process may start the protocol with a given input and later provide an additional input to the protocol. This detail is crucial for the liveness of the consensus protocol, which will be explained later.

In contrast to binding crusader agreement, which outputs a value in {0,,1}, our binding graded agreement additionally outputs a grade between {0,1,2} which signifies the confidence of the process in the decision. The possible outputs are (1,2),(1,1),(,0),(0,1),(0,2) and the protocol must guarantee that the outputs of any two processes with a certain depth are the same or next to each other in the previously provided order. This is made explicit in the graded agreement property.

Definition 18 (Depth-characterized asymmetric binding graded agreement).

A protocol for binding graded agreement with depths d and d, defined through the events bga-propose(v) and bga-decide(v,g), shortened as BGA[d,d], satisfies the following properties:

Strong Termination:

If there exists a value v such that for each process pi with depth d+1, a kernel Ki𝒦i of correct processes inputs v, then every process with depth d eventually bga-decides.

Validity:

If a process with depth d bga-decides on a value different from (v,2), then a process with depth d bga-proposed 1v.

Graded Agreement:

If two processes with depth d bga-decide (v,g) and (v,g), then 1) |gg|1, 2) v= if and only if g=0, and 3) if min(g,g)>0 then v=v.

Binding:

Let time τ be the first time at which there is a process with depth d that bga-decides. There is a value b{0,1}, defined at time τ, such that no process with depth d bga-decides (1b,) in any extension of this execution.

We note that strong termination implies that if all correct processes bga-propose a value, then every process with depth d eventually bga-decides and prove it formally in the full version of this paper [3]. However, we need the stronger requirement for composition, as processes with depth 0 cannot be guaranteed to obtain an input whenever this depends on the output of another protocol. Algorithm 3 presents a solution to this problem for d=2 and d=6. We prove its correctness in Theorem 19. The proof is presented in the full version of this paper [3].

Theorem 19.

Algorithm 3 solves depth-characterized asymmetric binding graded agreement with d=2 and d=8.

To simplify the protocol description, we introduce the following notion of a valid dar-delivery of a vote, which is a concrete instantiation of the justifiers needed in the justified proxcensus protocol by Kamp [18].

Definition 20 (Valid dar-deliver).

When we say that the dar-delivery of a vote message [vote,,vj,Qj] is valid in the view of a process pi, we mean that if =0, then for each pkQj a message [quorum,vj] from pk was dar-delivered. Otherwise, for >0 we require that for each pkQj a message [vote,1,vk,Qk] from pk was validly dar-delivered such that the average of the votes included in the set {vkpkQj} is equal to vj/2.

In other words, we require that pi should receive messages that would cause it to vote for vj if Qj was its own quorum.

The usage of reliable broadcast for these messages guarantees that if a process with some depth delivers a message, the same message will be eventually delivered by any other process with the appropriate depth. This prevents faulty processes from sending incorrect information to a subset of the processes. In the full version of this paper [3], we show that the set of all votes v and v that belong to the same round and are validly dar-delivered in the view of a process with depth 2: |vv|1. Similarly, we show that if no party with depth 2 inputs a value different from v, then all vote messages that are validly dar-delivered at parties with depth 2 in round must include a vote for v2. As such, receiving a validly dar-delivered vote, corresponds to receiving a vote justified by threshold signatures in the justified proxcensus protocol by Kamp [18].

Algorithm 3 Asymmetric binding graded agreement (code for pi).

7.3 Consensus

Definition 21 introduces the concept of depth to the asymmetric consensus problem. We propose a consensus algorithm using the round-based paradigm of Abraham et al. [1]. Each round consists of a call to the binding graded agreement and common coin primitives presented earlier. If the values obtained from the two primitives match, then the processes deliver it; otherwise, another round is executed.

We make a small addition to the common coin and binding graded agreement calls. When one of these sub-protocols is triggered, it is done so with a round tag. This is used to keep track of the round that is running and does not interfere with any details of the sub-protocols. When the protocol call returns, it will also include the tag with which it was called.

Definition 21 (Depth-characterized asymmetric Byzantine consensus).

A protocol for asymmetric Byzantine consensus, shortened as C[d], defined through the events c-propose(val) and c-decide(val), satisfies:

Termination:

Every process with depth d eventually c-decides with probability 1.

Validity:

If all correct processes c-propose the same value val, then no processes with depth d c-decides 1val.

Agreement:

No two processes with depth d c-decide different values.

A difference with respect to symmetric round-based protocols is that not all processes will finish all the sub-protocol calls. Only processes with depth 8 can complete the graded agreement, and only those with depth 9 also finish the subsequent common coin. If we follow a naive approach, in which only those processes that completed the previous round participate in the next, the required depth increases with the number of rounds.

We address this fact with the strong termination property of binding grading agreement, which guarantees liveness, even when not every process starts the execution of the protocol. Without this element, after each round, liveness could only be guaranteed for processes with higher and higher depths. Since such a protocol can have executions with infinite length [14], we would only be able to provide guarantees for processes with infinite depth, which goes against our objectives here.

A process may execute multiple rounds in parallel. This is enabled by the usage of arrays (send, sent) to store the process states separately for each round. This design ensures that the process can continue sending messages for every round it has initiated, which may be needed by other processes in the system.

Algorithm 4 presents a solution to the asymmetric consensus problem for all processes with depth 9. It relies on the binding graded agreement and common coins previously introduced. Theorem 22 proves that it satisfies the properties described in Definition 21. Since we want to prove the properties for all processes with depth 10, in the proofs, we will assume that there is at least one such process. The proof of the algorithm and intermediate results are deferred to the full version of this paper [3].

Theorem 22.

Algorithm 4 solves C[10].

Algorithm 4 Asymmetric binary consensus (code for pi).

8 Conclusion and Future Work

Prior to this work, solutions to problems such as reliable broadcast and consensus relied on guild assumptions. Theorem 9 shows that this assumption effectively reduces to the existence of a symmetric system, constructed from the original assumptions, that provides equivalent or stronger guarantees. In other words, existing solutions are not well-suited for genuinely asymmetric settings.

To overcome this limitation, we introduced a more fine-grained way to characterize asymmetry through the notion of depth. We proved that reliable broadcast can be solved for all processes with depth at least 3, and consensus for processes with depth at least 9. This significantly relaxes the requirements compared to prior work by Alpos et al. [2], which established feasibility only for processes with infinite depth (i.e., guild members).

The exact minimum depth required for solving asymmetric reliable broadcast and consensus remains an open problem. For reliable broadcast, the lower bound is either 2 or 3; for consensus, it lies between 1 and 10. Determining these thresholds is crucial, as a lower depth implies less reliance on other processes and more flexible systems.

Finally, an important direction for future research is to explore whether the concepts and techniques introduced here extend to other asymmetric trust models [20, 22].

References

  • [1] Ittai Abraham, Naama Ben-David, and Sravya Yandamuri. Efficient and adaptively secure asynchronous binary agreement via binding crusader agreement. In PODC, pages 381–391. ACM, 2022. doi:10.1145/3519270.3538426.
  • [2] Orestis Alpos, Christian Cachin, Björn Tackmann, and Luca Zanolini. Asymmetric distributed trust. Distributed Comput., 37(3):247–277, 2024. doi:10.1007/S00446-024-00469-1.
  • [3] Ignacio Amores-Sesar, Christian Cachin, Simon Holmgaard Kamp, and Juan Villacis. Weaker assumptions for asymmetric trust. arXiv preprint arXiv:2509.09493, 2025.
  • [4] Ignacio Amores-Sesar, Christian Cachin, and Jovana Micic. Security analysis of ripple consensus. In OPODIS, volume 184 of LIPIcs, pages 10:1–10:16. Schloss Dagstuhl – Leibniz-Zentrum für Informatik, 2020. doi:10.4230/LIPICS.OPODIS.2020.10.
  • [5] Ignacio Amores-Sesar, Christian Cachin, Juan Villacis, and Luca Zanolini. Dag-based consensus with asymmetric trust. In PODC, pages 151–161. ACM, 2025. doi:10.1145/3732772.3733527.
  • [6] Hagit Attiya and Jennifer L. Welch. Distributed computing - fundamentals, simulations, and advanced topics (2. ed.). Wiley series on parallel and distributed computing. Wiley, 2004.
  • [7] Josh Cohen Benaloh and Jerry Leichter. Generalized secret sharing and monotone functions. In CRYPTO, volume 403 of Lecture Notes in Computer Science, pages 27–35. Springer, 1988. doi:10.1007/0-387-34799-2_3.
  • [8] Gabriel Bracha and Sam Toueg. Asynchronous consensus and broadcast protocols. J. ACM, 32(4):824–840, 1985. doi:10.1145/4221.214134.
  • [9] Ethan Buchman, Jae Kwon, and Zarko Milosevic. The latest gossip on BFT consensus. CoRR, abs/1807.04938, 2018. arXiv:1807.04938.
  • [10] Vitalik Buterin and Danny Ryan. Ethereum 2.0: Proof of stake and shard chains. https://ethereum.org/en/eth2/, 2018. Accessed: 2025-08-19.
  • [11] Christian Cachin, Rachid Guerraoui, and Luís E. T. Rodrigues. Introduction to Reliable and Secure Distributed Programming (2. ed.). Springer, 2011. doi:10.1007/978-3-642-15260-3.
  • [12] Brad Chase and Ethan MacBrough. Analysis of the XRP ledger consensus protocol. CoRR, abs/1802.07242, 2018. arXiv:1802.07242.
  • [13] Ivan Damgård, Yvo Desmedt, Matthias Fitzi, and Jesper Buus Nielsen. Secure protocols with asymmetric trust. In ASIACRYPT, volume 4833 of Lecture Notes in Computer Science, pages 357–375. Springer, 2007. doi:10.1007/978-3-540-76900-2_22.
  • [14] Michael J. Fischer, Nancy A. Lynch, and Mike Paterson. Impossibility of distributed consensus with one faulty process. J. ACM, 32(2):374–382, 1985. doi:10.1145/3149.214121.
  • [15] Yossi Gilad, Rotem Hemo, Silvio Micali, Georgios Vlachos, and Nickolai Zeldovich. Algorand: Scaling byzantine agreements for cryptocurrencies. In SOSP, pages 51–68. ACM, 2017. doi:10.1145/3132747.3132757.
  • [16] Martin Hirt and Ueli M. Maurer. Player simulation and general adversary structures in perfect multiparty computation. J. Cryptol., 13(1):31–60, 2000. doi:10.1007/S001459910003.
  • [17] Patrick Hunt, Mahadev Konar, Flavio Paiva Junqueira, and Benjamin C. Reed. Zookeeper: Wait-free coordination for internet-scale systems. In USENIX ATC. USENIX Association, 2010. URL: https://www.usenix.org/conference/usenix-atc-10/zookeeper-wait-free-coordination-internet-scale-systems.
  • [18] Simon Holmgaard Kamp. A new way to achieve round-efficient asynchronous byzantine agreement. IACR Cryptol. ePrint Arch., page 143, 2025. URL: https://eprint.iacr.org/2025/143.
  • [19] Avinash Lakshman and Prashant Malik. Cassandra: a decentralized structured storage system. ACM SIGOPS Oper. Syst. Rev., 44(2):35–40, 2010. doi:10.1145/1773912.1773922.
  • [20] Xiao Li, Eric Chan, and Mohsen Lesani. Quorum subsumption for heterogeneous quorum systems. In DISC, volume 281 of LIPIcs, pages 28:1–28:19. Schloss Dagstuhl – Leibniz-Zentrum für Informatik, 2023. doi:10.4230/LIPICS.DISC.2023.28.
  • [21] Marta Lokhava, Giuliano Losa, David Mazières, Graydon Hoare, Nicolas Barry, Eli Gafni, Jonathan Jove, Rafal Malinowsky, and Jed McCaleb. Fast and secure global payments with stellar. In SOSP, pages 80–96. ACM, 2019. doi:10.1145/3341301.3359636.
  • [22] Giuliano Losa, Eli Gafni, and David Mazières. Stellar consensus by instantiation. In DISC, volume 146 of LIPIcs, pages 27:1–27:15. Schloss Dagstuhl – Leibniz-Zentrum für Informatik, 2019. doi:10.4230/LIPICS.DISC.2019.27.
  • [23] Dahlia Malkhi and Michael K. Reiter. Byzantine quorum systems. Distributed Comput., 11(4):203–213, 1998. doi:10.1007/S004460050050.
  • [24] David Mazieres. The stellar consensus protocol: A federated model for internet-level consensus. Stellar Development Foundation, 32:1–45, 2015. Available online from https://stellar.org/learn/stellar-consensus-protocol.
  • [25] Moni Naor and Avishai Wool. The load, capacity, and availability of quorum systems. SIAM J. Comput., 27(2):423–447, 1998. doi:10.1137/S0097539795281232.
  • [26] Michael O. Rabin. Randomized byzantine generals. In FOCS, pages 403–409. IEEE Computer Society, 1983. doi:10.1109/SFCS.1983.48.
  • [27] Michael Senn and Christian Cachin. Asymmetric failure assumptions for reliable distributed systems. In PaPoC@EuroSys, pages 8–14. ACM, 2025. doi:10.1145/3721473.3722143.
  • [28] Isaac C. Sheff, Xinwen Wang, Robbert van Renesse, and Andrew C. Myers. Heterogeneous paxos. In OPODIS, volume 184 of LIPIcs, pages 5:1–5:17. Schloss Dagstuhl – Leibniz-Zentrum für Informatik, 2020. doi:10.4230/LIPICS.OPODIS.2020.5.
  • [29] Luca Zanolini. Asymmetric Trust in Distributed Systems. Inaugural dissertation, University of Bern, Faculty of Science, Bern, Switzerland, July 2023. Defense date: 6 July 2023. doi:10.48549/4481.