Latest Protocol Releases

Calling all MultiversX Validators!

‍
The Vega Release (rc/v1.7.10) is officially live for mainnet and soon afterwards a bug that needs urgent fixing was found.

‍

Key Highlights:

• Fix for duplicated data risk [#6166]: cleans the duplicated data from the auction list.

For support, queries, or further clarifications, please reach out to us on Telegram, Discord, or your preferred communication channel.

‍

Greetings, MultiversX Builders!

‍
The Vega Release (rc/v1.7.10) is officially live, marking another important milestone in our roadmap. This release brings into production one of the most awaited and discussed upgrades, Phase 4 of the Staking module. Along this, other 2 features are being added, and 29 fixes and optimizations.

‍

Key Highlights:

• Staking phase 4 [#4934]- this feature proposes important changes with the core goals of increasing the total EGLD staked and contributing further to the network decentralization. The most important one is the removal of the existing 3,200 nodes cap and the queue system, which at the moment allows new validators to join only when others leave, with an auction-based free-market mechanism. 
• Chain Simulator [#5558]- This simulator is designed to replicate the behavior of a local testnet. Unlike a traditional testnet, this simulator operates without a consensus group, allowing for isolated testing and development and should require less resources compared with a local testnet.
• Enable epochs handler [#5419] - This feature refactors the enable epochs component to become more extensible and avoid the unnecessary changes in the satellite repos for the mx-chain-go repo.

We’ve covered these updates in our recent validators sessions on Discord. To ensure a seamless transition, we encourage all validators and developers to review the changes outlined in this release and prepare accordingly before May 21st, the day when the activation will take place. For support, queries, or further clarifications, please reach out to us on Telegram, Discord, or your preferred communication channel.

‍

Calling all validators!

We're rolling out a new upgrade for the validator nodes. We introduce a patch that brings some minor fixes but also adds the possibility to execute historical vm-queries operations.

Thank you for your continued support and cooperation. For support, queries, or further clarifications, reach out to us on Telegram, Discord, or your preferred communication channel.

Calling all validators!

We're rolling out a new upgrade for the validator nodes. You might recall the last update's short notice, where we had to delay activating the```MigrateDataTries```feature. Thankfully, the issue was confined to devnet only, leading to the hard fork on January 18. Since then, the team has focused on resolving this, with long-hours of debugging and testing. Now, we want to introduce a patch that fixes the issue and also performs the trie balancing. This ensures that gas costs align with the previously announced Phase 2 details, which you can review here: https://dynamic-gas.multiversx.com .

Thank you for your continued support and cooperation. For support, queries, or further clarifications, reach out to us on Telegram, Discord, or your preferred communication channel.

‍

Calling all validators!

We're rolling out a new upgrade for your nodes! This release introduces one important fix:

• VM 1.5 fix;

For support, queries, or further clarifications, reach out to us on Telegram, Discord, or your preferred communication channel.

Calling All Validators!

We're rolling out a new upgrade for your nodes! This release maintains full backward compatibility with version 1.6.7.0 previously announced and introduces two key fixes:

• Performance Enhancement: We've addressed a potential performance degradation issue that could occur during the transition epoch when upgrading nodes from version 1.5.x to 1.6.x.
• Node Stability Improvement: A fix has been implemented for a previously identified malfunction in the single-key redundancy node, a critical update to reduce the likelihood of increased Validator/Leader Failures.

For support, queries, or further clarifications, reach out to us on Telegram, Discord, or your preferred communication channel.