The post Stellar (XLM) Network Incident: Post-Mortem Analysis of State Archival Issue appeared on BitcoinEthereumNews.com. Felix Pinkston Nov 07, 2025 21:20 Stellar (XLM) Development Foundation addresses a critical network incident involving Soroban Live State Prioritization, detailing the root cause and corrective measures. The Stellar (XLM) Development Foundation (SDF) has released a comprehensive post-mortem report detailing a significant network incident that occurred on October 9, 2025, involving the newly implemented Soroban Live State Prioritization feature. This feature, part of the Whisk Protocol 23 (P23), was designed to enhance data handling and storage within the Stellar network. Incident Overview The issue, which went undetected for 35 days, began affecting the network as early as September 4, 2025. It was discovered that a bug within the Soroban feature was corrupting certain data entries. The SDF moved swiftly to collaborate with affected parties and network validators to manage and ultimately resolve the issue by October 23, 2025. Extent of Data Corruption In total, 478 data entries were initially corrupted due to the bug. However, according to the SDF, most of these entries were successfully repaired to their intended values. Despite these efforts, 84 data entries remained corrupted, necessitating further mitigation strategies by involved protocols and issuers. Response and Resolution Upon identifying the issue, the SDF prioritized containment, achieving significant progress by October 10, 2025. The foundation’s technical team worked diligently to address the root cause, ensuring that similar bugs are prevented in the future. The incident has provided valuable insights into the network’s vulnerabilities, prompting the SDF to implement enhanced monitoring and testing protocols. Lessons Learned This incident underscores the importance of rigorous testing and monitoring in blockchain technology. The SDF’s proactive approach in addressing the issue and its transparent communication with stakeholders have been critical in maintaining trust and integrity within the Stellar ecosystem. For more detailed information, interested parties… The post Stellar (XLM) Network Incident: Post-Mortem Analysis of State Archival Issue appeared on BitcoinEthereumNews.com. Felix Pinkston Nov 07, 2025 21:20 Stellar (XLM) Development Foundation addresses a critical network incident involving Soroban Live State Prioritization, detailing the root cause and corrective measures. The Stellar (XLM) Development Foundation (SDF) has released a comprehensive post-mortem report detailing a significant network incident that occurred on October 9, 2025, involving the newly implemented Soroban Live State Prioritization feature. This feature, part of the Whisk Protocol 23 (P23), was designed to enhance data handling and storage within the Stellar network. Incident Overview The issue, which went undetected for 35 days, began affecting the network as early as September 4, 2025. It was discovered that a bug within the Soroban feature was corrupting certain data entries. The SDF moved swiftly to collaborate with affected parties and network validators to manage and ultimately resolve the issue by October 23, 2025. Extent of Data Corruption In total, 478 data entries were initially corrupted due to the bug. However, according to the SDF, most of these entries were successfully repaired to their intended values. Despite these efforts, 84 data entries remained corrupted, necessitating further mitigation strategies by involved protocols and issuers. Response and Resolution Upon identifying the issue, the SDF prioritized containment, achieving significant progress by October 10, 2025. The foundation’s technical team worked diligently to address the root cause, ensuring that similar bugs are prevented in the future. The incident has provided valuable insights into the network’s vulnerabilities, prompting the SDF to implement enhanced monitoring and testing protocols. Lessons Learned This incident underscores the importance of rigorous testing and monitoring in blockchain technology. The SDF’s proactive approach in addressing the issue and its transparent communication with stakeholders have been critical in maintaining trust and integrity within the Stellar ecosystem. For more detailed information, interested parties…

Stellar (XLM) Network Incident: Post-Mortem Analysis of State Archival Issue

2025/11/09 04:22


Felix Pinkston
Nov 07, 2025 21:20

Stellar (XLM) Development Foundation addresses a critical network incident involving Soroban Live State Prioritization, detailing the root cause and corrective measures.

The Stellar (XLM) Development Foundation (SDF) has released a comprehensive post-mortem report detailing a significant network incident that occurred on October 9, 2025, involving the newly implemented Soroban Live State Prioritization feature. This feature, part of the Whisk Protocol 23 (P23), was designed to enhance data handling and storage within the Stellar network.

Incident Overview

The issue, which went undetected for 35 days, began affecting the network as early as September 4, 2025. It was discovered that a bug within the Soroban feature was corrupting certain data entries. The SDF moved swiftly to collaborate with affected parties and network validators to manage and ultimately resolve the issue by October 23, 2025.

Extent of Data Corruption

In total, 478 data entries were initially corrupted due to the bug. However, according to the SDF, most of these entries were successfully repaired to their intended values. Despite these efforts, 84 data entries remained corrupted, necessitating further mitigation strategies by involved protocols and issuers.

