Stellar Network Accidentally Forked after Consensus System Failure

Stellar Network Accidentally Forked after Consensus System Failure

Earlier this week, Stellar Network faced an accidental fork that occurred after the failure of their underlying consensus system. The event was first reported by Joyce Kim, the Executive Director at Stellar Development Foundation. She tried outlining the reasons behind the failure of their deterministic consensus system, blaming its limitations as one of the major reasons that explains why their network got forked at first place. She wrote: "A deterministic asynchronous consensus system can have at most two of the following three properties: safety (results are valid and identical at all....


Related News

Stellar Forks and Decides to Create a New Consensus System.

On December 5, Stellar Executive Director Joyce Kim disclosed news of a ledger fork related to a failure of their consensus system. The consensus system used by both Stellar and Ripple have never been used at the scale Stellar is implementing, and the system failed to reach consensus causing a fork in the ledger. Stellar has about 140,000 active accounts per week, and over 3 million total accounts. The maximum number of total accounts the Stellar consensus mechanism has previously supported is 2.88 million. “On Tuesday night, the nodes on the network began to disagree and caused a fork of....

Jed McCaleb Talks Stellar's New Protocol for Consensus

The Stellar Foundation has released details about the new consensus protocol it hopes to deploy on the Stellar network as early as this summer. Founded on a concept called federated Byzantine agreement, the Stellar Consensus Protocol is intended to replace Stellar's existing consensus protocol, itself is based on the system used by competitor Ripple Labs. The Stellar team said in December that it was working to replace its existing protocol following network issues last September. The Stellar Foundation, the organization that oversees the development of the Stellar network, published the....

Stellar Switches To Centralized System After Node Issue Causes Accidental Fork

Update: Stellar's Jed McCaleb has issued a statement on the issue. While he does not deny that the code has been changed since its fork from Ripple, he does maintain that the Ripple protocol could be at risk. The "TL;DR" version he posted can be found at the bottom of this article, along with the full version here. The remainder of the article, saving for the quote at the end, is in its original form. A failure in its consensus system has caused a hard fork of the Stellar network, forcing its creators to switch to a centralized system while it awaits an upgrade. In the meantime, Stellar....

Stellar Network Fork Prompts Concerns Over Ripple Consensus Protocol

A recent unintended ledger fork in the Stellar network led to a temporary disruption of its transaction system and a broader debate about the integrity of the Ripple consensus protocol. The debate began on 5th December, when Stellar Development Foundation (SDF) executive director Joyce Kim published a blog post outlining a fork in the Stellar network that the company attributed to problems within the Ripple consensus protocol. Both Ripple Labs and Stellar use the open-source protocol to provide competing transaction networks that allow fiat money to be sent over the blockchain. The....

Stellar Now Open to Developers Following Network Upgrade

Developers will now be able to build on Stellar's distributed network following an upgrade to its codebase which will also protect it against forking. According to a blog post by founder Jed McCaleb, the upgraded network is now more secure, scalable and modular than before. He added: 'The Stellar Consensus Protocol (SCP) optimises for safety rather than liveness when the network loses quorum - meaning the system is secure against forking. The Stellar Core code is now more comprehensible and elegant. Less than half the size of the previous codebase, it runs faster and uses less memory and....