As Bitcoin scalability attacks are underway, BIP62 may permanently solve the problem

In the past 72 hours, the Bitcoin protocol has suffered a scalability attack. This attack caused a considerable amount of user funds to be blocked on the network, and Bitcoin transactions seemed to be sent twice or double-spent. Normally, the blocked transactions will eventually be confirmed by the network, and the misleading transaction outputs will disappear. This attack does not affect the security of Bitcoin transactions, but it will bring a public crisis.

In the past few months, the Bitcoin network has experienced this kind of spam transaction blocking scalability attack, which will affect transaction confirmation. The cryptocurrency community has taken note of the suggestion of Charlie Lee, the founder of Litecoin, on this issue: Litecoin has a simple solution to the spam transaction blocking attack.

Developers have also been trying to add BIP62 to solve this problem, but Pieter Wuille believes that BIP62 will bring complexity. The Bitcoin community is currently complaining about the transaction ductility attack. In a post on BitcoinTalk, a user even claimed to be the culprit of the attack. He said:

"Well, it was none other than me who did this. The stress test is suspended for now, but I reserve the right to resume it. If you have any questions, feel free to ask."

Bitcoin users are being told that their past transactions are safe, and a Reddit thread titled ELI5 (Explain Like I'm Five) advises people to wait patiently for past transactions to be fully confirmed by the blockchain.

"I am amazed at the community's slow response to this issue. As long as BIP62 is submitted, all miners will be encouraged to implement the solution and transactions will proceed smoothly," said a Reddit user.

Currently, the transactions that are changed on the blockchain do not involve the leakage of private keys, which means that the user's Bitcoin is 100% safe and will not change the amount sent and the target address. The transaction just takes a longer time to confirm.

Yesterday I also sent a coin from my wallet, which took more than an hour to confirm the existence of the transaction malleability attack. At that time, I didn't know that there was a double spend in the transaction list of the wallet, but the double spend record eventually disappeared from my wallet. In general, it is generally believed that BIP62 will permanently solve the malleability and spam transaction blocking problems in the protocol.

Bitcoin core developers have not responded to this incident. In January this year, Gavin Andresen said that he felt that the DERSIG BIP was not bad. He will submit several improvements, such as BIP62, and explained that it will simply avoid OpenSSL in consensus confirmation.