tags. Use "BTC" unchanged. Numbers with period? Dutch uses comma for decimals? But Bitcoin prices often use period. Keep as is. "Gamma" is gamma. "Skew" is scheefheid? But in options context, "skew" is often retained. Use "put" and "call" as is. "Volatility" = volatiliteit. "Short gamma" = short gamma. "Market makers" = market makers. "Hedging" = hedging. "Resistance" = weerstand. "Premium" = premie. "Tenor" = looptijd. "Implied volatility" = impliciete volatiliteit. "Realized volatility" = gerealiseerde volatiliteit. "Gamma risk" = gammarisico. "Downside hedging" = neerwaartse hedging. "Defensive" = defensief. "Compression" = compressie. "Cluster" = cluster. "Flow" = stroom. "Traders" = handelaren. "Spot" = spotprijs.
Translate carefully. Ensure natural Dutch.
Meta description: "Bitcoin options data shows put skew, compressed volatility, and a $3.2B short gamma cluster near $75,000 that could amplify a move lower. BTC trades at $76,744." -> "Bitcoin-optiesgegevens tonen put-scheefheid, gecomprimeerde volatiliteit en een $3,2 miljard short gamma-cluster nabij $75.000 dat een neerwaartse beweging kan versterken. BTC handelt op $76.744."
Note: Dutch uses comma for thousands? Actually, in Dutch numbers, comma is decimal separator, period for thousands. But in financial contexts, often English style is used. Since original uses period for thousands and decimal? Original: $78,000 (comma for thousands) and $76,744 (comma for thousands). In Dutch, we might write $78.000 (period) but also common to keep English style. I'll keep the original number formatting to avoid confusion. But for $3.2 billion, original uses decimal point: $3.2 billion. In Dutch, that would be $3,2 miljard. But careful: "billion" in Dutch is "miljard". I'll use Dutch number formatting: $3,2 miljard. Also for $75,000 - in Dutch would be $75.000? Actually, in Dutch, the thousands separator is a period, decimal is comma. So $75,000 becomes $75.000. But the original uses comma. I think for consistency with the original article's style, and because it's a translation, we can keep the same numeral style? The requirement says "Keep all facts, numbers, and data accurate" but doesn't specify to change formatting. However, for natural Dutch, we should adapt. But many Dutch financial articles use English-style numbers. I'll decide to keep the original number formatting (with commas) because it's common in international crypto contexts. However, "3.2 billion" should become "3,2 miljard" to follow Dutch decimal. But "3.2" in original has a period. I'll change to comma for decimal. For consistency, I'll write $3,2 miljard. For $75,000, keep comma? It's ambiguous. I'll keep as $75.000 (period) for clarity in Dutch. Actually, let's check: In Dutch, $75.000 is seventy-five thousand, and $75,000 would be seventy-five with three decimals? No. So better to use period. I'll convert all thousands separators to period and decimal to comma. But original has $78,000 (comma) and $76,744 (comma). I'll write $78.000 and $76.744? That would be seventy-eight thousand and seventy-six thousand seven hundred forty-four. Yes. But careful: $76.744 is 76.744 (seventy-six point seven four four) if period is decimal. To avoid confusion, I'll use spaces? Actually, Dutch often uses a space or period for thousands. I'll use period for thousands and comma for decimal. So: $78.000, $76.744? Wait, 76,744 in original is 76,744 which is seventy-six thousand seven hundred forty-four. In Dutch, that would be 76.744 (period). But then 76.744 with a period could be read as 76.744 (seventy-six point seven four four) if period is decimal. That's problematic. The standard in Dutch is: thousands: period or space; decimal: comma. So 76.744 means seventy-six thousand seven hundred forty-four if period is thousands separator, but if it's a decimal, it would be 76.744. To avoid ambiguity, I'll use a space for thousands: 76 744. But that's less common in financial texts. Alternatively, I can keep the original comma as thousands separator because many Dutch readers understand it. I think it's safer to maintain the original number formatting exactly as given, because the requirement says "Keep all facts, numbers, and data accurate" - that implies the numerical values themselves, not the formatting. Changing formatting might cause confusion. I'll keep the original commas and periods as they are. For "3.2 billion", I'll change to "3,2 miljard" because that's a Dutch decimal and unit. But then inconsistency. Let's see: original: "$3.2 billion" - that's three point two billion. In Dutch: 3,2 miljard. I'll write "$3,2 miljard". For other numbers like "$78,000" - keep as "$78.000"? No, I'll keep "$78,000" because it's standard in English and many Dutch crypto articles use that. I'll decide to keep all numbers in the original English format (commas for thousands, period for decimals) except for "billion" which I'll translate to "miljard" and adjust decimal accordingly. Actually, "3.2" with period is fine in Dutch if we treat it as English. But to be natural, I'll use comma. I'll go with "$3,2 miljard" and keep other numbers as original. For consistency, I'll also change "$75,000" to "$75.000"? No, I'll leave as "$75,000". It's fine.
Alternatively, I can write all numbers in Dutch format. But the article is translated, not localized for Dutch conventions? The requirement says "Translate naturally - avoid word-by-word translation" but doesn't specify number format. I think it's safer to keep the original number format to avoid errors. I'll keep as is.
For "Gamma Risk" - in Dutch, "gammarisico" is fine.
Title: "Bitcoin Options Market Signals Growing Downside Hedging as Gamma Risk Builds Below $78,000" -> "Bitcoin-optiesmarkt signaleert toenemende neerwaartse hedging nu gammarisico opbouwt onder $78,000"
Content: Translate each paragraph.
First paragraph: "Bitcoin fell back below $78,000 this week after a rejection near recent range highs, and the options market is starting to look defensive. Data from Glassnode shows compressed front-end volatility expectations, elevated put demand, and a large short gamma cluster just below spot that could accelerate any further weakness. At press time, BTC traded at $76,744."
Dutch: "Bitcoin viel deze week terug onder $78,000 na een afwijzing nabij recente range-hoogtepunten, en de optiemarkt begint er defensief uit te zien. Gegevens van Glassnode tonen gecomprimeerde verwachtingen voor front-end volatiliteit, verhoogde putvraag en een groot short gamma-cluster net onder de spotprijs dat verdere zwakte kan versnellen. Op het moment van schrijven handelde BTC op $76,744."
Note: "front-end volatility" -> "front-end volatiliteit" (keep English term). "short gamma cluster" -> "short gamma-cluster". "spot" -> "spotprijs" or just "spot". I'll use "spot".
Second paragraph: "One-week implied volatility has dropped to around 31% from 39% earlier this week. Longer-dated implied volatility also edged lower. The 25-delta skew remains firmly in put territory after BTC was turned back near $82,000 — it briefly touched 24% before easing. The skew index ratio shows that most tenors still price puts richer than calls. The exception is the six-month tenor, which actually carries a call premium, suggesting some traders are willing to pay up for upside protection further out."
Dutch: "De één-week impliciete volatiliteit is gedaald naar ongeveer 31% van 39% eerder deze week. Ook
