Loading market data...

translation:

translation:

What the papers say

The two pieces, both appearing in Nature on the same day, focus on methodological flaws in single-cell mtDNA analysis. The reply-and-response format indicates an active debate rather than a settled conclusion. The specifics are niche, confined to genomics research. Neither paper mentions blockchain, digital assets, or any crypto-related technology.

...
..." We need to translate the text, but keep the HTML structure and inline styles. Also the market snapshot has numbers and labels. We should translate the labels like "24h Change" -> "24u Wijziging" or "24 uur verandering"? Actually "24h Change" is common, but we can translate to "24u verandering". "7d Change" -> "7d verandering" or "7 dagen". "Fear & Greed" -> "Angst & Hebzucht" (common in Dutch). "Sentiment" -> "Sentiment" (same). "neutral" -> "neutraal". "Bitcoin (BTC)" stays. "Rank #1" -> "Rang #1" maybe. But we need to be consistent. Also the paragraph after that: "Why crypto can ignore this" -> "Waarom crypto dit kan negeren". Then content. Let's translate all text. Also the meta description: "Two Nature papers on mtDNA artefacts have zero crypto relevance, but they echo on-chain data risks. A reminder to cross-verify metrics." -> "Twee Nature-artikelen over mtDNA-artefacten hebben nul crypto-relevantie, maar ze echoën de risico's van on-chain data. Een herinnering om metrics te verifiëren." Now, we need to produce JSON with title, content (HTML), and meta description. Let's do the full translation. I'll write the translated content in Dutch, preserving the HTML structure exactly. The div with class market-snapshot: we need to translate the text inside but keep the style attributes. So we'll translate the labels and the values? The values are numbers and symbols, keep them. The "Fear & Greed" value "46" and "Fear" -> "Angst" maybe. "Sentiment" -> "Sentiment" and "neutral" -> "neutraal". Also "Bitcoin (BTC): $67,940 Rank #1" - keep as is, but maybe "Rang #1" for "Rank #1"? But "Rank" is also used in Dutch, but we can translate to "Rang". Let's do "Rang #1". But the original has "Rank #1", we can keep as "Rang #1" to be Dutch. Also the heading "What the papers say" -> "Wat de artikelen zeggen". "Why crypto can ignore this" -> "Waarom crypto dit kan negeren". "A data-integrity reminder" -> "Een herinnering aan data-integriteit". "The academic back-and-forth" -> "De academische heen-en-weer" or "De academische uitwisseling". We'll use "De academische uitwisseling". Now translate paragraphs. Let's write the full HTML. I'll output JSON with the translated strings. Be careful with quotes and special characters. Since we output JSON, we need to escape double quotes in the HTML. But we can use single quotes for attributes? The original uses double quotes for attributes. We'll keep as is, but in JSON we need to escape them. So we'll put the HTML as a string with escaped double quotes. But in the response, we can just output the JSON with the string properly escaped. Alternatively, we can use a tool, but we'll manually create the JSON. Let's do step by step. First, title translation: "Nature's mtDNA Artefact Papers Are a Crypto Non-Event—and a Data-Integrity Reminder" -> "Nature's mtDNA-artefactartikelen zijn een crypto-non-event—en een herinnering aan data-integriteit" But maybe better: "Nature's mtDNA-artefactartikelen: een crypto-non-event en een herinnering aan data-integriteit" but we need to keep the dash. Let's use the first. Content translation: Original paragraphs: 1. "Two articles published online in Nature on 19 August 2026 address artefacts in single-cell mitochondrial DNA analyses that can misinform phylogenies. One is a reply to the other, part of an ongoing scientific exchange. For crypto markets, the papers are a complete non-event—no asset, protocol, or regulator is implicated, and there's no mechanism for them to affect prices." Translation: "Twee artikelen die op 19 augustus 2026 online in Nature zijn gepubliceerd, behandelen artefacten in mitochondriale DNA-analyses van individuele cellen die fylogenieën kunnen misleiden. Het ene is een antwoord op het andere, onderdeel van een lopende wetenschappelijke uitwisseling. Voor cryptomarkten zijn de artikelen een compleet non-event—geen asset, protocol of toezichthouder is betrokken, en er is geen mechanisme waardoor ze de prijzen kunnen beïnvloeden." 2.

What the papers say

->

Wat de artikelen zeggen

3. "The two pieces, both appearing in Nature on the same day, focus on methodological flaws in single-cell mtDNA analysis. The reply-and-response format indicates an active debate rather than a settled conclusion. The specifics are niche, confined to genomics research. Neither mentions blockchain, digital assets, or any crypto-related technology." Translation: "De twee stukken, beide op dezelfde dag in Nature verschenen, richten zich op methodologische tekortkomingen in single-cell mtDNA-analyse. Het antwoord-en-reactie-formaat duidt op een actief debat in plaats van een afgeronde conclusie. De specifieke onderwerpen zijn niche, beperkt tot genomics-onderzoek. Geen van beide noemt blockchain, digitale activa of enige crypto-gerelateerde technologie." 4. Then the market snapshot div. We need to translate the text inside. The div has inline styles, we keep them. The text: - "Market Data Snapshot" -> "Marktdata-snapshot" or "Marktgegevens-snapshot" but we can say "Marktdata-snapshot". Actually "Market Data Snapshot" is common, but we'll translate: "Marktdata-snapshot" - "24h Change" -> "24u wijziging" (or "24 uur verandering"). Let's use "24u wijziging" to keep short. - "+5.50%" stays. - "7d Change" -> "7d wijziging" - "+7.90%" stays. - "Fear & Greed" -> "Fear & Greed" is common, but we can translate to "Angst & Hebzucht" but often kept in English. Since it's a known index, I'll keep "Fear & Greed" but maybe translate to "Angst & Hebzucht". Actually in Dutch media they use "Fear & Greed" index. We'll keep "Fear & Greed" to be safe. - "46" stays. - "Fear" -> "Angst" (since the value is 46, it's in Fear zone). So we'll translate "Fear" to "Angst". - "Sentiment" -> "