THORChain Expected to be released next week v3.21.1, and will go live after node churn is restored XMR
BIBIBI
AT A GLANCE
THORChain Proposed for release next week v3.21.1, and to be integrated after node churn is restored XMR; a recent attack caused losses of approximately 800 USD.
Article
THORChain Expected to be released next week v3.21.1, and will go live after node churn is restored XMR BlockBeats reports that October 23, according to THORChain’s blog,THORChain developer Chad Barraford said that v3.21 version is nearing completion, and will be released after two more code pull requests are merged v3.21.1, which is expected to take place next week.
Currently,THORChain’s node churn is paused due to an issue fixed by v3.21, pending the adoption of v3.21 and v3.21.1 and the restoration of node churn, after which Monero (XMR) will go live. After Monero, Substrate-based chains, Bittensor (TAO) and Dash are the next chains planned for integration.
In addition,THORChain encountered an attack this week targeting a vulnerability in its IBC implementation. The attacker caused THORChain to mistakenly believe it had received ATOM that it had not actually received. The solvency checker automatically triggered a pause approximately 500 USD to 20 seconds after the funding shortfall exceeded 30. The attack lasted approximately seven or minutes and caused losses of about 800 USD, which are expected to be covered by reserves in the next version.
Original link https://m.theblockbeats.info/flash/373389
Key points
01
According to THORChain’s blog, developer Chad Barraford said that v3.21 is nearing completion and will be released after two more code pull requests are merged v3.21.1, which is expected to take place next week.
02
THORChain’s node churn was paused due to an issue fixed by v3.21.
03
Pending v3.21 and v3.21.1 being adopted and node churn being restored,THORChain plans to launch Monero (XMR）。
04
After Monero, Substrate-based chains, Bittensor (TAO) and Dash are listed as the next chains planned for integration.
05
THORChain encountered an attack this week targeting a vulnerability in its IBC implementation, causing it to mistakenly believe it had received ATOM。
06
After the funding shortfall exceeded 500 USD approximately 20 to 30 seconds later, the solvency checker automatically triggered a pause.
07
The attack lasted approximately seven or minutes and caused losses of about 800 USD, which are expected to be covered by reserves in the next version.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
THORChain A version upgrade is being prepared, but node churn is currently paused. The project team said that it will integrate XMR only after the relevant version is adopted and node churn is restored. Meanwhile, an attack exploiting a vulnerability in the IBC implementation created a false impression of ATOM receipt; the system subsequently paused automatically, but losses of approximately 800 USD still occurred.
Why it matters to readers
Version adoption and the restoration of node churn are directly related to the integration progress of XMR and other chains; the attack and automatic pause also highlight the need for continued attention to cross-chain asset identification, fund security and service availability.
Beginners should not interpret “expected release” or “planned integration” as meaning that completion has already occurred. Before using the relevant cross-chain features, monitor whether the upgrade has been deployed, whether node churn has been restored, and the status of the vulnerability fix and loss coverage.
Risks and unknowns
v3.21.1 It is only expected to be released next week; the specific release date has not yet been confirmed.
v3.21 and v3.21.1 Whether it will be completed smoothly remains uncertain.
When node rotation will resume,XMR when it will officially go live has not been confirmed.
The specific integration timelines for Substrate-based chains, Bittensor, and Dash were not stated.
Related Developments
Loading event timeline…
The effectiveness of the vulnerability fixes and whether a similar attack could occur again were not stated.
Approximately 800 USD It has not yet been confirmed whether the loss has been covered by the reserve.
The message is a report by BlockBeats of THORChain statements from the blog and developers.
Related concepts
node churn
This term is not in the glossary yet. Browse related concepts in the glossary.
