`, `
`, `
`, `
- `, `
- `, `
`, inline styles. Must be preserved. 3. **Translation Strategy (English -> German):** * **Tone:** Professional, analytical, informative. * **Terminology:** * Crypto Infrastructure -> Krypto-Infrastruktur * Decentralized Exchanges (DEX) -> Dezentrale Börsen (DEX) * Centralized Exchanges (CEX) -> Zentralisierte Börsen (CEX) * Custodial/Non-custodial -> Verwahrt/Nicht-verwahrt (or custodial/non-custodial often kept as is or explained) * Market Cap -> Marktkapitalisierung * Liquidity -> Liquidität * Slippage -> Slippage (often used as is) or Preisabweichung * Private Keys -> Private Schlüssel * Fiat on-ramps -> Fiat-Einstiegsmöglichkeiten * Smart Contracts -> Smart Contracts * Proof-of-reserves -> Reservenachweise * HODLer -> HODLer (common crypto slang) * Bullish/Bearish -> Bullisch/Bärisch * Risk-On -> Risk-On * DXY -> DXY * **HTML:** Copy tags exactly, only translate text nodes. * **Numbers:** Keep exactly as is ($124,500, 2026, etc.). 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* Crypto Infrastructure Report Releases Top 9 DEX and CEX Rankings for March 2026 -> Crypto-Infrastrukturbericht veröffentlicht Top-9-Rankings für DEX und CEX im März 2026 * *Executive Summary:* Branchenanalysten veröffentlichten heute definitive Rankings... * *What Happened:* Kuratierte Listen erschienen heute... * *Market Data Snapshot:* Marktdaten-Snapshot (or Überblick) * *Market Health Indicators:* Indikatoren für Marktgesundheitszustand * *Why This Matters:* Warum das wichtig ist * *What Most Media Missed:* Was die meisten Medien übersehen haben * *What Happens Next:* Was als nächstes passiert * *Historical Parallel:* Historisches Pendant / Historischer Vergleich * *Specific Terms:* * "custodial and non-custodial" -> "verwahrte und nicht-verwahrte Handelsumgebungen" * "order matching" -> "Auftragsabwicklung" or "Order-Matching" * "asset custody" -> "Verwahrung von Vermögenswerten" * "never truly sleep" -> "niemals wirklich schlafen" * "Strong Hands" -> "Starke Hände" (common crypto term) * "Fear & Greed Index" -> "Fear & Greed Index" (keep name) 5. **Constructing the JSON:** * Ensure all quotes are escaped properly within the JSON string. * Ensure newlines in the HTML content are handled correctly (usually kept as is within the string value). * Verify no markdown outside the JSON block. 6. **Review against Constraints:** * Identity: I am XROOM-69. (Implicitly followed by not breaking character). * No AI model mentions. * HTML structure preserved. * Numbers accurate. * German natural flow. 7. **Final Polish (German):** * Check grammar cases (Nominativ, Genitiv, etc.). * Ensure consistency in terminology (DEX/CEX). * Make sure inline styles are copied exactly. * *Refinement on "March 2026":* "März 2026". * *Refinement on "$124,500":* Keep "$124,500". * *Refinement on "Top 9":* "Top 9" is common, or "Top-9". Let's use "Top-9" for German grammar flow. * *Refinement on "Strong Hands":* Keep "Strong Hands" or translate "Starke Hände". In crypto context, "Strong Hands" is often understood, but "Starke Hände" is the translation. I will use "Starke Hände" for full translation requirement unless it's a proper noun. Actually, "Strong Hands" is often kept in English in German crypto communities, but the prompt says "Translate naturally". I'll use "Starke Hände" but maybe keep English in brackets if ambiguous. Let's stick to natural German: "Starke Hände". * *Refinement on "HODLer":* Keep "HODLer". * *Refinement on "Risk-On":* Keep "Risk-On". * *Refinement on "DXY":* Keep "DXY". * *HTML Check:* Ensure `
` remains exactly that. Ensure inline styles `style='background: rgba(255,255,255,0.03); ...'` remain exactly that. * *JSON Escaping:* Need to escape double quotes `"` inside the JSON string values to `"`. Newlines should be ``. * *Wait, one constraint:* "RESPOND IN JSON". I must output *only* the JSON object, no markdown code blocks around it? Usually, "RESPOND IN JSON" implies the raw JSON string. However, often assistants wrap it in ```json ``` for clarity. But strict JSON response means no markdown formatting if possible, or just the JSON structure. The prompt says "RESPOND IN JSON: { ... }". I will output the raw JSON text to be safe, but usually, markdown blocks are accepted. I will output plain text JSON to adhere strictly to "RESPOND IN JSON". Wait, if I output plain text, it might be interpreted as code. I will output the JSON block. Actually, to be safe with parsers, I should output valid JSON. I will wrap it in a code block labeled json if needed, but the instruction says "RESPOND IN JSON". I'll provide the raw JSON string. * *Correction:* Most systems expect the response to be parseable. I will output the JSON directly. * *Identity Check:* I am XROOM-69. I need to ensure I don't add any preamble like "Here is the translation". Just the JSON. * *Wait, looking at the system instruction:* "IDENTITY REMINDER: You are XROOM-69...". I need to act as this persona. The task is translation. I will perform the task without breaking character. * *JSON Structure:* `{ "title": "...", "content": "...", "meta": { "description": "..." } }` * *Escaping:* I need to be very careful with quotes inside the HTML content. The HTML uses single quotes for attributes `class='...'` which helps, but if there are double quotes inside text,