tags.
First paragraph: "A new analysis from blockchain data firm Glassnode estimates that over 30% of all Bitcoin ever issued is exposed to quantum computing risk. That's 6.04 million BTC—split between 1.92 million from structural vulnerabilities like legacy P2PK outputs and a far larger 4.12 million from operational habits, chiefly address reuse and poor key management."
Indonesian: "Analisis baru dari perusahaan data blockchain Glassnode memperkirakan bahwa lebih dari 30% dari seluruh Bitcoin yang pernah diterbitkan terpapar risiko komputasi kuantum. Itu berarti 6,04 juta BTC—terbagi antara 1,92 juta dari kerentanan struktural seperti output P2PK lama dan 4,12 juta yang jauh lebih besar dari kebiasaan operasional, terutama penggunaan ulang alamat dan manajemen kunci yang buruk."
Note: Use commas for decimals in Indonesian? Usually decimal point is comma, but in numbers like 1.92 million, we write 1,92 juta. However, in English numbers we keep the dot? Actually Indonesian uses comma for decimal. But in tech context, sometimes they keep dot. Safer to use Indonesian decimal comma: 1,92 juta. But check original: "1.92 million" with dot. For consistency, I'll use dot as thousands separator? No, Indonesian uses dot for thousands and comma for decimals. So 1.92 million = 1,92 juta. But careful: 6.04 million -> 6,04 juta. I'll write "6,04 juta BTC" and "1,92 juta" and "4,12 juta". Also "P2PK" keep as is.
Second paragraph: "The dominant source of quantum vulnerability isn't old software—it's how people handle their keys. Glassnode's data shows that 4.12 million BTC are at risk from operational exposure. That happens when a holder spends from a P2PKH or P2WPKH address: the public key gets written on-chain. If that same address was ever reused, the remaining coins are toast. A quantum computer running Shor's algorithm can derive the private key from a public key in polynomial time. The numbers are sobering."
Indonesian: "Sumber dominan kerentanan kuantum bukanlah perangkat lunak lama—melainkan cara orang menangani kunci mereka. Data Glassnode menunjukkan bahwa 4,12 juta BTC berisiko akibat paparan operasional. Ini terjadi ketika pemegang melakukan transaksi dari alamat P2PKH atau P2WPKH: kunci publik ditulis di rantai. Jika alamat yang sama pernah digunakan ulang, koin yang tersisa akan hilang. Komputer kuantum yang menjalankan algoritma Shor dapat memperoleh kunci privat dari kunci publik dalam waktu polinomial. Angka-angka ini sungguh memprihatinkan."
"toast" -> "hilang" or "lenyap"? "Hilang" is fine.
Third paragraph: "Structural exposure—1.92 million BTC—includes the obvious ancient P2PK outputs (where the public key was always visible), but it also covers Taproot (P2TR) outputs. That surprised some observers. P2TR was supposed to be more private, but its design still exposes the public key on first spend if certain conditions are met. The data lumps it in with bare multisig and other legacy formats. So the risk isn't just from coins mined in 2010."
Indonesian: "Paparan struktural—1,92 juta BTC—mencakup output P2PK kuno yang jelas (di mana kunci publik selalu terlihat), tetapi juga mencakup output Taproot (P2TR). Hal ini mengejutkan beberapa pengamat. P2TR seharusnya lebih privat, namun desainnya masih mengekspos kunci publik pada transaksi pertama jika kondisi tertentu terpenuhi. Data menggabungkannya dengan multisig telanjang dan format lama lainnya. Jadi risikonya tidak hanya dari koin yang ditambang pada tahun 2010."
"bare multisig" -> "multisig telanjang"? Might be "multisig polos" or "multisig tanpa pelindung"? Better keep "bare multisig" as is? But requirement says use Indonesian terminology. In crypto, "multisig" is common. "Bare multisig" is a specific term. I'll translate as "multisig polos" or just "multisig mentah"? Let's use "multisig telanjang" but that might be confusing. Alternatively, "multisig tanpa bungkus" but not standard. I'll keep "bare multisig" in English as it's a proper term? The requirement says "use appropriate Indonesian terminology for crypto/tech terms" but if no standard, maybe keep original. I'll write "multisig telanjang" in quotes? Safer: "multisig mentah" but I'll go with "multisig tanpa pelindung" for clarity. Actually, "bare multisig" refers to a type of multisig script without additional wrapping. In Indonesian, I've seen "multisig polos". I'll use "multisig polos".
Fourth paragraph: "Shor's algorithm is devastating against ECDSA public keys—it can compute the private key fast. But it can't reverse a hash to discover a public key in the first place. That's a critical limitation. Coins sitting in addresses that have never been spent (and therefore never revealed the public key on-chain) are safe—until the owner tries to move them. That's why address reuse is the real ticking bomb. A single spend from a reused address exposes all remaining funds to anyone with a powerful enough quantum machine."
Indonesian: "Algoritma Shor sangat menghancurkan terhadap kunci publik ECDSA—ia dapat menghitung kunci privat dengan cepat. Namun ia tidak dapat membalikkan hash untuk menemukan kunci publik sejak awal. Itu adalah keterbatasan yang kritis. Koin yang berada di alamat yang belum pernah digunakan (dan karena itu tidak pernah mengungkapkan kunci publik di rantai) aman—sampai pemiliknya mencoba memindahkannya. Itulah mengapa penggunaan ulang alamat adalah bom waktu yang sesungguhnya. Satu transaksi dari alamat yang digunakan ulang mengekspos semua sisa dana kepada siapa pun yang memiliki mesin kuantum yang cukup kuat."
"ticking bomb" -> "bom waktu"
Fifth paragraph: "The clock isn't ticking yet—large-scale quantum computers remain theoretical, and no one knows exactly when they'll arrive. But the data suggests a meaningful chunk of Bitcoin's supply is already prepped for exploitation once they do. For now, the fix is simple: don't reuse addresses. Move coins to fresh ones after each transaction. The onus is on users to manage their key hygiene before the technology catches up."
Indonesian: "Jam belum berdetak—komputer kuantum skala besar masih bersifat teoretis, dan tidak ada yang tahu persis kapan mereka akan hadir. Namun data menunjukkan bahwa sebagian besar pasokan Bitcoin sudah siap untuk dieksploitasi begitu mereka tiba. Untuk saat ini, perbaikannya sederhana: jangan gunakan ulang alamat. Pindahkan koin ke alamat baru setelah setiap transaksi. Tanggung jawab ada pada pengguna untuk mengelola kebersihan kunci mereka sebelum teknologi menyusul."
"key hygiene" -> "kebersihan kunci" or "higiene kunci"? "Kebersihan kunci" is fine.
Meta description: "Glassnode data reveals 30.2% of Bitcoin's supply is vulnerable to quantum attacks, primarily due to address reuse and poor key management. Learn how Shor's algorithm threatens coins and what users can do."
Indonesian: "Data Glassnode mengungkapkan bahwa 30,2% pasokan Bitcoin rentan terhadap serangan kuantum, terutama karena penggunaan ulang alamat dan manajemen kunci yang buruk. Pelajari bagaimana algoritma Shor mengancam koin dan apa yang dapat dilakukan pengguna."
Note: 30.2% -> 30,2% in Indonesian.
Now combine into JSON. Ensure proper escaping of quotes. Use double quotes for JSON. The content should be a string with HTML tags. I'll
