The Litecoin crew simply introduced a brand new core model launch, which accommodates necessary safety updates.
In a tweet, the Litecoin official X account revealed that Core model 0.21.5.5 is now out there. The Litecoin Core v0.21.5.5, a patch model launch, contains necessary MWEB consensus hardening, node reliability enhancements, pockets and mining fixes, and construct/check updates. Consequently, all node operators and pockets customers are strongly inspired to improve ASAP.
The discharge additionally accommodates notable adjustments, together with necessary MWEB validation and state-handling fixes.
The utmost P2P protocol message size was elevated to 32 MB in order that legitimate MWEB blocks and messages match beneath the message-size restrict. The discharge additionally prevents the studying of the earlier block from disk when establishing HogEx transactions. This additionally avoids together with MWEB transactions in candidate blocks when their enter and output commitments would sum to zero.
Assessments had been added and expanded for MWEB P2P messages, duplicate pegins, crash restoration, mutated blocks, mining, and pockets/RPC habits.
The MWEB PMMR rewind corruption was fastened alongside improved MMR file write sturdiness. A transaction index consistency challenge was fastened that might happen if writing block information failed after the index commit.
Litecoin releases report on zero day bug
In April, Litecoin suffered a zero-day bug, which induced a DoS assault that disrupted main mining swimming pools. Non-updated mining nodes allowed an invalid MWEB transaction, permitting them to peg out cash to 3rd social gathering DEXs. A 13-block reorg reversed these invalid transactions, not permitting them to be included in the primary chain. The Litecoin Core 0.21.5.4 was launched shortly after to deal with the failure.
At April’s shut, a submit mortem report was launched on the incident. Litecoin builders recognized a important validation bug in Litecoin’s Mimblewimble Extension Block implementation in March 2026. In April, a second attacker or tester tried to make use of the identical authentic exploit path. The upgraded nodes rejected the dangerous block, leading to a 13-block invalid chain that was later reorged out after upgraded miners coordinated on the legitimate chain. The foundation bug has now been fastened.


