BlockBeats News, May 22nd - Analyst Murphy (@Murphychen888) stated on social media that "Static Quantum Exposure" refers to those public keys that have been displayed on the blockchain and could theoretically be reverse-engineered by a future quantum computer with sufficient power using the Shor algorithm to derive the corresponding private keys of circulating bitcoins. According to Glassnode data, there are currently approximately 6.04 million bitcoins in such a quantum risk exposure state, including:

Structural Exposure, involving approximately 1.92 million bitcoins. This type of risk mainly stems from script designs such as P2PK, bare multisig, Taproot, etc., which directly reveal the public key during the transaction process. Among them, bitcoins mined in the Satoshi era are considered the most difficult to securely migrate due to the special address format and script structure.

Operational Exposure, on a larger scale, involving approximately 4.12 million bitcoins. This type of risk is mainly caused by address reuse behavior, where users repeatedly use the same address to receive or send bitcoins, resulting in the public key being exposed after the initial spend. Although this type of risk exposure is significant, since it originates from user behavior, it can theoretically be more easily improved through standardized management.

Out of the total exposed amount mentioned above, approximately 1.66 million bitcoins are related to exchange platforms. From the marked balances, Coinbase has only about 5% of its assets exposed to quantum risk, while the quantum risk exposure of other exchanges and known entities is generally higher.

It is important to note that the above analysis is not intended to rank entities by risk or predict a specific timetable for the quantum technology threat. The key point is to illustrate that the vast majority of quantum risk exposures in the current Bitcoin ecosystem are issues at the management level, which can be effectively controlled or even significantly reduced through measures such as avoiding address reuse and standardizing wallet usage processes.