Loading market data...

** Bitcoin Drops Below $67,000 as $300M in Long Positions Liquidated

** Bitcoin Drops Below $67,000 as $300M in Long Positions Liquidated

`, `

`, `

`, `
    `, `
  • `, `

    `, inline styles. * **Key Terms:** Bitcoin, Ethereum, Long Positions, Liquidated, Derivatives, Equity markets, Crude oil, Market Cap, Volume, Fear & Greed Index, RSI, Moving Average, On-Chain, Whale Activity, HODLer, DXY, Bond Yields. * **Numbers:** $67,000, $300M, $2,000, $100, $66,850, -4.25%, -8.10%, $1.31 Trillion, 32, $65,500, $68,200, 14d, 38. 3. **Translation Strategy (English to Persian):** * **Tone:** Professional, financial, news-like. * **Crypto Terms:** * Bitcoin -> بیت‌کوین (Bitcoin) * Ethereum -> اتریوم (Ethereum) * Long Positions -> پوزیشن‌های لانگ (Long Positions) or موقعیت‌های خرید (Buy Positions) - Usually "پوزیشن‌های لانگ" is common in Persian crypto communities. * Liquidated -> لیکوئید شدند (Liquidated) * Market Cap -> بازار سرمایه (Market Cap) or ارزش بازار (Market Value) - "ارزش بازار" is more common. * Fear & Greed Index -> شاخص ترس و طمع * RSI -> شاخص قدرت نسبی (RSI) * Moving Average -> میانگین متحرک * On-Chain -> آنچین (On-Chain) * Whale -> نهنگ (Whale) * HODLer -> هودلر (HODLer) * DXY -> شاخص دلار (DXY) * Bond Yields -> بازده اوراق قرضه * Risk-Off -> ریسک‌گریز (Risk-Off) * **HTML:** Must remain intact. Only text nodes inside tags should be translated. Attributes like `class`, `style`, `href` (if any) must remain unchanged. * **Numbers/Currency:** Keep USD symbols ($) and numbers as is (e.g., $67,000). * **Meta Description:** The original input has `ORIGINAL META DESCRIPTION: ` but it's empty. I need to generate a suitable meta description based on the content and translate it. 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* بیت‌کوین به زیر ۶۷,۰۰۰ دلار سقوط کرد؛ ۳۰۰ میلیون دلار پوزیشن لانگ لیکوئید شد * *Executive Summary:* خلاصه اجرایی * *What Happened:* چه اتفاقی افتاد * *Market Data Snapshot:* نمای کلی داده‌های بازار * *Market Health Indicators:* شاخص‌های سلامت بازار * *Technical Signals:* سیگنال‌های تکنیکال * *On-Chain Health:* سلامت آنچین * *Macro Environment:* محیط کلان اقتصادی * *Paragraph 1:* بازارهای دارایی دیجیتال با اصلاح تیزی مواجه شدند... * *Paragraph 2:* حجم معاملات افزایش یافت... * *Paragraph 3:* خارج از اکوسیستم کریپتو... * *Data Points:* Keep numbers exactly. Translate labels like "Current Price" to "قیمت فعلی", "24h Price Change" to "تغییر قیمت ۲۴ ساعته", etc. * *Status Labels:* [Bearish] -> [نزولی], [Fear] -> [ترس], [Strong] -> [قوی], [Broken] -> [شکسته شده], [Oversold] -> [اشباع فروش], [Below] -> [زیر], [High] -> [بالا], [Distributing] -> [توزیع], [Inflow] -> [ورودی], [Weak Hands] -> [دست‌های ضعیف], [Positive] -> [مثبت], [Headwind] -> [مانع/باد مخالف], [Risk-Off] -> [ریسک‌گریز], [Selling] -> [فروش]. * *Meta Description:* Needs to be generated since the original was empty. Something like: "Bitcoin falls below $67k with $300M liquidations. Market sentiment turns bearish amid macro pressures." -> "بیت‌کوین به زیر ۶۷ هزار دلار سقوط کرد و ۳۰۰ میلیون دلار پوزیشن لانگ لیکوئید شد. sentiment بازار تحت فشارهای کلان اقتصادی نزولی شد." 5. **Reviewing Constraints:** * JSON format required. * HTML structure preserved. * No identity leakage (don't say "I am an AI"). * Persian language (fa). 6. **Constructing the JSON:** * Escape quotes within the JSON string values properly. * Ensure newlines in HTML are handled correctly (usually kept as is within the string). 7. **Final Polish:** * Check specific terms: "Long Positions" -> "پوزیشن‌های لانگ" (common usage) or "موقعیت‌های خرید". Let's use "پوزیشن‌های لانگ" as it's standard in Persian crypto news. * "Liquidated" -> "لیکوئید". * "Risk-on assets" -> "دارایی‌های ریسک‌پذیر". * "Safe havens" -> "پناهگاه‌های امن". * "Perfect storm" -> "طوفان کامل". * "Weak Hands" -> "دست‌های ضعیف" (common crypto slang translation). * "Headwind" -> "باد مخالف" (metaphorically used for resistance/obstacle). * *Meta Description:* Since the original input had `ORIGINAL META DESCRIPTION: ` followed by nothing, I should create one based on the content to fulfill the JSON structure requirement properly. * *HTML Integrity:* Ensure `
    ` remains exactly that. Inline styles must remain exactly that. * *Numbers:* Ensure Persian numerals are used for text, but usually in financial contexts within HTML/Code, English numerals (0-9) are often preferred for compatibility, but the prompt asks for Persian translation. Standard practice in Persian web content is often using Persian numerals (۰-۹) for text, but keeping USD amounts like $67,000 with English numerals is also common for clarity. I will use Persian numerals for general text and keep specific financial data formats consistent with the original (English numerals) for accuracy as per "Keep all facts, numbers, and data accurate". Actually, standard Persian localization often converts numbers to Persian digits. However, in crypto/tech contexts, English digits are often retained for prices to avoid confusion. I will retain English digits for prices and percentages to ensure accuracy and avoid parsing errors, but translate the surrounding text. Wait, "Translate naturally" usually implies Persian numerals for text. But "Keep all facts, numbers, and data accurate" suggests not altering the values. I will keep the numeric values (prices, percentages) in English digits as they appear in the original to ensure no ambiguity in financial data, but translate the labels. * *Refinement on Numbers:* In Persian typography, it's elegant to use Persian digits (۱,