`, `
`, `
`, `
- `, `
- `, ``, etc.) and attributes (`class`, `style`). * **Crypto/Tech Terms:** Use standard German terms (e.g., "Market Cap" -> "Marktkapitalisierung", "Volume" -> "Volumen", "Sentiment" -> "Stimmung", "Support/Resistance" -> "Unterstützung/Widerstand", "HODLer" -> often kept as is or explained, but "HODLer" is common crypto slang even in German. I will keep "HODLer" as it's a proper noun/slang often untranslated, or use "Langzeithalter". Given the context of "HODLer Behavior", "Verhalten der HODLer" is common. "Risk-On/Risk-Off" is often kept in English in German financial contexts, but I can translate to "Risikobereitschaft hoch/niedrig". Let's stick to common industry usage: "Risk-On/Risk-Off" is widely understood, but "Risikofreude" is better German. I will use a mix where appropriate for natural flow. Actually, requirement 5 says "Use appropriate German terminology". So "Risk-On" -> "Risikofreudig", "Risk-Off" -> "Risikoavers". However, in brackets like `[Risk-On/Risk-Off/Mixed]`, these are placeholders for values. I should translate the *labels* but keep the *placeholder options* understandable or translated. Since the placeholders represent dynamic values, I should translate the options within the brackets to German so the user knows what to fill in. E.g., `[Bullish/Bearish/Neutral]` -> `[Bullisch/Bärisch/Neutral]`. * **Proper Nouns:** NYSE, Jon Herrick, Bitcoin, BTC, DXY, RSI, MA, etc. remain unchanged. 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* NYSE plant Integration der Blockchain-Technologie in ihre Betriebsabläufe * *Executive Summary:* Zusammenfassung * *What Happened:* Was passiert ist * *Market Data Snapshot:* Marktdaten-Schnappschuss * *Primary Asset:* Primäres Asset * *Current Price:* Aktueller Preis * *Market Cap:* Marktkapitalisierung * *Volume Signal:* Volumensignal * *Market Sentiment:* Marktstimmung * *Fear & Greed Index:* Fear & Greed Index (often kept) or "Angst-und-Gier-Index". Let's use "Fear & Greed Index" as it's a specific brand name often used, but "Angst-und-Gier-Index" is the translation. I'll use "Fear & Greed Index" as it's a proper noun-ish term in crypto, but translate the options. Actually, better to translate: "Angst-und-Gier-Index". * *On-Chain Signal:* On-Chain-Signal * *Macro Signal:* Makro-Signal * *Market Health Indicators:* Indikatoren für die Marktgesundheit * *Technical Signals:* Technische Signale * *Support Level:* Unterstützungsniveau * *Resistance Level:* Widerstandsniveau * *Overbought/Oversold:* Überkauft/Überverkauft * *Moving Average:* Gleitender Durchschnitt * *On-Chain Health:* On-Chain-Gesundheit * *Network Activity:* Netzwerkaktivität * *Whale Activity:* Whale-Aktivität (or "Aktivität großer Investoren"). "Whale" is common slang. I'll keep "Whale". * *Exchange Flows:* Börsenflüsse * *HODLer Behavior:* Verhalten der HODLer * *Strong/Weak Hands:* Starke/Schwache Hände * *Macro Environment:* Makroumfeld * *DXY Impact:* DXY-Auswirkung * *Bond Yields:* Anleiherenditen * *Risk Appetite:* Risikoappetit * *Institutional Flow:* Institutioneller Fluss * *Why This Matters:* Warum das wichtig ist * *For Traders:* Für Trader * *For Investors:* Für Investoren * *What Most Media Missed:* Was die meisten Medien übersehen haben * *What Happens Next:* Was als Nächstes passiert * *Short-Term Outlook:* Kurzfristige Aussicht * *Long-Term Scenarios:* Langfristige Szenarien * *Historical Parallel:* Historisches Pendant / Historischer Vergleich * *Meta Description:* Needs to be generated since original was empty. "Die NYSE plant die Integration der Blockchain-Technologie. Erfahren Sie mehr über die Auswirkungen auf den Kryptomarkt und die Marktindikatoren." 5. **Reviewing Constraints:** * JSON format strictly. * Escape quotes within JSON strings. * Preserve HTML structure exactly (classes, styles). * Placeholders like `$[Price]` must not be translated inside the brackets unless they are options like `[Bullish/Bearish]`. The prompt shows `$[Price]` (variable) vs `[Bullish/Bearish/Neutral]` (options). I should translate the options inside the brackets for consistency in a German template, but keep variable placeholders like `$[Price]` intact as they represent dynamic data injection. Actually, looking at the prompt: `$[Price]`, `[+/-X.XX%]`. These look like template variables. I should keep them exactly as is to ensure the system filling them knows what to do. However, `[Bullish/Bearish/Neutral]` are options for a human reader or a system. To be safe and natural for a German audience, I will translate the options inside the brackets (e.g., `[Bullisch/Bärisch/Neutral]`) but keep the variable syntax like `$[Price]` intact. Wait, if this is a template for a system, changing the text inside brackets might break the filling logic if it expects English keys. But the instruction says "Translate this article". Usually, this means the visible text. Placeholders like `[Price]` are visible text representations of variables. I will translate the descriptive options (B