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



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

Market Opportunity
Stellar Logo
Stellar Price(XLM)
$0.2162
$0.2162$0.2162
+0.51%
USD
Stellar (XLM) Live Price Chart
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 [email protected] 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

Why 100 Percent Test Coverage is Not Possible — Lessons from Testing Banking and Healthcare Systems

Why 100 Percent Test Coverage is Not Possible — Lessons from Testing Banking and Healthcare Systems

Quality is not about testing everything; quality is about testing what is most important.
Share
Hackernoon2025/12/26 16:05
US eyes crypto mining at disputed nuclear plant in Russia-Ukraine conflict: report

US eyes crypto mining at disputed nuclear plant in Russia-Ukraine conflict: report

The plant is located in Ukraine and has been under Russian control since 2022, with its future management a key issue in peace talks.
Share
Coinstats2025/12/26 18:58
Google's AP2 protocol has been released. Does encrypted AI still have a chance?

Google's AP2 protocol has been released. Does encrypted AI still have a chance?

Following the MCP and A2A protocols, the AI Agent market has seen another blockbuster arrival: the Agent Payments Protocol (AP2), developed by Google. This will clearly further enhance AI Agents' autonomous multi-tasking capabilities, but the unfortunate reality is that it has little to do with web3AI. Let's take a closer look: What problem does AP2 solve? Simply put, the MCP protocol is like a universal hook, enabling AI agents to connect to various external tools and data sources; A2A is a team collaboration communication protocol that allows multiple AI agents to cooperate with each other to complete complex tasks; AP2 completes the last piece of the puzzle - payment capability. In other words, MCP opens up connectivity, A2A promotes collaboration efficiency, and AP2 achieves value exchange. The arrival of AP2 truly injects "soul" into the autonomous collaboration and task execution of Multi-Agents. Imagine AI Agents connecting Qunar, Meituan, and Didi to complete the booking of flights, hotels, and car rentals, but then getting stuck at the point of "self-payment." What's the point of all that multitasking? So, remember this: AP2 is an extension of MCP+A2A, solving the last mile problem of AI Agent automated execution. What are the technical highlights of AP2? The core innovation of AP2 is the Mandates mechanism, which is divided into real-time authorization mode and delegated authorization mode. Real-time authorization is easy to understand. The AI Agent finds the product and shows it to you. The operation can only be performed after the user signs. Delegated authorization requires the user to set rules in advance, such as only buying the iPhone 17 when the price drops to 5,000. The AI Agent monitors the trigger conditions and executes automatically. The implementation logic is cryptographically signed using Verifiable Credentials (VCs). Users can set complex commission conditions, including price ranges, time limits, and payment method priorities, forming a tamper-proof digital contract. Once signed, the AI Agent executes according to the conditions, with VCs ensuring auditability and security at every step. Of particular note is the "A2A x402" extension, a technical component developed by Google specifically for crypto payments, developed in collaboration with Coinbase and the Ethereum Foundation. This extension enables AI Agents to seamlessly process stablecoins, ETH, and other blockchain assets, supporting native payment scenarios within the Web3 ecosystem. What kind of imagination space can AP2 bring? After analyzing the technical principles, do you think that's it? Yes, in fact, the AP2 is boring when it is disassembled alone. Its real charm lies in connecting and opening up the "MCP+A2A+AP2" technology stack, completely opening up the complete link of AI Agent's autonomous analysis+execution+payment. From now on, AI Agents can open up many application scenarios. For example, AI Agents for stock investment and financial management can help us monitor the market 24/7 and conduct independent transactions. Enterprise procurement AI Agents can automatically replenish and renew without human intervention. AP2's complementary payment capabilities will further expand the penetration of the Agent-to-Agent economy into more scenarios. Google obviously understands that after the technical framework is established, the ecological implementation must be relied upon, so it has brought in more than 60 partners to develop it, almost covering the entire payment and business ecosystem. Interestingly, it also involves major Crypto players such as Ethereum, Coinbase, MetaMask, and Sui. Combined with the current trend of currency and stock integration, the imagination space has been doubled. Is web3 AI really dead? Not entirely. Google's AP2 looks complete, but it only achieves technical compatibility with Crypto payments. It can only be regarded as an extension of the traditional authorization framework and belongs to the category of automated execution. There is a "paradigm" difference between it and the autonomous asset management pursued by pure Crypto native solutions. The Crypto-native solutions under exploration are taking the "decentralized custody + on-chain verification" route, including AI Agent autonomous asset management, AI Agent autonomous transactions (DeFAI), AI Agent digital identity and on-chain reputation system (ERC-8004...), AI Agent on-chain governance DAO framework, AI Agent NPC and digital avatars, and many other interesting and fun directions. Ultimately, once users get used to AI Agent payments in traditional fields, their acceptance of AI Agents autonomously owning digital assets will also increase. And for those scenarios that AP2 cannot reach, such as anonymous transactions, censorship-resistant payments, and decentralized asset management, there will always be a time for crypto-native solutions to show their strength? The two are more likely to be complementary rather than competitive, but to be honest, the key technological advancements behind AI Agents currently all come from web2AI, and web3AI still needs to keep up the good work!
Share
PANews2025/09/18 07:00