Latest Protocol Releases

GM MultiversX Builders!

The lastest API service release brings:

• update to nestjs10 and latest nestjs-sdk 3.1.2 (#1160)
• Transactions pool endpoint (#1165)
• Identities in assets (#1055)

And this is not all. Check the entire list of tasks for a better overview and send us feedback and let’s get in touch if you have any improvement ideas. Become a builder!

The Sirius Release was unexpectedly robust, featuring a significant number of enhancements and new features. Due to the extensive nature of these changes, a few minor elements were overlooked. An example is this bug that required fixing:

• identity owner;

Send us feedback and let’s get in touch if you have any improvement ideas. Become a builder!

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.

Greetings, MultiversX Builders! The Sirius Release (rc/v1.6.7) is officially live, marking a significant milestone in our roadmap. This release introduces over 18 new features, several critical breaking changes, and numerous fixes and improvements. It sets the stage for the upcoming Vega Release and paves the way for our goal of reducing finality time to 3 seconds.

🔧 Key Highlights:

• Multikey Support (#4741): Enhances node functionality by allowing them to sign with multiple keys, boosting security and flexibility in operations.
• Consensus Signature Check Optimization (#4467): Major CPU efficiency improvements in block signature verification during consensus, reducing processing time significantly.
• Governance v3 Contract (#4879): Introduction of a new governance contract in Go, running alongside existing system SCs, offering refined proposal and voting mechanisms.
• DNS v2 (#5045): An update to the DNS functionality, allowing multiple and deletable user names, managed through specialized smart contracts.
• Balance Data Tries (#4636): In the data trie, values are now saved at the hash of the key instead of the original key, ensuring a balanced structure by randomizing the keys. A 'Version' field is added for backward compatibility, and a new API endpoint confirms if an account's data trie is fully migrated.
• VM1.5 (#4789): Integration of the new smart contract processor with features like Multi-async, ManagedBigFloats, ManagedMap, BackTransfers, and updated to Wasmer 2.2.
• Transaction Execution Ordering Refactor (#4918): Redesigns the grouping and execution order of transactions for improved efficiency and reliability in cross-shard interactions.
• Dynamic Gas Cost Introduction(#749): This change addresses a previously unnoticed imbalance—the time consumed for accessing the trie wasn't reflected in transaction consumed gas.

We've covered these updates in our recent developer sessions on Discord. To ensure a seamless transition, we encourage all developers to review the changes outlined below and prepare accordingly before January 16th. For support, queries, or further clarifications, reach out to us on Telegram, Discord, or your preferred communication channel.

Events notifier release v1.2.0+ has to be synced with mx-chain-go Sirius release:

• There is a new observer node → notifier integration using WebSockets.
• Outport data refactoring to common structures for all outport drivers. The same data that is sent to other drivers (like indexer) will be now sent to notifier. The already existing data events will be backwards compatible, they will not be changed.