Riot Platforms, 1분기 매출 1억 6,720만 달러… 데이터센터 사업이 채굴 부진 상쇄

and

tags. We'll preserve that structure. Also ensure proper nouns: Riot Platforms, Bitcoin, Texas, New York remain in English. Use Korean terms for technical terms like "halving" -> "반감기", "hash rate" -> "해시레이트", "mining" -> "채굴", "data center" -> "데이터센터", "high-performance computing" -> "고성능 컴퓨팅", "AI workloads" -> "AI 워크로드", "block rewards" -> "블록 보상", "margin" -> "마진", "revenue" -> "매출", "income" -> "수익", "segment" -> "부문", "diversify" -> "다각화", "pure play" -> "순수 플레이" (might be okay as is or "순수 투자 대상" but "pure play" is a finance term; we can keep as "순수 플레이" or explain? Better to keep as "순수 플레이" since it's a term. Alternatively, "비트코인 가격에만 의존하는 순수 투자처" but that's longer. Let's use "순수 플레이" as it's understood in context.) Also note numbers: $167.2 million -> 1억 6,720만 달러 (1억 = 100 million, so 167.2 million = 1.672억? Actually 1억 = 100 million, so 167.2 million = 1억 6,720만 달러. Yes. $33.2 million -> 3,320만 달러. Q1 -> 1분기. Q2 -> 2분기. Now format JSON. Ensure double quotes and proper escaping if needed. The content HTML will have double quotes inside, so we need to escape them or use single quotes? The JSON spec requires double quotes for keys and string values. Inside the string, we can have double quotes if escaped with backslash. Alternatively, we can use single quotes inside the HTML attributes, but the original uses double quotes. Let's keep as is and escape. For example:

... but the

tags have no attributes, so no quotes. The headings are

with no attributes. So no need to escape. But if there were attributes like class, we'd need to escape. Here it's simple. Let's write the JSON. Note: The meta description should be a string. Final JSON structure: { "title": "Riot Platforms, 1분기 매출 1억 6,720만 달러… 데이터센터 사업이 채굴 부진 상쇄", "content": "

Riot Platforms는 2026년 1분기에 1억 6,720만 달러의 매출을 기록했으며, 이는 성장하는 데이터센터 사업이 3,320만 달러를 기여한 덕분입니다.