Response and Resolution

Upon identifying the issue, the SDF prioritized containment, achieving significant progress by October 10, 2025. The foundation’s technical team worked diligently to address the root cause, ensuring that similar bugs are prevented in the future. The incident has provided valuable insights into the network’s vulnerabilities, prompting the SDF to implement enhanced monitoring and testing protocols.

Lessons Learned

This incident underscores the importance of rigorous testing and monitoring in blockchain technology. The SDF’s proactive approach in addressing the issue and its transparent communication with stakeholders have been critical in maintaining trust and integrity within the Stellar ecosystem.

For more detailed information, interested parties can access the full post-mortem report available on the Stellar website.

Image source: Shutterstock

Source: https://blockchain.news/news/stellar-network-incident-post-mortem-analysis

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.

You May Also Like

Aave DAO to Shut Down 50% of L2s While Doubling Down on GHO

Aave DAO to Shut Down 50% of L2s While Doubling Down on GHO

The post Aave DAO to Shut Down 50% of L2s While Doubling Down on GHO appeared on BitcoinEthereumNews.com. Aave DAO is gearing up for a significant overhaul by shutting down over 50% of underperforming L2 instances. It is also restructuring its governance framework and deploying over $100 million to boost GHO. This could be a pivotal moment that propels Aave back to the forefront of on-chain lending or sparks unprecedented controversy within the DeFi community. Sponsored Sponsored ACI Proposes Shutting Down 50% of L2s The “State of the Union” report by the Aave Chan Initiative (ACI) paints a candid picture. After a turbulent period in the DeFi market and internal challenges, Aave (AAVE) now leads in key metrics: TVL, revenue, market share, and borrowing volume. Aave’s annual revenue of $130 million surpasses the combined cash reserves of its competitors. Tokenomics improvements and the AAVE token buyback program have also contributed to the ecosystem’s growth. Aave global metrics. Source: Aave However, the ACI’s report also highlights several pain points. First, regarding the Layer-2 (L2) strategy. While Aave’s L2 strategy was once a key driver of success, it is no longer fit for purpose. Over half of Aave’s instances on L2s and alt-L1s are not economically viable. Based on year-to-date data, over 86.6% of Aave’s revenue comes from the mainnet, indicating that everything else is a side quest. On this basis, ACI proposes closing underperforming networks. The DAO should invest in key networks with significant differentiators. Second, ACI is pushing for a complete overhaul of the “friendly fork” framework, as most have been unimpressive regarding TVL and revenue. In some cases, attackers have exploited them to Aave’s detriment, as seen with Spark. Sponsored Sponsored “The friendly fork model had a good intention but bad execution where the DAO was too friendly towards these forks, allowing the DAO only little upside,” the report states. Third, the instance model, once a smart…
Share
BitcoinEthereumNews2025/09/18 02:28
Shytoshi Kusama Addresses $2.4 Million Shibarium Bridge Exploit

Shytoshi Kusama Addresses $2.4 Million Shibarium Bridge Exploit

The post Shytoshi Kusama Addresses $2.4 Million Shibarium Bridge Exploit appeared on BitcoinEthereumNews.com. The lead developer of Shiba Inu, Shytoshi Kusama, has publicly addressed the Shibarium bridge exploit that occurred recently, draining $2.4 million from the network. After days of speculation about his involvement in managing the crisis, the project leader broke his silence. Kusama emphasized that a special “war room” has been set up to restore stolen finances and enhance network security. The statement is his first official words since the bridge compromise occurred. “Although I am focusing on AI initiatives to benefit all our tokens, I remain with the developers and leadership in the war room,” Kusama posted on social media platform X. He dismissed claims that he had distanced himself from the project as “utterly preposterous.” The developer said that the reason behind his silence at first was strategic. Before he could make any statements publicly, he must have taken time to evaluate what he termed a complex and deep situation properly. Kusama also vowed to provide further updates in the official Shiba Inu channels as the team comes up with long-term solutions. As highlighted in our previous article, targeted Shibarium’s bridge infrastructure through a sophisticated attack vector. Hackers gained unauthorized access to validator signing keys, compromising the network’s security framework. The hackers executed a flash loan to acquire 4.6 million BONE ShibaSwap tokens. The validator power on the network was majority held by them after this purchase. They were able to transfer assets out of Shibarium with this control. The response of Shibarium developers was timely to limit the breach. They instantly halted all validator functions in order to avoid additional exploitation. The team proceeded to deposit the assets under staking in a multisig hardware wallet that is secure. External security companies were involved in the investigation effort. Hexens, Seal 911, and PeckShield are collaborating with internal developers to…
Share
BitcoinEthereumNews2025/09/18 03:46