The Bitco Layer 2 Annoucée blockchain stacks of blockchain solutions on May 24, the abolition of block production after the resolution is linked to “Malebavio Stying from the mempool synchronization logic of the Stacks-Node node”.
The batteries warns against “occasional degradation” in the production of blocks
On May 24, the blockchain stacks of Bitcoin 2 Blockchain solutions announced the withdrawal of the production of blocks after he approached “Malebavivior caused in the synchronization logic of Mempool of the node of battery”. He advised all node operators, in particular minors and signatories, to upgrade their nodes to release 3.1.0.0.11.
How, in a shared update via X, the solction of layer 2 warned of the additional “degradation of opportunities” in the production of blocks until all minors and signatories end up the upgrade. The announcement director of node operators to go to the latest version intervened only a few hours after the basic developers said they identified the potential cause. In the initial post-mortem shared on Github, the battery team said:
“The bug itself dates back to 2020 and has to do with bad behavior in the mempool synchnure logic of the pile node which makes certain nodes are poorly recovered in response to the RPC calls used by Normal Syncheng Mempool.
According to the preliminary conclusion, the last upgrade is compatible with the 3.xxxxx chain guidelines The version of the last upgrade should finally solve the problem, which is initially recognized on April 18.
At the time, the Stacks team insisted that a “simple patch” would solve the problem and the node operators needed to do nothing. How, a delay in the production of blocks linked to a Bitcoin fork in block 897442 caused the developers to initiate another survey on May 19.
After seeing 70% of the signatories restore a previous version of the chain channel, normal blockchain production resumed that the developers to report to Anotter Dlay Four Dais later.
