NewsCryptoRadix Halts Network for 10 Days After Three-Year-Old Bug Tied to $1.3 Million Drain

Radix Halts Network for 10 Days After Three-Year-Old Bug Tied to $1.3 Million Drain

Author: CoinLineup·

Key Takeaways

  • A three-year-old bug in the Radix layer-1 blockchain has been linked to a reported $1.3 million drain of funds.
  • The Radix network has been halted for 10 days, stopping all transactions and application activity, including transfers of the native XRD token.
  • The halt's duration is unusually long compared with outages on other networks, indicating significant remediation work is needed before a coordinated restart can occur.
  • It remains unconfirmed which protocol component contained the bug, how the drain occurred, who is responsible, and whether affected users will be compensated or funds recovered.
  • Key developments to watch include the official restart announcement, a technical post-mortem explaining the vulnerability, and whether the patch receives an independent security audit.
Radix Halts Network for 10 Days After Three-Year-Old Bug Tied to $1.3 Million Drain

A bug in the Radix blockchain network has been linked to a reported $1.3 million drain, prompting the network to halt operations for 10 days while the issue is addressed.

What the Radix Incident Involves

Radix is a layer-1 blockchain — a base-level network designed to run decentralized applications and process transactions. According to reporting by CryptoSlate, the bug at the center of this incident is three years old, meaning it existed in the codebase long before it was exploited or triggered.

The reported $1.3 million drain refers to funds that left the network or a connected protocol as a result of the bug. The precise mechanism, the affected assets, and whether any recovery is possible have not been confirmed in the available information.

A network-wide halt of this kind also differs from the compromise of a single decentralized application: the base protocol itself is paused, meaning all activity on Radix stops rather than only the activity tied to one contract or service.

Why the Blockchain Was Halted for 10 Days

When a serious bug is discovered in a blockchain network, one common response is to pause the network entirely. A halt stops all transactions from processing, which can prevent further losses while developers investigate and deploy a fix. Unlike traditional software, there is no central server to patch mid-incident — blockchain code runs across many independent nodes, so freezing activity is often the most direct way to stop ongoing losses while a fix is prepared.

The Radix network halt is reported to last 10 days — an unusually long window compared with the brief outages seen on other networks, suggesting the issue requires significant remediation work. Extended downtime of this kind also ripples outward to the applications built on the network, since any service that depends on Radix must pause alongside it. Bringing the network back is equally deliberate: the parties running it have to coordinate on the corrected code and resume from a single agreed-upon point in the ledger, which is why restart updates tend to matter as much as the halt itself.

The Radix team's official communications can be monitored via the Radix blog for updates on the timeline and the restart process.

For anyone holding Radix's native token, XRD, a 10-day halt means no transfers, swaps, or interactions with applications on the network until operations resume. Funds are not accessible through the chain during this window, though they are not necessarily at risk because of the halt itself.

What Remains Unknown

The available reporting does not confirm which specific component of the Radix protocol contained the bug, how the $1.3 million drain occurred step by step, or who is responsible. There is also no confirmed information on whether affected users will be compensated or whether the drained funds can be recovered.

Security incidents involving bugs in base-layer infrastructure are not isolated events in crypto. Vulnerabilities that go undetected for years can have outsized consequences once they are eventually triggered, and a three-year-old bug reaching this point underscores how difficult long-term code auditing can be for blockchain teams.

Users who interact with Radix-based applications should also be aware that incidents like this can involve smart contracts — automated programs that run on a blockchain and execute transactions without a middleman. If the bug touched a smart contract layer, the scope of impact may extend beyond a single wallet or account.

What to Watch as the Halt Continues

The most important updates to follow are the official restart announcement from the Radix team at radixdlt.com, any post-mortem — a detailed technical account of how the vulnerability worked and how it was fixed — and whether the resulting patch has been independently audited, meaning reviewed by security specialists who were not involved in writing it, before the network resumes.

For those who hold XRD or use any Radix-based application, the practical steps are straightforward: do not attempt transactions until the network is confirmed live again, watch the official Radix channels for a restart date, and wait for a full technical explanation before drawing conclusions about the long-term safety of the network.

Until the restart is confirmed, the success of the remediation work and the status of the drained funds remain the central open questions surrounding the incident.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.