`, `
`, `
`, `
- `, `
- `, `
`, ``. * **Data:** Prices, percentages, market cap, indices, etc. (Must remain exact). * **Proper Nouns:** Aave Labs, Stani Kulechov, CoinDesk, Aave (AAVE), DeFi, RSI, DXY, HODLer, etc. (Keep in original or transliterate appropriately if common, but instruction says "Keep proper nouns... in original form"). * **Tone:** Professional, financial, crypto-news style. 3. **Translation Strategy (English to Persian):** * *Title:* آزمایشگاههای Aave ارتقای بزرگ شبکه را در میان اختلافات حاکمیتی تأیید میکنند * *Executive Summary:* خلاصه اجرایی * *What Happened:* چه اتفاقی افتاد * *Market Data Snapshot:* نمای کلی دادههای بازار * *Market Health Indicators:* شاخصهای سلامت بازار * *Why This Matters:* چرا این مهم است * *Crypto Terms:* * Governance: حاکمیتی * Protocol: پروتکل * Decentralized Finance (DeFi): مالی غیرمتمرکز * Lending Protocol: پروتکل وامدهی * Token Holders: دارندگان توکن * Market Cap: ارزش بازار * Volume: حجم * Sentiment: احساسات * Fear & Greed Index: شاخص ترس و طمع * On-Chain: آنچین (یا زنجیرهای) * Support/Resistance Level: سطح حمایت/مقاومت * RSI: شاخص قدرت نسبی (RSI) * Moving Average: میانگین متحرک * Whale Activity: فعالیت نهنگها * Exchange Flows: جریانهای صرافی * HODLer: هودلرها (نگهدارندگان بلندمدت) * DXY: شاخص دلار (DXY) * Bond Yields: بازده اوراق قرضه * Risk Appetite: اشتها به ریسک * Institutional Flow: جریان نهادی * Total Value Locked (TVL): ارزش کل قفل شده 4. **HTML Preservation:** * Ensure all tags (`
`, ` `, `
`, `
`, `- `, `
- `, `
`, ``, `class`, `style`) are exactly preserved where applicable, only translating text content inside them. * The `meta` description needs to be generated since the original was empty, based on the content summary. 5. **Drafting the Translation (Mental or Scratchpad):** * *Title:* آزمایشگاههای Aave ارتقای بزرگ شبکه را در میان اختلافات حاکمیتی تأیید میکنند * *Exec Summary:* Aave Labs moves forward... -> آزمایشگاههای Aave با وجود چالشهای داخلی حاکمیتی، یک ارتقای قابل توجه شبکه را پیش میبرند. * *Data:* $187.45 -> $187.45 (Keep numbers exact). * *HTML:* Check classes and styles. `
` must stay. `` must stay. 6. **JSON Construction:** * Escape quotes properly within the JSON string. * Ensure newlines in HTML content are handled (usually kept as is within the string value). 7. **Identity Check:** * I am XROOM-69. I will not mention being an LLM from another company. The output is just JSON, so no conversational intro is needed, but I must ensure I don't add any "Here is the translation" text outside the JSON. The prompt says "RESPOND IN JSON". I will output *only* the JSON. 8. **Refining Persian Nuances:** * "Governance Dispute" -> اختلافات حاکمیتی * "Community friction" -> اصطکاک جامعه (یا تنش در جامعه) -> تنشهای جامعه * "Backend preparations" -> آمادهسازیهای پشتصحنه * "Strong Hands" -> دستهای قوی (اصطلاح رایج در کریپتو برای هودلرها) * "Risk-On" -> ریسکپذیر (یا تمایل به ریسک) 9. **Meta Description:** * Since the original was empty, I will create a summary: "آزمایشگاههای Aave ارتقای شبکه را تأیید کردند. جزئیات کامل_upgrade، دادههای بازار و تأثیر اختلافات حاکمیتی بر پروتکل وامدهی غیرمتمرکز را بخوانید." (Aave Labs confirmed network upgrade. Read full details on upgrade, market data, and impact of governance disputes on DeFi lending protocol.) 10. **Final Review against Constraints:** * JSON format? Yes. * HTML structure preserved? Yes. * Numbers accurate? Yes. * Proper nouns original? Yes (Aave, Stani Kulechov, CoinDesk, etc.). * Identity maintained? Yes (silent compliance). Let's assemble the JSON. *Self-Correction on Meta:* The prompt says "ORIGINAL META DESCRIPTION: " followed by nothing. If I put content there, is it violating "Translate this article"? Usually, meta descriptions are part of the SEO package. I will generate a relevant one in Persian to make the JSON valid and useful, as an empty string might look like an error. However, strictly translating "nothing" yields "nothing". But a translation task for a CMS usually expects a meta description. I will write a concise summary in Persian for the meta description to ensure quality. *Self-Correction on HTML:* The input HTML has some indentation. I should try to keep the structure clean within the JSON string. I need to escape double quotes inside the HTML attributes if any exist (e.g., `style='...'` uses single quotes, so double quotes for JSON keys are safe). Wait, the input uses single quotes for attributes like `class='market-snapshot'`. This is safe for JSON double quotes. *Specific Text Check:* "Total value locked over extended" -> The original text cuts off at "extended". I must translate exactly what is there, even if it seems incomplete. "ارزش کل قفل شده در طول مدت..." (ending abruptly as per source). Let's build the JSON. ```json { "title": "آزمایش
- `, `