On Wednesday, an Ethereum Foundation researcher posted an entry urging the entire industry to prepare for something in advance: “blinding mode.” What’s in the crosshairs is the signature system used to protect Bitcoin and Ethereum wallets.
Justin Drake’s concern is that AI could find a way to break this signature algorithm before quantum computers do. He set a standard for “break”: using off-the-shelf hardware to compute a private key within a week. In the worst case, he wrote, “months, not years.”
He added two more notes of his own. This is only an assumption—there’s currently no evidence that AI has already cracked existing cryptography. His recommendation is not drastic: no need to change wallets, and no need to wait for new algorithms. Just slowly move large funds to new addresses whose public keys have never been exposed. Buterin’s takeaway was that the risk should be taken seriously. Holders shouldn’t panic.
Whether a “public key” has ever been exposed is the tipping point; the old records tell the story best.
On August 11, 2013, the Bitcoin community issued an emergency alert. The problem was with the random number generator in the Android operating system. The randomness it produced could repeat. In cryptography, there’s a hard-and-fast rule: if the same random number is used twice, then with two signatures that used it, an attacker can reverse-engineer the private key. The attacker scans the public blockchain, finds repeated random numbers, computes the private key, and empties the wallet. All of this uses only publicly available data.
Two bad outcomes, same weak spot. What was truly exploited was the path of inferring private keys from public information. Back then, it took about two months for the alert in August to be followed by a patch for Android 4.4. This time, it’s a different “question setter,” but still the same math problem.
I’ll outline a three-step wrap-up. First, check whether the address holding large funds has ever sent anything to the outside. If it has, the public key is already on the chain. Next, move the long-idle portion into an address that has never received a transaction. Finally, transfer in batches—don’t consolidate everything into one conspicuous move within a week.
#中本聪国际社区Baoluo币商资本 #币安推出BinanceIntelligence #Bitcoin
Justin Drake’s concern is that AI could find a way to break this signature algorithm before quantum computers do. He set a standard for “break”: using off-the-shelf hardware to compute a private key within a week. In the worst case, he wrote, “months, not years.”
He added two more notes of his own. This is only an assumption—there’s currently no evidence that AI has already cracked existing cryptography. His recommendation is not drastic: no need to change wallets, and no need to wait for new algorithms. Just slowly move large funds to new addresses whose public keys have never been exposed. Buterin’s takeaway was that the risk should be taken seriously. Holders shouldn’t panic.
Whether a “public key” has ever been exposed is the tipping point; the old records tell the story best.
On August 11, 2013, the Bitcoin community issued an emergency alert. The problem was with the random number generator in the Android operating system. The randomness it produced could repeat. In cryptography, there’s a hard-and-fast rule: if the same random number is used twice, then with two signatures that used it, an attacker can reverse-engineer the private key. The attacker scans the public blockchain, finds repeated random numbers, computes the private key, and empties the wallet. All of this uses only publicly available data.
Two bad outcomes, same weak spot. What was truly exploited was the path of inferring private keys from public information. Back then, it took about two months for the alert in August to be followed by a patch for Android 4.4. This time, it’s a different “question setter,” but still the same math problem.
I’ll outline a three-step wrap-up. First, check whether the address holding large funds has ever sent anything to the outside. If it has, the public key is already on the chain. Next, move the long-idle portion into an address that has never received a transaction. Finally, transfer in batches—don’t consolidate everything into one conspicuous move within a week.
#中本聪国际社区Baoluo币商资本 #币安推出BinanceIntelligence #Bitcoin