Federated Byzantine Agreement (FBA) is a consensus mechanism where participants, or nodes, do not require a global view of the entire network. Instead, each node selects a set of other nodes it trusts, forming its quorum slice. Agreement is reached when a sufficient number of these overlapping trust relationships, or quorums, converge on a decision. This model, formalized in the Stellar Consensus Protocol (SCP), enables decentralized governance without proof-of-work mining, making it highly energy-efficient and suitable for systems where participants have known identities or reputations.
Federated Byzantine Agreement (FBA)
What is Federated Byzantine Agreement (FBA)?
Federated Byzantine Agreement (FBA) is a class of consensus protocols where nodes form trust-based subsets, called quorum slices, to achieve agreement in a decentralized network.
The core innovation of FBA is its flexible trust model. Unlike traditional Byzantine Fault Tolerance (BFT) systems that require a fixed, known set of validators, FBA allows each node to define its own quorum slice. This creates a decentralized web of trust where no single entity controls membership. Consensus is achieved through quorum intersection, a mathematical guarantee that ensures any two quorums share at least one honest node, preventing the network from forking. This structure is inherently more open and adaptable than permissioned BFT systems.
FBA's primary implementation is the Stellar Consensus Protocol (SCP), which powers the Stellar network for cross-border payments. In SCP, nodes run a process called Federated Voting, which includes the phases nominate and ballot to agree on transaction sets. Other projects exploring FBA-like models include Ripple (XRP Ledger) with its Unique Node List (UNL) system, though its consensus mechanism has distinct centralized characteristics. FBA is particularly well-suited for consortium blockchains and financial networks where latency and finality are critical.
Key advantages of FBA include low energy consumption, fast transaction finality (typically 3-5 seconds), and flexible security assumptions. Its main trade-offs involve complex configuration of quorum slices and potential centralization risks if trust relationships become too concentrated. Compared to Proof-of-Work (PoW) and Proof-of-Stake (PoS), FBA does not use economic staking or mining, instead relying on social and reputational capital to secure the network, making it a unique solution in the consensus landscape.
Etymology & Origin
The conceptual and historical foundation of the Federated Byzantine Agreement (FBA) consensus model, tracing its evolution from classical distributed systems to modern blockchain implementations.
The term Federated Byzantine Agreement (FBA) is a compound descriptor that precisely defines its operational principles. "Federated" denotes a decentralized network structure where participants form trust relationships through quorum slices, rather than a single, centralized authority. "Byzantine Agreement" is a foundational computer science problem, formalized by Leslie Lamport, Robert Shostak, and Marshall Pease in 1982, which addresses achieving consensus in a network where some nodes may be faulty or malicious (Byzantine faults). FBA merges these concepts to solve consensus in an open, permissionless-like setting with flexible trust.
The direct intellectual precursor to FBA is the Stellar Consensus Protocol (SCP), published in 2015 by David Mazières. SCP was the first to implement the FBA model, providing a formal framework for nodes to declare which other nodes they trust to not collude, forming a "federated" web of trust. This was a significant departure from proof-of-work and classical Byzantine Fault Tolerance (BFT), which often require a known, fixed set of validators. The "Byzantine" component was adapted from these earlier BFT protocols but applied within the novel, dynamic quorum structure defined by the federation.
The development of FBA was driven by the need for a consensus mechanism that balanced decentralization, low energy cost, and flexible membership—key requirements for global payment networks like Stellar. Its etymology reflects a synthesis of decades of distributed systems research: borrowing the robustness guarantees of Byzantine fault tolerance and combining them with a decentralized, graph-based trust model indicated by "federated." This hybrid approach aimed to avoid the centralization pressures of proof-of-work and the permissioned nature of traditional BFT.
In practice, FBA's origin in SCP established core terminology still used today, such as quorum, quorum slice, and federated voting. The model's innovation lies in allowing each node to choose its own quorum slice, making the system's security dependent on the overlap of these individual trust decisions rather than a global validator list. This design philosophically draws from how trust operates in real-world social and financial networks, translating informal relationships into a formal algorithmic process.
The legacy and continued evolution of FBA demonstrate its foundational role. While SCP remains its canonical implementation, the principles of federated Byzantine agreement have influenced other blockchain designs seeking scalable, energy-efficient consensus. The term itself has become a standard category in the taxonomy of consensus mechanisms, sitting distinctly between permissioned BFT and fully permissionless protocols like proof-of-stake, defined eternally by the dual concepts embedded in its name: decentralized federation and Byzantine fault tolerance.
Key Features & Characteristics
Federated Byzantine Agreement (FBA) is a decentralized consensus model that enables a network of nodes to agree on the validity of transactions without a central authority, using a system of overlapping trust.
Quorum Slices
The core building block of FBA. Instead of requiring agreement from the entire network, a node only needs agreement from a quorum slice—a subset of other nodes it personally trusts. This creates a flexible, personalized trust graph where each node defines its own slice.
- Enables asynchronous and leaderless consensus.
- A transaction is confirmed when it is included in the intersection of enough quorum slices to form a quorum.
Decentralized Trust
FBA achieves security through a federated model of trust. There is no fixed, global validator set. Instead, nodes choose whom to include in their quorum slices, creating a web of trust relationships.
- No Proof-of-Work: Energy efficient.
- No Centralized Committee: Avoids single points of failure.
- Security emerges from the overlap of these individual trust choices across the network.
Byzantine Fault Tolerance
FBA provides Byzantine Fault Tolerance (BFT), meaning the network can reach consensus correctly even if some participants are malicious (Byzantine nodes) or fail. It achieves this through its quorum intersection property.
- A network is intact if the quorum slices of well-behaved nodes sufficiently overlap.
- As long as the network remains intact, it can tolerate arbitrary failures within non-intact parts.
- This is a form of asynchronous BFT.
Open Membership
Unlike permissioned BFT systems, FBA allows for open membership. Any participant can join the network and start validating transactions by convincing other nodes to include them in their quorum slices.
- No Central Whitelist: Entry is permissionless.
- Reputation-Based: A node's influence grows organically as it gains the trust of others.
- This model supports a more organic and decentralized growth of the validator set.
Comparison to Other Models
FBA differs fundamentally from other major consensus mechanisms:
- vs. Proof-of-Work (Bitcoin): FBA is energy-efficient and offers fast, low-cost finality instead of probabilistic settlement.
- vs. Proof-of-Stake (Ethereum): FBA does not use staked capital as the primary security mechanism; it uses a trust graph.
- vs. Traditional BFT (Hyperledger Fabric): FBA is designed for open, permissionless networks, not closed consortiums.
How Federated Byzantine Agreement Works
Federated Byzantine Agreement (FBA) is a consensus protocol that enables decentralized networks to agree on a single truth without a central authority, even when some participants are faulty or malicious.
Federated Byzantine Agreement (FBA) is a consensus protocol that enables a decentralized network to achieve agreement on a single truth, such as the order of transactions, without relying on a central authority or global participant knowledge. It is designed to tolerate Byzantine faults, where network nodes may fail arbitrarily or act maliciously. Unlike traditional Byzantine Fault Tolerance (BFT) systems that require each node to know and communicate with every other node, FBA operates through a system of overlapping trust. Each node, or validator, chooses its own unique node list (UNL)—a subset of other nodes it trusts to behave correctly. Consensus emerges as these trust clusters, or quorum slices, intersect.
The core innovation of FBA is its quorum system. A quorum is a set of nodes sufficient to reach agreement. In FBA, a quorum is formed when every member of the set has a quorum slice—its own trusted subset—contained within the larger quorum. This creates a quorum intersection property: any two quorums must share at least one honest node. This intersection prevents the network from forking into conflicting states, as any agreement requires validation through these overlapping trust relationships. The Stellar Consensus Protocol (SCP) is the canonical implementation of FBA, defining the precise nomination and balloting phases nodes use to propose and confirm values.
A node's security and influence in the network are directly tied to its chosen unique node list. If a node selects a UNL where too many members are malicious or collude, it can be led to accept invalid statements, a risk known as ballot stuffing. Therefore, participants must curate their trust lists carefully, often relying on reputable entities or organizations. This model facilitates open membership; anyone can join the network without permission, but they must establish trust relationships to participate meaningfully in consensus. This contrasts with proof-of-work or proof-of-stake, where influence is tied to resource expenditure or token ownership.
FBA offers distinct advantages, including low energy consumption (as it does not require competitive computation), fast transaction finality (typically 2-5 seconds), and flexible trust. Its primary trade-off is the subjective trust requirement: the security of the entire network depends on the quality and decentralization of the trust graphs formed by its participants. If too many nodes trust the same small set of entities, the system becomes centralized in practice. FBA is particularly suited for use cases like cross-border payments and asset issuance, where a balance of speed, efficiency, and decentralized governance is critical.
Visualizing the Trust Graph
An exploration of Federated Byzantine Agreement (FBA), a consensus model that uses a decentralized web of trust to secure distributed networks without requiring a central authority.
Federated Byzantine Agreement (FBA) is a consensus mechanism where network participants, called nodes, achieve agreement by each selecting their own unique subset of other nodes they trust, forming a personalized quorum slice. The global trust graph is the emergent, decentralized network of all these overlapping quorum slices. Unlike proof-of-work or traditional Byzantine Fault Tolerance (BFT), FBA does not require a fixed, universally known validator set; instead, consensus is achieved through the intersection of these trusted subsets, allowing for open membership and organic growth. This model is famously implemented by the Stellar blockchain.
The core innovation of FBA is its decentralized trust model. Each node's configuration defines its quorum slice—the group of peers whose agreement is sufficient to convince that node of a statement's validity. For the entire network to reach consensus, there must exist a quorum, a set of nodes where each member's quorum slice overlaps sufficiently with the set. This structure creates fault tolerance; the network can withstand Byzantine (malicious or faulty) nodes as long as the trust graph does not allow a malicious group to form a quorum without including enough honest nodes. Visualizing this reveals a non-hierarchical web where influence is derived from being widely trusted by others.
In practice, building and analyzing the trust graph is critical for security. Key concepts include quorum intersection, which ensures that no two conflicting statements can be simultaneously ratified by disjoint groups, and identifying minimal blocking sets, the smallest groups of nodes that can disrupt consensus if they fail. Network architects must design quorum configurations to avoid centralization risks, such as a single entity controlling a disproportionately large quorum slice across many nodes. Tools for visualization help stakeholders audit network health, detect over-reliance on key participants, and ensure the decentralized and resilient properties of the system are maintained.
Examples & Implementations
Federated Byzantine Agreement (FBA) is a foundational consensus protocol used by several major blockchain networks. These examples illustrate its practical implementations and key architectural variations.
Quorum Slice Configuration
The critical configuration that defines a node's trust dependencies in FBA. A quorum slice is a set of nodes sufficient to convince a specific node of agreement. Key principles include:
- Overlap Requirement: For safety, the quorum slices of all nodes must intersect sufficiently.
- Decentralized Trust: Each entity configures its own slice, avoiding a central authority.
- Fault Tolerance: The configuration determines resilience to Byzantine failures within the network.
Comparison with Proof-of-Stake (PoS)
FBA differs fundamentally from Nakamoto Consensus (Proof-of-Work) and Proof-of-Stake systems.
- Voting vs. Staking: FBA nodes vote based on declared trust relationships, not staked capital or computational work.
- Finality: Provides immediate finality; once a value is accepted, it cannot be reversed, unlike probabilistic finality in longest-chain protocols.
- Energy Efficiency: It is inherently low-energy, as it does not require mining or intensive staking hardware.
Security & Threat Models
FBA's security relies on the structure of the decentralized trust graph. Primary threats include:
- Quorum Intersection Failure: If the network partitions into disjoint quorums, safety can be broken, leading to a fork.
- Sybil Attacks: Mitigated by requiring nodes to be vetted for inclusion in others' quorum slices, making identity creation costly.
- Liveness vs. Safety Trade-off: Configurations that maximize liveness (ability to progress) may reduce tolerance for faulty nodes, and vice versa.
Use Case: Cross-Border Payments
FBA is particularly suited for financial settlement networks due to its speed, finality, and low cost. Implementations like Stellar and Ripple use it to:
- Settle transactions in 3-5 seconds.
- Handle thousands of transactions per second (TPS).
- Enable atomic cross-currency exchanges through built-in decentralized exchange functionality. This makes FBA a pragmatic choice for institutional and remittance-focused blockchain applications.
FBA vs. Other Consensus Mechanisms
A technical comparison of Federated Byzantine Agreement with other major consensus protocols, highlighting architectural and operational differences.
| Feature / Metric | Federated Byzantine Agreement (FBA) | Proof of Work (PoW) | Proof of Stake (PoS) | Practical Byzantine Fault Tolerance (PBFT) |
|---|---|---|---|---|
Architectural Model | Decentralized, trust-based quorums | Competitive, permissionless | Stake-weighted, permissionless or permissioned | Voting-based, permissioned |
Energy Efficiency | ||||
Finality | Probabilistic (Stellar) / Immediate (SCP) | Probabilistic | Probabilistic or Immediate (Casper) | Immediate |
Fault Tolerance Threshold | Up to 20% of quorum slices by weight | Up to 25% of hashrate (honest majority) | Up to 33% of staked assets | Up to 33% of nodes (f < (n-1)/3) |
Typical Latency to Consensus | 3-5 seconds | 10 minutes (Bitcoin) | 12 seconds - 1 minute | < 1 second |
Scalability (Peak TPS) | 1,000 - 5,000+ | 7 (Bitcoin) | 10,000 - 100,000+ | 10,000 - 20,000 |
Primary Security Assumption | Trust in quorum intersection | Computational work (honest majority hashrate) | Economic stake (honest majority stake) | Limited, known validator set |
Permissionless Participation |
Security Considerations & Attack Vectors
Federated Byzantine Agreement (FBA) is a consensus mechanism where nodes trust specific other nodes (a quorum slice) to achieve network-wide agreement, introducing unique security trade-offs compared to proof-of-work or proof-of-stake.
Sybil Attacks & Quorum Intersection
A core security guarantee of FBA is quorum intersection: any two quorums must share at least one well-behaved node. If an attacker creates many Sybil nodes and convinces honest nodes to include them in their quorum slices, they can split the network into disjoint quorums, leading to a fork. Defenses include strict, identity-based admission to the trusted node set or using proof-of-stake weight to influence slice composition.
Quorum Slice Hijacking
The security of an individual node depends on the correctness of the nodes it chooses to trust. If a malicious actor compromises a critical node that is part of many other nodes' quorum slices, it can disproportionately influence consensus. This creates a targeted attack vector where attackers focus on subverting highly connected validators. Node operators must carefully curate their trust lists based on proven reliability and security practices.
Liveness vs. Safety Trade-off
FBA configurations force a trade-off between liveness (the ability to process new transactions) and safety (guaranteeing no forks).
- Tightly coupled slices (high overlap) favor safety but can halt if a small set of nodes fails.
- Loosely coupled slices favor liveness but increase the risk of conflicting ledgers if nodes are poorly connected. Network architects must balance this based on the application's tolerance for downtime versus irreversible errors.
Centralization Pressure
While FBA is more decentralized than a single entity, it naturally trends toward centralization around a de facto core set of highly trusted nodes (e.g., large institutions in the Stellar network). This creates a security bottleneck; compromising this core set could compromise the entire network. The security model thus shifts from securing a decentralized resource (hash power, stake) to securing the reputations and infrastructure of these central entities.
Byzantine Node Cascades
A Byzantine node that is trusted by many others can propagate incorrect messages or votes, causing a cascade of faults through the quorum slices. Unlike in Nakamoto consensus, where one miner's bad block is orphaned, in FBA a malicious validator can directly corrupt the consensus process for all nodes that include it in their slice. This makes the security of the network highly dependent on the integrity of the trust graph.
Contrast with Other Mechanisms
Key security differences from major consensus models:
- vs. Proof-of-Work (Bitcoin): FBA has no cryptoeconomic cost for participation, replacing it with a social trust cost. It's energy-efficient but lacks PoW's attack cost symmetry.
- vs. Proof-of-Stake (Ethereum): FBA does not use staking slashing for penalties. Misbehavior is managed through trust revocation, a slower, social process.
- vs. Practical Byzantine Fault Tolerance (PBFT): FBA has no fixed, global validator set, offering more organic growth but less predictable security thresholds.
Common Misconceptions About FBA
Federated Byzantine Agreement (FBA) is a foundational consensus mechanism, but its unique trust-based model is often misunderstood. This section clarifies key technical distinctions and corrects widespread inaccuracies about how FBA networks like Stellar achieve decentralized consensus.
No, Federated Byzantine Agreement (FBA) is a distinct consensus mechanism from Proof-of-Stake (PoS). FBA achieves agreement through a quorum slice-based voting system where nodes explicitly choose whom to trust, forming overlapping trust networks. In contrast, PoS typically uses a validator's staked economic value (their "stake") as the weighted probability for proposing or validating the next block. While both are energy-efficient alternatives to Proof-of-Work, their security models differ fundamentally: FBA's security derives from the correct configuration of trust graphs, whereas PoS's security is tied to economic incentives and slashing penalties.
Frequently Asked Questions (FAQ)
Federated Byzantine Agreement (FBA) is a foundational consensus mechanism for decentralized networks. These questions address its core principles, key differences from other protocols, and its practical applications.
Federated Byzantine Agreement (FBA) is a consensus mechanism where nodes establish trust by forming small, overlapping subsets called quorum slices, allowing the network to reach agreement without requiring every node to know or trust every other node. Unlike traditional Byzantine Fault Tolerance (BFT) which uses a fixed, known validator set, FBA enables open participation; any node can join by convincing others to include it in their quorum slices. This creates a decentralized trust graph. The network reaches consensus when a quorum—a set of nodes sufficient to convince one another of a statement's validity—is achieved. The Stellar network is the primary blockchain implementation of this model.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.