Liquid network block production resumes following transaction processing issues
Liquid network block production resumes following transaction processing issues
Awaiting Liquid transactions had been queued in the mempool for roughly 22 hours subsequently the network reported an effect which acquired "cake signer nodes failing to validate certain parameters confronting each other."
2342 Full views
40 Total shares
Block product on Blockstream'southward Liquid network has resumed after technical bug related to a functionary upgrade caused many transactions to queue for hours.
In a Mon update from a Liquid oversight board fellow member identified merely as Wiz, Liquid'southward failsafe mode was activated yesterday as "an unexpected event occurred causing block signer nodes declining to validate certain parameters against each other." Equally a result, the network stopped producing blocks and transactions steadily queued in the Liquid mempool for roughly 22 hours, starting at approximately 5:19 pm Eastern Time on Mon.
Wiz reported Liquid developers have upgraded 10 of the 15 functionaries, with block production expected to resume once ane more has been stock-still. Pending Liquid transactions had been queued in the mempool until the nodes were upgraded, which was completed on Tuesday every bit the network reported blocks were coming in.
Related: Blockstream'southward Liquid pushes for DeFi with new decentralized exchange
First announced in 2022, Liquid was designed to be a Bitcoin (BTC) sidechain aimed at speeding upwards BTC transactions settlements for crypto exchanges. The network supports its LiquidBTC (LBTC) tokens pegged to Bitcoin — in that location are 3,293 currently in circulation. In addition, the Liquid Federation has 57 members, including crypto exchanges Bitfinex, BitMEX, and Huobi.
Source: https://cointelegraph.com/news/liquid-network-block-production-resumes-following-transaction-processing-issues
Posted by: zuritadind1987.blogspot.com

0 Response to "Liquid network block production resumes following transaction processing issues"
Post a Comment