,
. We need to preserve structure. Also meta description.
We'll produce JSON with title, content (HTML), and meta description.
Let's translate carefully.
Title: "Cronos Network Halted After $75M Tectonic Exploit, Crypto.com Says Apps Unaffected" -> Arabic: "شبكة كرونوس تتوقف بعد استغلال تكتونيك بقيمة 75 مليون دولار، وكريبتو.كوم تؤكد أن تطبيقاتها غير متأثرة" but we need to keep proper nouns. "Cronos" is often transliterated as "كرونوس". "Tectonic" as "تكتونيك". "Crypto.com" as "كريبتو.كوم" or "Crypto.com" but we can keep as is? The instruction says keep proper nouns in original form, so we can keep "Cronos", "Tectonic", "Crypto.com" in Latin script? But the translation is to Arabic, so we might transliterate. The instruction says "Keep proper nouns (names, company names) in original form" - that means we should not translate them, but we can write them in Latin script? Usually in Arabic articles, they might use Arabic transliteration. But the instruction says "in original form" - so we should keep them as they are, e.g., "Cronos", "Tectonic", "Crypto.com". However, the title is in English, we need to translate the rest. So we can write: "شبكة Cronos تتوقف بعد استغلال Tectonic بقيمة 75 مليون دولار، وCrypto.com تؤكد أن تطبيقاتها غير متأثرة" - but that mixes. Better to transliterate? The instruction says "Keep proper nouns (names, company names) in original form" - so we should keep them as they are, not translate. So we can write "Cronos" and "Tectonic" and "Crypto.com" in Latin script within Arabic text. That is acceptable. So title: "شبكة Cronos تتوقف بعد استغلال Tectonic بقيمة 75 مليون دولار، وCrypto.com تؤكد أن تطبيقاتها غير متأثرة" - but we need to ensure it's natural. Alternatively, we can use Arabic transliteration: "شبكة كرونوس تتوقف بعد استغلال تكتونيك بقيمة 75 مليون دولار، وكريبتو.كوم تؤكد أن تطبيقاتها غير متأثرة" - but that changes the proper nouns. The instruction says "Keep proper nouns (names, company names) in original form" - so we should keep them as they are, not translate. So we should write "Cronos", "Tectonic", "Crypto.com" in Latin. But in Arabic text, it's common to use Arabic transliteration. However, the instruction is explicit: "Keep proper nouns (names, company names) in original form" - so we should not translate them, but we can write them in Latin script. I'll go with that.
So title: "شبكة Cronos تتوقف بعد استغلال Tectonic بقيمة 75 مليون دولار، وCrypto.com تؤكد أن تطبيقاتها غير متأثرة"
But we need to ensure the title is a proper translation. Also, "Halted" means "تتوقف" or "تم إيقافها". "After $75M Tectonic Exploit" - "بعد استغلال Tectonic بقيمة 75 مليون دولار". "Crypto.com Says Apps Unaffected" - "Crypto.com تؤكد أن تطبيقاتها غير متأثرة". That works.
Now content: We need to translate each paragraph. Let's do it.
Original:
The Cronos network was halted this week after an exploit on Tectonic protocol, with estimated losses of $75 million. The outage forced validators to pause the chain, leaving users unable to transact for hours. Crypto.com CEO Kris Marszalek said the company's app and exchange were unaffected by the breach and continued operating normally.
The exploit
Tectonic, a lending and borrowing protocol built on Cronos, suffered the attack. The exact method hasn't been detailed, but the damage is pegged at $75 million. That's a significant chunk of value for a chain that's still building out its DeFi ecosystem.
The timing isn't great. Cronos has been trying to position itself as a serious player in the Cosmos ecosystem, and a hit like this raises questions about security standards across the network.
Network halt
After the exploit, the Cronos network was halted. That's a drastic step, but not unusual when a protocol is bleeding funds. Halting gives developers and validators time to assess the damage and prevent further losses. Users on the chain were left in limbo, unable to move assets or interact with dApps.
It's not clear how long the halt lasted or when normal operations resumed. The focus now is on recovery and figuring out what went wrong.
Crypto.com's response
Kris Marszalek moved quickly to reassure users. He stated that Crypto.com's app and exchange were not affected by the Tectonic breach and continued operating normally. That's a key distinction — the exploit hit a protocol on the Cronos chain, not the exchange itself.
Still, the incident puts Crypto.com in an awkward spot. The company is closely tied to Cronos, and any instability on the chain reflects on its broader ecosystem. Marszalek's statement was short on details, but the message was clear: the exchange is fine.
What happens next is uncertain. The team behind Tectonic will need to explain how the exploit happened and whether users can expect any recovery. For now, the $75 million loss is a stark reminder that DeFi remains a risky frontier.
The Cronos network was halted this week after an exploit on Tectonic protocol, with estimated losses of $75 million. The outage forced validators to pause the chain, leaving users unable to transact for hours. Crypto.com CEO Kris Marszalek said the company's app and exchange were unaffected by the breach and continued operating normally.
The exploit
Tectonic, a lending and borrowing protocol built on Cronos, suffered the attack. The exact method hasn't been detailed, but the damage is pegged at $75 million. That's a significant chunk of value for a chain that's still building out its DeFi ecosystem.
The timing isn't great. Cronos has been trying to position itself as a serious player in the Cosmos ecosystem, and a hit like this raises questions about security standards across the network.
Network halt
After the exploit, the Cronos network was halted. That's a drastic step, but not unusual when a protocol is bleeding funds. Halting gives developers and validators time to assess the damage and prevent further losses. Users on the chain were left in limbo, unable to move assets or interact with dApps.
It's not clear how long the halt lasted or when normal operations resumed. The focus now is on recovery and figuring out what went wrong.
Crypto.com's response
Kris Marszalek moved quickly to reassure users. He stated that Crypto.com's app and exchange were not affected by the Tectonic breach and continued operating normally. That's a key distinction — the exploit hit a protocol on the Cronos chain, not the exchange itself.
Still, the incident puts Crypto.com in an awkward spot. The company is closely tied to Cronos, and any instability on the chain reflects on its broader ecosystem. Marszalek's statement was short on details, but the message was clear: the exchange is fine.
What happens next is uncertain. The team behind Tectonic will need to explain how the exploit happened and whether users can expect any recovery. For now, the $75 million loss is a stark reminder that DeFi remains a risky frontier.
