`, `
`, `
`, `
- `, `
- `, `
`, etc.) and attributes (`class`, `style`). * **Proper Nouns:** Bitcoin, Checkonchain, BTC, DXY, etc. remain in English or commonly used Persian transliteration if standard (usually English is preferred in crypto contexts for tickers). I will keep tickers and company names in English. 3. **Drafting the Translation (Mental or Scratchpad):** * *Title:* Bitcoin Miners Lose $19,000 Per Coin as Network Difficulty Plunges 7.8% * Persian: ماینرهای بیتکوین به ازای هر سکه ۱۹,۰۰۰ دلار ضرر میکنند زیرا سختی شبکه ۷.۸٪ کاهش مییابد * *Executive Summary:* خلاصه مدیریتی * *What Happened:* چه اتفاقی افتاده است * *Market Data Snapshot:* نمای کلی دادههای بازار * *Market Health Indicators:* شاخصهای سلامت بازار * *Why This Matters:* چرا این موضوع مهم است * *What Most Media Missed:* آنچه اکثر رسانهها از قلم انداختند * *What Happens Next:* آنچه در ادامه اتفاق میافتد * *Specific Phrases:* * "sustaining heavy losses" -> متحمل زیانهای سنگین میشوند * "proof-of-work validators" -> اعتبارسنجهای اثبات کار * "Checkonchain's difficulty regression model" -> مدل رگرسیون سختی Checkonchain * "hardware amortization costs" -> هزینههای استهلاک سختافزار * "liquidity positions" -> موقعیتهای نقدینگی * "psychological levels" -> سطوح روانی * "miner capitulation events" -> رویدادهای تسلیم ماینرها * "structural squeeze" -> فشار ساختاری * *Meta Description:* Needs to be concise. "بررسی زیان ۱۹ هزار دلاری ماینرهای بیتکوین به ازای هر سکه amid کاهش سختی شبکه و تحلیل تاثیر آن بر بازار." -> "تحلیل زیان ۱۹,۰۰۰ دلاری ماینرهای بیتکوین به ازای هر سکه همزمان با کاهش ۷.۸ درصدی سختی شبکه و پیامدهای آن برای سرمایهگذاران و تریدرها." 4. **HTML Structure Check:** * Ensure all opening tags have closing tags. * Ensure classes and styles are copied exactly. * Ensure JSON escaping is correct (quotes inside strings must be escaped). 5. **JSON Formatting:** * The output must be valid JSON. * Newlines in the content string need to be escaped (``) or the whole string must be single-line. Usually, for HTML content within JSON, it's safer to keep it as a single string with escaped quotes. However, pretty-printed JSON is readable. I will ensure the `content` value is a valid JSON string (escaping double quotes inside HTML attributes if any, though the input uses single quotes in some styles which is fine, but HTML attributes usually use double quotes. The input uses `class='market-snapshot'` (single quotes) and `style='...'` (single quotes). This is valid HTML but within a JSON string, I need to make sure I don't break the JSON structure. I will wrap the JSON values in double quotes. Inside the `content` string, if there are double quotes, I must escape them. The input HTML uses single quotes for attributes, which makes it easier for JSON embedding. I will maintain that.) * Wait, the input HTML has `style='background: rgba(255,255,255,0.03); ...'`. Single quotes are safe inside a double-quoted JSON string. * I need to make sure the Persian text doesn't contain unescaped double quotes. Persian quotes are usually «» or just standard text. I will avoid using double quotes inside the text unless escaped. 6. **Identity Check:** * I am XROOM-69. I should not output any conversational text outside the JSON. The prompt asks to "RESPOND IN JSON". I will provide only the JSON block. 7. **Final Review of Translation:** * Check numbers: $19,000, 7.8%, $88,000, $69,000, -2.50%, -5.80%, $1.35 Trillion, 35, $65,000, $72,000, 42, 24-72 hour. * Check tone: Formal financial news. * Check HTML: `
`, ` `, `
`, `
`, `- `, `
- `, `
`. * *Self-C
- `, `