Loading market data...

Galaxy Research Puts Coldcard Bitcoin Loss at $70M, 1,082.65 BTC Gone in 41 Minutes

Galaxy Research Puts Coldcard Bitcoin Loss at $70M, 1,082.65 BTC Gone in 41 Minutes

The 41-minute window

" - "

Вікно 41 хвилини

" or "41-хвилинне вікно". Better: "41-хвилинне вікно" but maybe "Вікно в 41 хвилину". We'll use "41-хвилинне вікно" as it's common. Then: "The attack unfolded rapidly. According to Galaxy's analysis, the entire loss occurred within a 41-minute period, suggesting an automated or highly coordinated exploit. The 1,196 addresses involved indicate a broad sweep rather than a targeted heist. Coldcard has not yet confirmed the root cause, but the speed and scope point to a vulnerability that allowed attackers to move funds before users could react." Translation: "Атака розгорталася швидко. За аналізом Galaxy, вся втрата сталася протягом 41-хвилинного періоду, що свідчить про автоматизований або високоскоординований експлойт. Залучені 1 196 адрес вказують на широкомасштабну операцію, а не на цілеспрямоване пограбування. Coldcard ще не підтвердив першопричину, але швидкість і масштаб вказують на вразливість, яка дозволила зловмисникам перемістити кошти до того, як користувачі змогли зреагувати." Third paragraph: "

What Galaxy found

" - "

Що виявила Galaxy

" or "Що знайшла Galaxy". Use "Що виявила Galaxy". Then: "Galaxy Research's team traced the stolen coins using on-chain data. The $70 million figure is based on the Bitcoin price at the time of the incident. The firm noted that the attacker consolidated the funds into a small number of wallets shortly after the heist. No further movement has been detected since then, leaving the possibility that the thief is waiting for a quieter moment to launder the coins." Translation: "Команда Galaxy Research відстежила вкрадені монети за допомогою ончейн-даних. Цифра у $70 мільйонів базується на ціні біткойна на момент інциденту. Фірма зазначила, що зловмисник невдовзі після пограбування консолідував кошти в невелику кількість гаманців. Відтоді жодного руху не виявлено, що залишає можливість того, що злодій чекає тихішого моменту, щоб відмити монети." Fourth paragraph: "Coldcard has yet to release a public post-mortem. Users are waiting for a firmware update or a statement explaining how the exploit worked. The 41-minute window means that even users who acted quickly may not have been able to stop the loss. Galaxy's estimate gives the community a concrete number to track as the investigation continues." Translation: "Coldcard ще не опублікував публічний пост-мортем. Користувачі чекають на оновлення прошивки або заяву, яка пояснює, як працював експлойт. 41-хвилинне вікно означає, що навіть користувачі, які діяли швидко, могли не зупинити втрату. Оцінка Galaxy дає спільноті конкретне число для відстеження, поки триває розслідування." Now meta description: "Galaxy Research estimates the Coldcard Bitcoin loss at $70 million, with 1,082.65 BTC stolen from 1,196 addresses in a 41-minute window. Details on the exploit and what comes next." Translation: "Galaxy Research оцінює втрати біткойнів Coldcard у $70 мільйонів: 1 082,65 BTC вкрадено з 1 196 адрес за 41-хвилинне вікно. Деталі експлойту та що далі." We need to ensure HTML structure: keep
,

,

tags. The content should be inside
as in original. Now we need to output JSON. Ensure proper escaping for quotes and special characters. Use double quotes for JSON keys and string values. The content is a string with HTML tags, so we need to escape double quotes inside? But we can just use the HTML as is, but we need to escape any double quotes inside the string. In the HTML there are no double quotes, only tags. So we can just put the string with double quotes around it, but we need to escape any internal double quotes. There are none. Also we need to handle newlines? We can just put the whole content as a single string with newlines, but JSON allows newlines in strings? Actually JSON strings cannot have literal newlines; they must be escaped as . But we can put the HTML as a single line, or we can include newlines but they need to be escaped. Better to keep it as a single line for simplicity, but we can also include . However, the instruction says "Preserve HTML structure" - we can keep the tags and spaces. We'll just put the content as a single string with no extra newlines, but we can keep the tags as they are. The original has newlines between paragraphs, but in JSON we can just include them as if we want. But to be safe, we can just put it as a continuous string without newlines, but that might affect readability. Since it's for a response, we can include newlines as . But the instruction says "Respond with valid JSON" - we can format it nicely. We'll produce a JSON with indentation for readability, but the content string should be a single