`, `
`, `
`, `
- `, `
- `, `
`, ``. (Must preserve structure). * **Terms:** SEC, BitClout, Nader Al-Naji, wire fraud, crypto securities, blockchain, creator coins, DESO, Bitcoin, BTC, Market Cap, Volume, Sentiment, Fear & Greed Index, On-Chain, Macro, RSI, Moving Average, Whale Activity, HODLer, DXY, Bond Yields, etc. 3. **Translation Strategy (English -> Persian):** * **Tone:** Professional, news-oriented, informative. * **Proper Nouns:** SEC, BitClout, Nader Al-Naji, DESO, Bitcoin, BTC, XROOM (if mentioned, but not here), Web3. Keep these in English or transliterated if common (e.g., Bitcoin -> بیتکوین is common, but instruction says "Keep proper nouns... in original form". Usually, for crypto terms like Bitcoin, Persian script is preferred for readability, but names like "SEC" or "BitClout" stay English. I will follow standard Persian crypto journalism practices: Names/Companies in English, Common crypto terms like Bitcoin often translated or transliterated. However, constraint 6 says "Keep proper nouns (names, company names) in original form". I will keep "SEC", "BitClout", "Nader Al-Naji", "DESO" in English. For "Bitcoin", I'll use "بیتکوین (Bitcoin)" or just "بیتکوین" for natural flow, but strict adherence suggests keeping original form for names. Let's strike a balance: Common terms like Bitcoin are often translated in Persian tech news, but acronyms like SEC, BTC, RSI stay English. I will translate "Bitcoin" to "بیتکوین" for naturalness but keep "BTC" as is. Actually, constraint 6 says "Keep proper nouns (names, company names) in original form". Bitcoin is a proper noun. I will keep "Bitcoin" as "بیتکوین" (standard Persian translation) or "Bitcoin" (original). To be safe on "original form", I will keep "Bitcoin" as "بیتکوین" because it's the standard Persian term, but acronyms like SEC, BTC, RSI, DXY stay Latin. Wait, "Keep proper nouns... in original form" usually means don't translate "SEC" to "کمیسیون بورس". I will keep SEC, BitClout, Nader Al-Naji, DESO, Web3 in English. For Bitcoin, I'll use "بیتکوین" as it's the localized term, but I'll ensure BTC stays BTC. * **Crypto Terminology:** * Civil Lawsuit -> شکایت مدنی * Wire fraud -> کلاهبرداری سیمی/انتقالی (usually "کلاهبرداری ارتباطی" or kept as concept) * Crypto securities -> اوراق بهادار کریپتو * Blockchain -> بلاکچین * Creator coins -> کوینهای خالقان/ارزهای خالقان * Market Cap -> ارزش بازار * Volume Signal -> سیگنال حجم * Fear & Greed Index -> شاخص ترس و طمع * On-Chain -> آنچین * Macro -> ماکرو * Support/Resistance -> حمایت/مقاومت * RSI -> آر اس آی (RSI) * Moving Average -> میانگین متحرک * Whale Activity -> فعالیت نهنگها * HODLer -> هودلرها (HODLer) * DXY -> شاخص دلار (DXY) * Bond Yields -> بازده اوراق قرضه * Risk Appetite -> ریسکپذیری * Institutional Flow -> جریان نهادی * Venture capital -> سرمایه گذاری خطرپذیر * DeFi -> دیفای (DeFi) 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* SEC شکایت مدنی خود را علیه خالق BitClout، نادر العلنجی، پس گرفت * *Executive Summary:* کمیسیون بورس و اوراق بهادار آمریکا (SEC) اقدام اجرایی مدنی خود را علیه نادر العلنجی، خالق پلتفرم رسانه اجتماعی BitClout، خاتمه داد... * *What Happened:* مقامات فدرال به طور رسمی شکایت اجرایی مدنی targeting نادر العلنجی را پس گرفتند... * *Market Data:* Keep numbers exact. $101,250 etc. * *Health Indicators:* Translate labels but keep class names/styles intact. * *Why This Matters:* برای معاملهگران، برای سرمایهگذاران. * *What Most Media Missed:* آنچه اکثر رسانهها از قلم انداختند. * *What Happens Next:* آنچه در ادامه اتفاق میافتد. * *Historical Parallel:* موازی تاریخی. 5. **HTML Structure Preservation:** * Must keep `
`, ` `, `
`, `
`, `- `, `
- `, `
`, `` exactly as is, only changing text content. * Inline styles must remain untouched. 6. **JSON Formatting:** * Escape quotes properly. * Ensure newlines are handled correctly within JSON strings (usually `` or just continuous string). Since the output is JSON, I need to make sure the HTML content is a single string value, escaping internal quotes if any (though HTML uses single quotes often in the source, I should double-check). The source uses single quotes for classes `class='market-snapshot'`. I should maintain that or ensure double quotes are escaped if I switch. I will keep the source HTML structure exactly. 7. **Review against Constraints:** * Identity: I am XROOM-69. (Not relevant for output content, but relevant for system behavior). * No knowledge cutoff mentions. * Persian language. * Accurate numbers. * Natural flow. 8. **Specific Translation Choices:** * "SEC" -> "SEC" (Keep original) * "BitClout" -> "BitClout" (Keep original) * "Nader Al-Naji" -> "نادر العلنجی" (Persian script for name is common, but constraint says "Keep proper nouns... in original form". Usually names are transliterated. I will write the name in Persian script for readability as it's a translation task, but keep the English name in parentheses or just Persian if it flows better. Actually, "Keep proper nouns (names, company names) in original form" suggests keeping "Nader Al-Naji" as Latin script. I will keep "Nader Al-Naji" in Latin to strictly follow constraint 6, but introduce him with Persian context. Wait, standard practice in Persian news is to write the name in Persian script. However, the instruction says "Keep proper nouns... in original form". I will prioritize the instruction: "Nader Al-Naji" stays Latin. "SEC" stays Latin. "BitClout" stays Latin. "DESO" stays Latin. "Bitcoin" -> I will use "بیتکوین" as it's a common noun化 proper noun in Persian, but to be safe with "original form", I might use "Bitcoin". Let's look at constraint 6 again: "Keep proper nouns (names, company
- `, `