The THORChain network went offline Thursday due to a software bug, the blockchain operators confirmed on Twitter. The team noted that they are working to resolve the issue as soon as possible, adding that the outage has nothing to do with solvency. Devs are aware of a chain halt and have identified the likely cause due to a unique transaction type (nothing to do with solvency). An update will be posted as soon as there is more confirmed information. — THORChain (@THORChain) October 27, 2022 A Non-Determinism Between Nodes About four hours after the initial announcement, the THORChain team shared another update, stating that the issue stemmed from sources of non-determinism between nodes. “Consensus halts in a distributed state machine are from sources of
Topics:
Mandy Williams considers the following as important: AA News
This could be interesting, too:
Chayanika Deka writes Chinese E-commerce Giant Alibaba Downsizing Metaverse Unit to Streamline Operations: Report
Wayne Jones writes Binance Co-Founder Clarifies Asset Listing Policies, Dispels FUD
Wayne Jones writes Bitcoin Poised for 0K, Trump Win May Be Short-Term Catalyst, Says Analyst
Chayanika Deka writes Financial Nihilism Fuels Meme Coin Frenzy as Traditional Finance Loses Appeal: Binance
The THORChain network went offline Thursday due to a software bug, the blockchain operators confirmed on Twitter.
The team noted that they are working to resolve the issue as soon as possible, adding that the outage has nothing to do with solvency.
Devs are aware of a chain halt and have identified the likely cause due to a unique transaction type (nothing to do with solvency).
An update will be posted as soon as there is more confirmed information.
— THORChain (@THORChain) October 27, 2022
A Non-Determinism Between Nodes
About four hours after the initial announcement, the THORChain team shared another update, stating that the issue stemmed from sources of non-determinism between nodes.
“Consensus halts in a distributed state machine are from sources of non-determinism between individual nodes and prevent the ledger from becoming corrupted,” the team wrote.
The network operators further outlined the steps required to resolve the problem, which included finding the source of non-determinism, releasing an update, and restarting the state machine, noting that they were close to finding the source.
After another three hours, the team announced they had discovered that the issue was string manipulation.
“Turns out to be string manipulation: code was pushing a cosmos.Uint (instead of a uint64) into a string, which causes the string to get the point of the big int instead of the actual value, causing the memo string to be different on different nodes.”
When Will THORChain Resume Operations?
The developers added that they overlooked the issue in stagenet because the bad memo was swapped immediately and was never written in the block. However, it affected the mainnet because it has a queue, which does not allow the swap to synth to happen on the same block, so the bad memo was written in the block.
The team also asked THORChain node operators to stand by and get ready for instructions as the patch was being shipped immediately.
It has been more than 15 hours since the network went offline, and there is yet to be an update from the team on when the network will resume operations.
Not The First
Meanwhile, THORChain’s outage is not the first of its kind, as several other blockchains have gone offline repeatedly.
Solana has experienced several network downtimes, with the most recent being late last month due to the creation of a duplicate block.